Thanks for the clarification.
I see why we wouldn't deploy the bundle and just allow access to the
DeploymentControllerContext through the Bundle facade.
I am still not sure I am clear on the BundleActivator deployment.
So the current thoughts are:
1. Invoke the Activator through REAL deployer - This just invokes the Activator and does
not create a new kernel context
2. Continue to use the REAL deployer to create the BeanMetaData -allows the Activator to
have decencies fulfilled prior to being invoke
3.
anonymous wrote :
| If you want to create a kernel controller context for the bundle activator
| that's a different issue. e.g. in "PRE-REAL" you could create the
context
| and make the deployment moving to REAL dependent on that "POJO".
|
In this option a context would be created in the PRE-REAL stage. What is meant by the
"deployment" being made in the move to REAL? Is this the
DeploymentControllerContext?
Please correct any terms I am misusing, I am still getting comfortable with the codebase,
and there are a lot of classes that I could see being called "deployment".
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130219#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...