[Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP asintegration WITHOUT the integration :-)
by kabir.khan@jboss.com
That's bizarre, my last post seems to have overwritten yours, and our names have been reversed?!?!?
For completeness, here is the post that I was replying to
"adrian" wrote :
|
| "kabir.khan(a)jboss.com" wrote : wrote : Do you have some pointers to the classloading rules? I still need to get my head around this part, but in the meantime do you think we need special ClassPools as well?
|
| I think the javassist ClassPath is closer to how the new classloaders work.
| The deployers could create a ClassPool/ClassPath structure
| that matches the classloader configuration.
|
| Like I said I don't think determining what configuration applies based on class
| locations/visibility is the correct solution anyway, even though I did manage to fix
| some issues by making AOP use ClassPool.getClassLoader() instead of the TCL.
|
| >From the tests I wrote in the AOP integration, the basic ScopedClassPool of javassist
| seems to be able to handle what we need for OSGi?
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081018#4081018
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081018
16 years, 8 months
[Design the new POJO MicroContainer] - Re: Adding ManagedObjectCreator support to AbstractSimpleRea
by adrian@jboss.org
"scott.stark(a)jboss.org" wrote : Note that the parameterized type for these deployers should really be AbstractSimpleRealDeployer<T extends Serializable> as the deployment instance needs to be castable to Serializable for the ManagedObjectFactory.
|
You can't do that. Its perfectly possible that the AbstractRealDeployer
is dealing with a transient attachment that is not intended for the management layer.
In fact, thinking about it. We shouldn't be encouraging the real deployers to do
the managed objects anyway. That should really be done in the parsing deployers.
I would be in favour of making the parsing deployers require Serializable attachments
which would mean the AppParsing deployer would currently fail to compile. ;-)
If both the parsing deployer and the real deployer have this code
for the same attachment its going to duplicate work.
So I'd like to change my vote to no. :-)
Although you could add a configuration flag to the deployer:
| private boolean buildManagedObject = false; // + getter and setter
| public void build(DeploymentUnit unit, Map<String, ManagedObject> managedObjects)
| {
| if (buildManagedObject)
| {
| ...
| }
| }
|
so it would be easy to enable it in other cases, i.e. via the configuration of the deployer.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081003#4081003
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081003
16 years, 8 months