The XSLSubdeployer is acting as an interceptor and a deployer. The transformation activity needs to be factored out from the subdeployer behavior. It makes no sense to add subdeployers that really do not deploy anything simply to achive the side effect of an interceptor.
Futher, the deployers need to stop dealing with the descriptor xml document parsing and instead operate on the descriptor metadata object model. This allows for a 4.0 deployer to deal with previous version deployment decriptors as the transformation from 3.0, 3.2, 4.0 deployment descriptors to the current deployment metadata is done outside of the deployer by a filter. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 16, 2003 5:48 PM Subject: Re: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb deployment > > On Monday, June 16, 2003, at 01:53 PM, Scott M Stark wrote: > > > This is not consistent with the move to extract the metadata parsing > > from the current > > deployers into filters or interceptors associated with the deployers. > > The key issue is > > to support transformation of multiple versions of the various > > descriptors into metadata > > used by the current deployer. > > Please explain your point of view. The XSLSubdeployer IS an > interceptor. This change is in the direction of allowing a single > chain of subdeployers that can deploy anything. Why would we want to > preserve the current ejb metadata classes? > > > > Converting the XSLSubDeployer into a filter for the different > > transformations that need to > > be supported is also something that make more sense than leaving this > > as a deployer. We > > also need the ability for multiple deployers to operation on a given > > deployment if we > > do not already. > > As noted, my changes to XSLSubDeployer supply a considerable amount of > this functionality. They are not proposed as a complete solution, but > they do allow deployment of mdbs in accordance with the jca 1.5 spec. > > david jencks > /********************************** > * David Jencks > * Partner > * Core Developers Network > * http://www.coredevelopers.net > **********************************/ ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
