> Good question that is something I am still thinking about
> here is my current understanding (disclaimer: research).
>
> SARs are nice from a packaging standpoint, (i.e. you ship a
> SAR to a client he can just drop it in his server at run
> time) but a nightmare from a jar creation/xml file editing
> standpoint.
>
> My favorite way to do this, and what I have been saying from
> the VERY BEGINNING, (do a search on the early SAR
> propositions) is let's put the plain xml file with either 1-
> the classes in lib/ext (we could hot deploy and monitor
> lib/ext actually) 2- a plain URL that references a file on
> the system or on a webserver, so you would just put the XML
> file and say classpath codebase=file:/myclassesinbulk/.
>
This wasn't in David J's stuff originally I just added support for it
recently.
So just to clarify currently you can use...
to add directory (so class files and resources in directory are accessible)
<classpath codebase="directoryURL" />
to add specific jars in directory
<classpath codebase="directoryURL" archives="jar1.jar,jar2.zip" />
to add all jars in directory
<classpath codebase="directoryURL" archives="*" />
> I HAD BUILD THAT SUPPORT IN THE FIRST VERSION ON RH I will
> make sure it is still there (I think it is actually). Then
> the *preferred* way is to just drop the xml snippet or add it
> to the base jboss-service.xml if you know it is going to be
> part of the server always.
> The only advantage of doing the snippet would be monitoring
> and reconfiguring the service based on this. Could be useful.
>
It is for development, which is why I put it back in.
David
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.303 / Virus Database: 164 - Release Date: 11/24/2001
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
