Elias Biris writes: > thanks for the reply: > > The changes that you suggest do not sort my problem. Even without the jars in the >classpath the Beanshell cannot find the requested classes promptly enough. Also my >code base is already quite large.
I don't know why this should be so. It works quite promptly on my system for finding JDK source files. Does your application include more classes than the JDK? Also do you have the same performance problem with the import class command (C-c C-v C-z)? The only thing that the source file finder uses the Beanshell for is to find the qualified name of the class. If the Beanshell is the problem, you should see the same problem with all JDE commands that use the Beanshell, including the import command and field and method completion. > > On another aspect, the invocation of the beanshell is done via the command: > > >Q:\Dir_1;Q:\dir_2;Q:\dir_3;Q:\dir_4;f:/Programs/emacs/site_lisp/jde/jde-2.2.9beta9.1/java/bsh > >commands;c:/jdk1.3.1/lib/tools.jar;f:/Programs/emacs/site_lisp/jde/jde-2.2.9beta9.1/java/lib/checkstyle.jar;f:/Programs/emacs/site_lisp/jde/jde-2.2.9beta9.1/java/lib/jakarta-regexp.jar;f:/Programs/emacs/site_lisp/jde/jde-2.2.9beta9.1/java/lib/jde.jar;f:/Programs/emacs/site_lisp/jde/jde-2.2.9beta9.1/java/lib/bsh.jar > > > > Does that mean that the Beanshell picks all the jars in that classpath as well for >searching? Yes. >In that case removing the extraneous jars from my classpath does not make any >difference as they get picked up from the command It would make a difference because they would be included twice, once by you and once by the JDE (bsh.jar and jde.jar) and once by the JDK (rt.jar). I'm not convinced yet that the problem is the Beanshell. - Paul
