>
> Can you give me a usecase where it is useful to add jars to the AS
> classpath (JBOSS_CLASSPATH/RUN_CLASSPATH in the run.sh scripts) and
> not just add them into lib folder ?
>
> Asking since it is a constant "battle" in the tooling between users
> who want full control and those who just want the server startup to
> *always* work.
> Before we go add a bunch of complex code to handle this I would like
> to know of a use case that merits that users can set the classpath at
> startup time instead
> of just adding it into lib.
>
> The usecases I have come up with I'm not sure if they are valid:
>
> 1) allows me to put stuff on the global classpath of the server
> without manipulating a possibly read-only lib directory
Something that I just remembered. If lib directory is read only, you
can always use -Djboss.lib.url to define a new path for the root lib
directory where you're able to write to it:
http://www.jboss.org/community/docs/DOC-10730 Yes, but it would still require a
full copy - just adding one jar to the
classpath is IMO simpler.
-max