|
Hi,
Patrick states in the Inline::Java doc about the CLASSPATH configuration option:
This CLASSPATH will only be available through the user classloader. To set the CLASSPATH globally (
+which is most probably what you want to do anyways), use the CLASSPATH environment variable.
and that's exactly where we ran into a problem. In the concrete case all but one part of the software worked well with the CLASSPATH configuration option; the one part which failed was a framework which did not found its classes and debugging into it we found that it just had InlineJavaServer on its classpath.
While setting the classpath through the env variable solved it I do not quite understand the constraint here -- what puzzles me most is the term "globally". Now that I realized that there are some subleties connected to that I would be happy about some enlightenment so that I understand why it works this way and not the other way.
Thanks ... Christian
|
