[jboss-dev-forums] [Design of POJO Server] - Re: Hot deploying deployers - deployer chains

[adrian@jboss.org]

"scott.stark at jboss.org" wrote : 
  | The logging really needs to be part of the core bootstrap. Enabling trace level logging of the kernel using -Dlog4j.configuration=log4j-trace.properties currently is not working as expected,
  | .

That's because 
1) -D against run.sh doesn't happen until the parsing of the main() arguments
2) It should be a url

anonymous wrote : 
  | I'm not clear on why we need a distinction between 1/2, especially in terms of loading the legacy mbean service descriptor. Why not just have:
  | 
  | 1. A boostrap-beans.xml to define the kernel and profile service implementation.
  | 2. A server/config/deployers to define the deployer packages.
  | 

This is because I want to seperate the core configuration
file from the user configurable options.
The core configuration is implementation detail that we are likely
going to want to change. Mixing it with user options make this hard.

This is certainly a short coming of the current conf/jboss-service.xml
You can't create one and use it from release to release because it
changes.

anonymous wrote : 
  | If we want a shared class loader used by the deployers the server/config/deployers can include a classloader-beans.xml descriptor pointing to the lib directory and the deployers can declare a dependency on it.
  | 

The problem with a classloader-beans.xml is there
is no working classloader implementation besides the UCL classloader
at the moment.
It is something that should be looked at, since there is also
currently no way for a -beans.xml to identify itself as scoped.

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

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