On Fri, Feb 14, 2003 at 01:00:54PM -0500, Shank, Gary wrote: > Thanks for the reply. As for the beanshell problem, the printStackTrace > results are: > unable to load language: beanshell: > java.lang.NoClassDefFoundError: com/ibm/bsf/util/BSFEngineImpl > at java.lang.ClassLoader.defineClass0(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:488) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:106) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:243) > at java.net.URLClassLoader.access$100(URLClassLoader.java:51) > at java.net.URLClassLoader$1.run(URLClassLoader.java:190) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:183) > at javax.management.loading.MLet.findClass(MLet.java:775) > at java.lang.ClassLoader.loadClass(ClassLoader.java:294) > at java.lang.ClassLoader.loadClass(ClassLoader.java:250) > at org.apache.bsf.BSFManager.loadScriptingEngine(Unknown Source) > at org.apache.bsf.BSFManager.exec(Unknown Source) > at > com.sterlingcommerce.woodstock.services.bsf.BSFImpl.processData(BSFImpl.java > :136)
Ah. An easy one... In the BSF 2.3 that was released to Apache, the class hierarchy has changed. We no longer use com.ibm.bsf..., but instead use org.apache.bsf... The BeanShell engine you are using is compiled against the older BSF, with the older class hierarchy. I would file a bug w/ the BeanShell developers, asking them to modify their engine to use the new hierarchy, or else to submit their engine for inclusion. Victor -- Victor J. Orlikowski | The Wall is Down, But the Threat Remains! ================================================================== [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
