[jboss-dev-forums] [Design of OSGi Integration] - Re: BundleActivatorDeployer Questions

[adrian@jboss.org]

"johnbailey" wrote : 
  | 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
  | 

You can implement both and let the user decide. It's easily configurable
which BundleActivatorDeployer they want. :-)

anonymous wrote : 
  | 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". 

I'm using the word deployment as a generic concept.

A deployment has lots of different 'views":

Deployment - the client side view
DeploymentContext - the internal view seen by the MainDeployer
DeploymentUnit - a facade over the DeploymentContext used by the deployers
DeploymentControllerContext - the deployment as seen by the Microcontainer
etc.

You're adding another one that makes it look like an OSGi bundle.

If you have a link to the DeploymentControllerContext in your Bundle facade
then you can move the deployment between the different DeploymentStages.
See DeployersImpl for how this works during normal deployment.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130228#4130228

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130228