[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: MC upgrade breaks scoped aop tests in trunk
alesj
do-not-reply at jboss.com
Sun Nov 30 10:12:52 EST 2008
"kabir.khan at jboss.com" wrote :
| It worked for about a year, now it suddenly doesn't.
|
It worked, but it was slightly wrong and now it's fixed.
Hence all code that relied on that impl detail should be fixed as well
(by the one who relied on that impl detail). ;-)
"kabir.khan at jboss.com" wrote :
| When deploying the beanfactory it uses the correct classloader, but when it comes to creating aspect instances I need to be able to pass in the classloader.
|
But isn't this what you need (see 'Used by the GBF')
"adrain at jboss.org" wrote :
|
| | From GenericBeanFactoryMetaData
| | Code:
| |
| | if (classLoader != null)
| | {
| | builder.setClassLoader(classLoader); // Used by the ControllerContext
| | builder.addPropertyMetaData("classLoader", builder.createValue(classLoader)); // Used by the GBF
| | }
| |
|
"kabir.khan at jboss.com" wrote :
| Anyway, if you're happy with me changing GBF I can do that. Is there anything I should be aware of?
If it's API back-compatible and not to invasive, sure.
In the worst case, why don't you create your own GBF,
it's not like you need a lot of features from the original, or do you?
(hence little duplication)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193235#4193235
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193235
More information about the jboss-dev-forums
mailing list