+1000 I'm really glad to see someone is taking advantage of the xsl sub deployer. I think more the simplifications/customizations we can make the better.
Do you have any ideas how we can include these customized configuration xml bits in one file, so you can have both regular mbean config, <xa-datasource>, <jms-provider>, etc etc. in one file, with each custom element being processed by its own xsl? I don't know if this would help, but in jboss 4 you can generate xmbean configuration including the initial attribute values and include it "inline" in a *-service.xml file. This lets you deploy POJO as xmbeans without needing the standard *MBean interface. Would you be interested in working on some xsl for jca 1.5 deployment? I have most of the server side stuff written, (and some of it even tested) but havent' started on deployment yet. I think it can be 99% xsl based, generating these xmbean configurations for the necessary adapter classes. Thanks david jencks On 2002.08.28 18:56:22 -0400 Michael Bartmann wrote: > Hi, > > I am just tryaing to (ab-)use the XSLSubDeployer to load a JMS-Provider. > (with Adapter, Loader and Pool to feed into MDB), and my first tests > look quite promising (Branch_3_2). > The bla-jmsp.xml is not much shorter than the ordinary bla-service.xml > (at the moment there are more parameters than with datasources) > but it is less error prone, cause some mbean references are "resolved" > automagically. > And (of course) xsl deployment decouples userspace configuration from > version specific mbean details. > > It is a bit difficult to get everything flexible enough for any other > jms-provider (xml-parameters only tested it with my own jms provider), > but as with datasources it copies nested <depends> and such literally. > > Do you think such a gadget would fit into the jboss codebase? > > My main usecase is deploying of many jms-providers bundled with their > own MDBs inside their own ear-scope. > To get the above mentioned mbean-references right in a lot > of jboss-service.xml files (you must use different ObjectNames cause > everything lives in the same JMX server) is monkey work and xsl > should help a lot... > > Enjoy, > Michael > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Jabber - The world's fastest growing > real-time communications platform! Don't just IM. Build it in! > http://www.jabber.com/osdn/xim > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
