[jboss-dev-forums] [Design of POJO Server] - Re: Towards a canonical server

[adrian@jboss.org]

"scott.stark at jboss.org" wrote : 
  | If the deployments and their order are also to be part of the profile definition, we would need to get the BootstrapMetaData from the Bootstraps, but those don't exist without loading the profile.xml. Its not a big deal for these to be manageable initially, but what is the long term plan?
  | 

The longer term plan should be to minimise the bootstrap to only what
is required to get a functional profile service.

But things have leaked into the bootstrap because of "bad" dependencies.

The splitting up of the bootstrap files is the first step in indentifying/reducing 
these dependencies so they can become more normal parts of the profile.

e.g. all the JMX stuff should be in deployers rather than the bootstrap,
but then you have the problem that the @JMX advice definition is too late in the process
to expose all beans.
aop is in the bootstrap for the same reason.

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

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