|
From: <jas...@ma...> - 2004-07-09 13:17:30
|
On 9 Jul 2004, at 14:09, Dmitriy Kopylenko wrote: > >Talking with David Blevins & Dain from Geronimo at JavaOne they were > lamenting on this nested-jar stuff, where it might be nice to have a > real simple deployment unit - maybe >just called 'jar' or something - > SPAR? for SPring ARchive? :). Anyways the jar could look something > like... > >> >> /META-INF/ >> applicationContext.xml (or spring.xml) >> /APP-INF/ >> lib/ >> commons-logging.jar >> someOtherRequiredJar.jar >> com/foo/MyClass.class >> ... >> >> i.e. we could include dependent jars inside the deployment unit in a >> special directory, along with any other resources & configurations - >> then we could just drop this jar in a directory. Or we could just use >> an unpacked directory version of this jar as well. > > > SPAR sounds cool ;-) :) > So the structure of the unit would look like this: > > /META-INF/ > applicationContext.xml (or spring.xml) > /APP-INF/ > lib/ > commons-logging.jar > someOtherRequiredJar.jar > applicationClasses.jar Was thinking you'd include your code as just .class files inside the spar, only including child jars for dependent libraries. i.e. lets minimise unnecessary jar-ing up if we can. > /WEB-INF/? > html resources? > jsp? > lib/ > some.properties? > other servlet classpath resources? Could do - though if you want WEB-INF stuff you could just use a WAR. (Though there's no reason why we can't have special files which Geronimo knows to look for in WARs for Spring applicationContext.xml etc. James ------- http://radio.weblogs.com/0112098/ |