[jason.greene]

I am just referring to our options for replacing the tomcat deployer object. So either we extend it, apply an advice/interceptor to it, or replace it with some kind of proxy/facade. Everything else remains the same as the solution you described earlier, A deployer service that catches and modifies the deployer instance on Tomcat5 in create or init states.

Where we need to get to is an aspectized deployment layer such that there is a webservice aspect that sees one or more components that need a webservice deployment facade. This needs to be broken up into parsing of the metadata that comes from various formats (war, ejb, mbean, mc pojo) and construction of the webservice message handling/routing layers.

We already have a unified view of metadata, and associated builders that pull from various sources. So far the following sources exist:

j2ee 1.4 JSE (war deployment)
j2ee 1.4 EJB 2.1 bean
Annotated JSE
Annotated EJB21 bean
Annotated EJB3 bean
Reflection

We would most likey just resuse EJB3 annotations for mc pojo support. We have discussed an MBean based metadata builder, as well as an annotated MBean (using EJB3 annotations).

Is the aspectized deployment layer in the works as part of mc?

-Jason

[starksm64]

I am just referring to our options for replacing the tomcat deployer object. So either we extend it, apply an advice/interceptor to it, or replace it with some kind of proxy/facade. Everything else remains the same as the solution you described earlier, A deployer service that catches and modifies the deployer instance on Tomcat5 in create or init states.

Ok, something that aligns with an aspectized deployment should be used as this is the direction we are heading. Inheritence is not a long term solution as its already clear the TomcatDeployer has internalized some behaviors that should be interceptable.

We already have a unified view of metadata, and associated builders that pull from various sources. So far the following sources exist:

j2ee 1.4 JSE (war deployment)
j2ee 1.4 EJB 2.1 bean
Annotated JSE
Annotated EJB21 bean
Annotated EJB3 bean
Reflection

We would most likey just resuse EJB3 annotations for mc pojo support. We have discussed an MBean based metadata builder, as well as an annotated MBean (using EJB3 annotations).

Is the aspectized deployment layer in the works as part of mc?

-Jason

In the works is one description that may apply. The aspectized deployment layer is one of the features to be completed for the alpha release of jboss5.