This could simplify things considerably. You're right, we had a
'delegate to JSR109Service' approach in place for the
AbstractWebContainer and the EJBDeployer. I mainly did this because I
was not happy with the order of deployment (subdepoyment start/create
before parent start/create). Realy the
-Ursprüngliche Nachricht-
Von: Scott M Stark [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 20. November 2003 15:34
An: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Betreff: [JBoss-dev] Re: deployment classloader in
AbstractWebContainer
The deployment localCl is only for
Its seems to me that we need to instead of having the JSR109Service
be a competely seperate deployer from the AbstractWebContainer (which
by the way needs to be broken up into a deployer + a container to
address some class override issues), that the AbstractWebContainer either
needs to incorporate
