On Tue, 21 Nov 2000, [EMAIL PROTECTED] wrote:
> Hello,
>
> After moving to JDE 2.2.6beta5, I am having a weird bean shell error
> when trying to use the jde-show-class-source function:
>
> Beanshell expression evaluation error.
> Expression: jde.util.JdeUtilities.buildClassList(
>
"C:\jdk1.2.2\jre\lib\rt.jar;\users\gberche\latestBuild\Xtrim\src;\users\gber
che\latestBuild\Xtrim\lib\HTTPClient.zip;\users\gberche\latestBuild\Xtrim\li
b\Stingray\Stingray.zip;\users\gberche\latestBuild\Xtrim\lib\kevin.jar;\user
s\gberche\latestBuild\Xtrim\lib\Cryptix;\users\gberche\latestBuild\Xtrim\lib
\xml\xml.jar;\users\gberche\latestBuild\Xtrim\lib\jWrap\jWrapRuntime.jar;\us
ers\gberche\latestBuild\Xtrim\lib\jWrap\FlexibleLayout.jar;\users\gberche\la
testBuild\Xtrim\lib\JNL\Classes;c:/Tools/jakarta-tomcat/lib/servlet.jar;c:/T
ools/jakarta-tomcat/lib/jasper.jar");
> Error: // Error: Error parsing input: bsh.TokenMgrError: Lexical
> error at line 2, column 43. Encountered: "j" (106), after :
> "\"C:\\"
>
> Would this come from my path including some backslashes? Should I
> update to Unix-style slashes? I was trying to keep native path
> separators '\' so that the buggy's Sun compiler ( version <1.2)
> would get native ones and be happy. I could not figure out if this
> was wrong to set such path in JDE.
>
>
> Would my problem be linked to the modification made to
> jde-wiz-update-class-list made in the beta14 release or simply a
> misconfiguration from my side (it works fine with jde-2.2.4)
>
> * The jde-wiz-update-class-list command now includes
> jde-global-classpath in the updated list. Thus, it is no
> longer necessary to restart the beanshell when switching
> projects.
>
>
> Following is the complete output of the *Messages* buffer from emacs
> startup.
>
> For information about the GNU Project and its goals, type C-h C-p.
> Loading c:/users/gberche/latestBuild/Xtrim/src/prj.el (source)...
> Loading c:/users/gberche/latestBuild/Xtrim/src/prj.el
> (source)...done Loading lazy-lock... Loading lazy-lock...done
> Loading thingatpt... Loading thingatpt...done Starting the
> BeanShell. Please wait... Loading
> c:/users/gberche/latestBuild/Xtrim/src/prj.el (source)... Loading
> c:/users/gberche/latestBuild/Xtrim/src/prj.el (source)...done
> Fontifying AccountLockedException.java... Fontifying
> AccountLockedException.java...
(regexps.........................................)
> Loading c:/users/gberche/latestBuild/Xtrim/src/prj.el
> (source)...done Rescanning classes... Beanshell expression
> evaluation error. Expression: jde.util.JdeUtilities.buildClassList(
>
"C:\jdk1.2.2\jre\lib\rt.jar;\users\gberche\latestBuild\Xtrim\src;\users\gber
che\latestBuild\Xtrim\lib\HTTPClient.zip;\users\gberche\latestBuild\Xtrim\li
b\Stingray\Stingray.zip;\users\gberche\latestBuild\Xtrim\lib\kevin.jar;\user
s\gberche\latestBuild\Xtrim\lib\Cryptix;\users\gberche\latestBuild\Xtrim\lib
\xml\xml.jar;\users\gberche\latestBuild\Xtrim\lib\jWrap\jWrapRuntime.jar;\us
ers\gberche\latestBuild\Xtrim\lib\jWrap\FlexibleLayout.jar;\users\gberche\la
testBuild\Xtrim\lib\JNL\Classes;c:/Tools/jakarta-tomcat/lib/servlet.jar;c:/T
ools/jakarta-tomcat/lib/jasper.jar");
> Error: // Error: Error parsing input: bsh.TokenMgrError: Lexical
> error at line 2, column 43. Encountered: "j" (106), after :
> "\"C:\\"
>
>
> Then when I try to use other bean-shell related commands such as
> "show symbol at point" I get evaluation errors: Error evaluating
> Lisp result of Java expression evaluation. Java expression:
> jde.util.JdeUtilities.getQualifiedName("AccountLockedException");.
> Java evaluation result: .
>
> Any idea on this problem are welcome!
Of course! Stupid me! Because I'm using UNIX I don't have this problem
myself. I'll fix it ASAP and send a patch (tomorrow).
Paul : I'm having problems posting to this list since I changed my
E-Mail address. I have to figure out under which address I'm
subscribed and change it... but for now, could you please forward my
answer to the list? Thanks!
--
Raffael Herzog
[EMAIL PROTECTED]
May the penguin be with you!
