Hi folks!
So deployment.util.Utils.getClassLoader() sets up a classloader with a
classpath consisting of:
- The passed root dir (i.e. modules/ or services/)
- The "lib" and "Lib" subdirs
- Any jar files found in "lib"/"Lib"
1) Who uses "Lib/" with a capital L? Do we need this?
2) Should the
Hi Glen,
Please see my comment inline.
> Hi folks!
>
> So deployment.util.Utils.getClassLoader() sets up a classloader with a
> classpath consisting of:
>
> - The passed root dir (i.e. modules/ or services/)
> - The "lib" and "Lib" subdirs
> - Any jar files found in "lib"/"Lib"
Yes correct.
>
> 1
Hi Deepal!
Deepal Jayasinghe wrote:
So deployment.util.Utils.getClassLoader() sets up a classloader with a
classpath consisting of:
- The passed root dir (i.e. modules/ or services/)
- The "lib" and "Lib" subdirs
- Any jar files found in "lib"/"Lib"
Yes correct.
1) Who uses "Lib/" with a capi
>
> The lib/ directory should contain jars, not classes directly, right?
> I agree that lib/*.jar should be added to the classpath, but I was
> asking about lib/ itself. Right now if you had
> lib/org/apache/axis2/SomeClass.class, that class would be available,
> which I do not think is appropri
