[jboss-dev-forums] [Design of POJO Server] - Re: DataSource/ServiceXSLDeployer processing issue

[bill.burke@jboss.com]

"adrian at jboss.org" wrote : "bill.burke at jboss.com" wrote : 
  |   | The EJB Deployer can do what it already does:  instantiate the container itself and install them manually into the kernel.  No need for special MC states.
  | 
  | I'm talking about solving the problem generically rather 20 different
  | solutions (each with their own bugs) in 20 different services.

I'd rather have each with their own bugs rather than a buggy generic solution that I have to keep backward compatibility with.

At least with the EJB container, what  a non-generic solution would be doing anyways is pushing as much information and processing to metadata and the metadata phase of deployment.  For instance, much of the processing for EJB container is pointcut bindings.  Theres no reason this processing cant be pushed to metadata.

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

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