Its a simply ease of use argument. Why should I have to go through a conversion step if this can be handled by the deployment process.
The current XML/metadata parsing is not maintainable. Changes are made that are not reflected in the schemas which make it difficult for tools to follow JBoss. Deployment descriptors also become non-validatable. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Bill Burke" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 16, 2003 10:58 PM Subject: RE: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb deployment > > 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
