As I see it, most of the work needs to be at deploy time, converting and processing the WL specific XML config files. If that's the case, then a few extra seconds (minute?) to start up isn't a great price to pay for the convenience. Any additional adaptor classes could sit inside a deploy time SAR/JAR, and so wouldn't need to clutter up the main tree at all.
Of course, INAHacker, so this might not be true ;) On Mon, May 13, 2002 at 05:01:15PM +0100, [EMAIL PROTECTED] wrote: > > Might it not make more sense to make a tool to extract the contents > of the jars, modify them to run on jboss, and produce a new jboss > compatible jar? That way the jboss code base wont get bogged down > with a load of stuff a lot of users will never go near. (don't take > it as a criticism, the idea is brilliant, I just thought this > approach could work well) Cheers, Simon -- "So you could say the greatest achievement of the Internet is that it turns nuclear war into nothing more than a series of routing errors." -- Mark Pesce _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
