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

[scott.stark@jboss.org]

"adrian at jboss.org" wrote : 
  | So how do you want to structure this?
  | 
  | For now, I'd suggest:
  | 
  | 1) Using the conf/jboss-service.xml
  | as the "core configuration"
  | which would contain:
  | * The static jars to deploy as now
  | * The core logging
  | * The remaining legacy bits 
  | 
  | We should aim to remove most of this over time,
  | either althogether or into their own deployments.
  | 
  | 2) Create a server/config/deployers
  | which serves to idenitfy the deployer packages
  | 

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, and if we want to use jdk logger we need to install a LogManager early on.

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.

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.


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

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