JSL> This is a classpath issue. ... Verify that the CLASSPATH being
JSL> passed to the beanshell contains the Jakarta.jar package. You
JSL> can find the classpath being passed to the beanshell in the *bsh*
JSL> buffer.
Ok, I've done a litte more debugging and found that if you set the
global classpath explicitly import works again. I know that in
previous versions of jde this code would use the CLASSPATH environment
variable if the jde-*-classpath variables were nil. Reading the
documentation I see:
...
If you do not set `jde-global-classpath', the JDE uses the
operation-specific classpath if it is set. If neither the global nor
the operation-specific classpath is set, the JDE does not generate a
-classpath argument for the operation, e.g., compile or run a Java
class. In this case, the operation uses the value of the CLASSPATH
variable if specified.
Is this: a) bug, b) a misunderstanding on my part, c) a change in
behavior?
Thanks,
--
Robert
