> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Scott > M Stark > Sent: Monday, June 16, 2003 11:35 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb > deployment > > > 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. >
Not sure I like this idea. Tell me why we need to support 3.2 and 3.0 descriptors in 4.0? I'd much rather a 3.2 component crap out gracefully in 4.0 than have to maintain 3 separate configuration mechanisms. I do like the idea of having a metamodel separate from XML parsing. BUT STILL, it is quite easy to navigate the current metadata/XML marriage that now exists in current configuration. Are you sure we're actually gaining any maintainability by changing the status quo? Bill ------------------------------------------------------- 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
