JBMC 2.0.0.Beta11

[adrian.brock]

The Beta11 and CR1 releases down to 9 issues.

Beta11

http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310060&fixfor=12311604

If you ignore the release tasks
JBMICROCONT-71/77 look to be complete?
JBMICROCONT-217 also looks complete?
JBMICROCONT-152 is probably really a fix in JBoissAS

Which leaves

JBMICROCONT-262 - field injection
JBMICROCONT-200 - problem with AOP proxies

CR1

Besides the aop work and its knock on tasks, none of the CR1
looks like it even needs to be 2.0.0.GA?

http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310060&fixfor=12312091
JBMICROCONT-28 - BeanMetaData as ValueMetaData - this looks like an unimplemented edge case?
JBMICROCONT-22 - Related Classes - a potential edge case within AOP
JBMICROCONT-25 - Configurator tidyup - like it says just tidyup

So most of what is left seems to be AOP? i.e. the parsing/deployment and a fix to the proxies.

[kabirkhan]

JBMICROCONT-200 was basically an AOP problem which should be fixed, but I will add a test to AOP-MC-INT to test so we can close this

[adrian.brock]

Ok, so I guess once the field injection is done we are ready for Beta11

Which just leaves the aop xml parsing as the main task for CR1

[adrian.brock]

Kabir, once JBoss MDR Beta12 is done later this week, we should look
at getting jboss-aop to use it.

[alesj]

JBMICROCONT-28 - BeanMetaData as ValueMetaData - this looks like an unimplemented edge case?

This is partially done.
BeanMetaData does implement VMD.
It's the cloning that's not done.

JBMICROCONT-25 - Configurator tidyup - like it says just tidyup

We can close this one, since I doubt it will ever get more tidy.
As for this FIXME

 // FIXME the isAssignable and isProgression currently needs a classloader
 // to work properly, use the bean's classloader if there isn't one provided
 if (cl == null)
 cl = info.getClassInfo().getType().getClassLoader();

The method was changed long ago to take classloader as parameter.
And I don't see what more we can do regarding classloader if one is not provided than what we already do.

[adrian.brock]

"alesj" wrote:

The method was changed long ago to take classloader as parameter.
And I don't see what more we can do regarding classloader if one is not provided than what we already do.

If they don't provide a classloader then that's their fault. ;-)

[alesj]

"alesj" wrote:

The method was changed long ago to take classloader as parameter.
And I don't see what more we can do regarding classloader if one is not provided than what we already do.

If they don't provide a classloader then that's their fault. ;-)

:-)
OK, I removed the FIXME and closed #25.