Hi,
I'd like to change the sar format to be more in line with other compressed
non jar package formats:
a sar file will contain a META-INF/jboss-service.xml file (in its current
format) and any number of other compressed package files (jar, rar, ear
etc) in an arbitrary directory structure. When deploying a sar file, all
the contained packages will be added to the [appropriate, for right now
system as in ServiceLibraries] classpath with one classloader (so you can
deploy/undeploy the sar as a unit, but not the individual contained
packages).
If there are no objections I will include this in the round of
modifications I am working on, that make a local copy of sars before
unpacking/making classloaders, and share unpacking code with the
RARDeployer. I will also take care of converting the existing sars to this
format and renaming jsrs to sars.
Also, a question about j2ee deployment. (sorry I've only been looking at
j2ee pfd 3) There are a lot of classpath descriptions in section 8.3.1/2
etc. referring to using manifest classpath entries to figure out what to
include in the application classpath. However, it seems to me that if we
simply include _all_ packages found in the ear in the application
classpath, we will be satisfying this requirement without having to look at
these classpath entries. Is there a problem with this approach? Did I
miss something?
Thanks
david jencks
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
