Bug 20652 - CNFEs for other module's classes
CNFEs for other module's classes
Product: obsolete
Classification: Unclassified
Component: languages
PC Linux
: P2 (vote)
Assigned To: issues@ide
Depends on:
  Show dependency treegraph
Reported: 2002-02-19 07:34 UTC by Svata Dedic
Modified: 2008-08-01 15:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT


Note You need to log in before you can comment on or make changes to this bug.
Description Svata Dedic 2002-02-19 07:34:46 UTC
I've tried to use Scripting module to inspect state of (another) module I've
debugged. It seems that classes, which are in other modules are not accessible
to the scripting engines, they does not even recognize their names.
Comment 1 Milos Kleint 2002-02-19 07:47:58 UTC
did you have the sources of other modules mounted? 
or you expect to have all the Nb modules accessible?
Comment 2 Milos Kleint 2002-02-19 07:48:47 UTC
btw which engine did you use? beanshell/dynamicjava/jython?
Comment 3 Svata Dedic 2002-02-19 08:17:36 UTC
I tried to use BeanShell and DynamicJava.
I didn't mount the sources, will it help ? From the module's code I
thought that it uses BeanShell from modules/ext though the scripting
module's classloader, which does not see other modules or the code
inside FileSystems.
Comment 4 mvdb 2002-02-19 11:26:54 UTC
The only scripting language in nb that supports using the FileSystem 
as a classpath is currently DynamicJava. It builds the classpath 
dynamically and adds it to the scripting classpath.
Comment 5 Milos Kleint 2002-03-12 13:46:22 UTC
if we update to beanshell 1.2b4 (maybe earlier, I didn't check), we
could add the mounted filesystems to the classpath as well, the
current version bundled with Netbeans doesn't allow that..
Comment 6 Milos Kleint 2002-03-25 14:46:57 UTC
updated the beanshell support to use the 1.2b5 jar as found on
Beanshell's homepage (as discussed with Pat - owner of the Beanshell
project - that's the most uptodate stable version)

I've added the code that adds the mounted filesystems to the classpath
of the beanshell interpreter. I'm not sure it will exactly solve your
problem but I don't think it's ok to access the Nb internals from
within the scripting module.. the same was the case with the
filesystems in the early days and was removed from there some time ago

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo