I don't get it.. With the Boot class that I commit you can load all of JBoss's jar's off the network. If footprint is all you care about, you wont be able to beat the 7k boot.jar (unoptimized with debug).
I just tested the Boot class out, and it can even boot JBoss 2.4.4 So I don't know why you are killing yourself with providing an API to startup JBoss. The only case I find that helpfull would be in the case where you don't want to use the configuration system the jboss uses. Is that really what the embeded market is looking for? What kind of embeded are we talking about? Regards, Hiram >From: "marc fleury" <[EMAIL PROTECTED]> >To: "Jason Dillon" <[EMAIL PROTECTED]> >CC: <[EMAIL PROTECTED]> >Subject: RE: [JBoss-dev] 57 words... and a signature >Date: Mon, 25 Feb 2002 22:08:55 -0800 > >Ok 57 congratulations, although you are a bit skimpy on the how > >|The embedding changes provides integrators with a simple API to >|configure, start and stop JBoss. >|It will allow 99% of resources to be loaded off network, leaving the >|boot footprint small for >|limited devices. > >this is a valid requirement, I understand it and I see the need, it is a >new >feature. > >go right ahead. > >marcf > > >_______________________________________________ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
