(comments to all proposals...) I do something like this disabled directory also, but not as good... I like the disabled.
Some things have mbeans that really don't need configuration, just lifecycle services. These are good candidates for the current sar structure. TransactionManager comes to mind. Switch tm's with no code bloat just by changing jbosstm.sar to tyrextm.sar. Native libraries are loaded by MainDeployer out of any package it unpacks (sar, ear, rar). Maybe it should deploy bare libraries? I don't know. As I mentioned in another recent post, we could have an external xml config and still package all the jars specific to a (large-scale) service in a sar with an empty (no mbeans) jboss-service.xml. This would package an easily configurable service in 2 files rather than count(jars) + 1. Maybe we could allow sars with no jboss-service.xml to simply have their classes loaded. Thanks david jencks On 2002.02.28 07:30:50 -0500 James Cook wrote: > I usually end up creating a "disabled" directory under the deploy > directory. In here I put the clustering xml along with the JBossMQ > stuff, and the HSQL DB items. Perhaps this kind of packaging would make > it clearer that these services exist, but are simply not activated. > > At some point someone will want to write a slick management GUI for > jBoss. It would be convenient if the XML descriptor and dependent > classes are stored in a standard location for discovery. It seems like > the SAR is the proper storage mechanism for these deployable services. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] On > > Behalf Of marc fleury > > Sent: Thursday, February 28, 2002 4:31 AM > > > The classes should go under a "classes" directory (today > > /lib/ext/) which is centralized and will make central > > downloading of files simple. > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
