Breaking up jboss.microcontainer.lib

[starksm64]

In in the interim of getting the jbossas thirdparty contents coming from maven repos, I want to breakup the current jboss/microcontainer jars to allow easier updates. Right now I'm just going to start with the jboss-managed.jar.

[starksm64]

I broke up the jboss/microcontainer jboss repository contents to move the jboss-managed.jar to jboss/jboss-managed. The 2.0.0.Beta10.1 releases are just partitioning of the 2.0.0.Beta10 released to move the jboss-managed.jar into a separate project in the repository.

[adrian.brock]

We also need to move container, metatype and classload* out of the MC project.

It might also be a good idea to split out container's Class/BeanInfo component
(used by JBossXB for example) and the MetaData{Repository} (used by AOP)
into seperate projects.

We could also make a case for seperating the POJO projects from the deployers.

Let's do this for the CR1 release.

[starksm64]

Ok.

[adrian.brock]

SInce I'm now about ready to integrate the latest MC (which is pretty close to RC1
status) into the AS, I thought I'd do this splitting up.

What I propose to do is move the following to top level projects
and either create an CR1 or Beta11 release based on outstanding issues in JIRA.

I'd like to get everything to CR1 in the next couple of weeks.
i.e. these could be the final releases.

Where I make it a CR1, I'll also create branches, leaving trunk for development
of the next version.

I'm ignoring issues that say "need to write tests" when judging if it should go to CR1.

Project: jboss-reflection
===================

This is the class/beaninfo stuff, used by at least JBossXB.
I'll make this a CR1. Besides all the javassist classinfo stuff (which we
aren't going to do for this release) there's two issues.

* ClassInfo serialization which I believe Ales has already done but not closed
http://jira.jboss.com/jira/browse/JBMICROCONT-128
* A simple bug that I'll fix
http://jira.jboss.com/jira/browse/JBMICROCONT-229

Project: jboss-metadata-repository
============================
This is the scoped metadata used by at least AOP
All the issues are about writing testing so this can go to CR1,
except one which isn't scheduled for this release
(LRU cache in CachedMetaDataContext which isn't currently used anywhere anyway :-).

Project: jboss-classloader
=====================
This is the classloader, classloading and classloading-vfs projects
This will remain at beta until all the classloading issues are resolved in JBossAS JIRA.

Project jboss-managed
===================
This is the metatype and managed projects.
I'll leave this at beta since Scott is mainly the one working on this,
so I don't know the status.

Project: jboss-deployers
====================
This is all the deployers projects.
Again this will remain at beta until we've got all the JBossAS issues resolved.

Project: OSGi
===========
This should really be a top level project. But it isn't included in the release
since it is WIP.

What remains
===========
That will just leave the core microcontainer and related integration
projects for aop, drools, jbpm, spring, etc.

With the other projects gone, we should look towards creating a CR1
for this, but there's still at least the outstanding issue with JBossXB/Maps
and we might want to add some "placeholder code" for Julien's requirement?

[starksm64]

I'm testing the managed/metatype changes locally in the profileservice project for now. I'll update these artifacts/projects in mc next week or so as I'm working on ejb3 stuff this week.

[adrian.brock]

I'm not doing it immediately ;-)
Though I would like to get this done sooner rather than later.

I still need to fix issues found with the integration of the latest changes into JBossAS.
We haven't done a major release of the MC since just after beta3 (there
wasn't one for beta4).

e.g. Issues like:
* classloader config changes (now that classloading is a real spi)
* the thread context classloader usage (for beans and deployers)
* AOP's use of the in memory vfs (now done properly in a seperate deployer)
* etc.

I also need to do an implementation of the modularised bootstrap
and Tomcat using the classloading dependencies, at least to
validate it is possible in a future release
even if we don't do them for 5.0.0.GA (i.e. I have the basics correct :-)

Another major issue I need to do for 5.0.0.RC1 is "refactoring" of the
deployers. e.g. things like the jca repository being in the parsing deployer
same with the loader-repository-config generation.
(And speaking of jca, that codebase still needs merging from 4.2.x
to make sure we have all the latest fixes).

Busy, busy, busy... ;-)

[adrian.brock]

Another major issue I need to do for 5.0.0.RC1 is "refactoring" of the
deployers.

Which also needs to include a test in the testsuite for a metadata only
deployment (e.g. programmatic construction of a datasource)
so we don't have issues like the one Thomas just raised:
http://jira.jboss.com/jira/browse/JBAS-5257
with deployers assuming things they shouldn't.

[anil.saldhana]

I do not think there are any issues with the security deployer (in the new version). It does not assume any virtual files. All it does is work on the metadata that is passed to it.

[adrian.brock]

I do not think there are any issues with the security deployer (in the new version). It does not assume any virtual files. All it does is work on the metadata that is passed to it.

I don't assume anything is correct until is actually tested. :-)

Thomas is the first to actually try what I'm talking about. It certainly works
in the tests in the MC project, but whether it works with the deployers in JBossAS
is a totally different issue.

[anil.saldhana]

I do not think there are any issues with the security deployer (in the new version). It does not assume any virtual files. All it does is work on the metadata that is passed to it.

I don't assume anything is correct until is actually tested. :-)

Thomas is the first to actually try what I'm talking about. It certainly works
in the tests in the MC project, but whether it works with the deployers in JBossAS
is a totally different issue.

Ok, as you showed us, it is the Service(Deployer) and not the Security(Deployer). ;) So your assertion that there may be issues with deployers is correct....

[alesj]

* ClassInfo serialization which I believe Ales has already done but not closed
http://jira.jboss.com/jira/browse/JBMICROCONT-128

Yup, this one is done.
I'll just make sure tomorrow if all is OK, and close the issue.

What remains
===========
That will just leave the core microcontainer and related integration
projects for aop, drools, jbpm, spring, etc.

We should get a name for this one as well.
A new name, to get people completely aware that we broke up the MC.
Plain jboss-microcontainer would just confuse them, expacting that there is more to what they actually see. ;-)

With the other projects gone, we should look towards creating a CR1
for this, but there's still at least the outstanding issue with JBossXB/Maps
and we might want to add some "placeholder code" for Julien's requirement?

I'm on the OSGi testsuite/tck atm, but once I'm done with that I can have a look at Julien's requirements.
You'll know when that happens since I'll start discussing it (asking all sort of questions) on the forum. :-)

I've pinged Alex for the JBossXB.CR6 release, which is gonna resolve our MC + JAXB issues.
He's almost done, but has some Xerces problems.

I'll update these artifacts/projects in mc next week or so as I'm working on ejb3 stuff this week.

Is that the container/pool we discussed?
We/you haven't raised any issues on it.