How can I probe Java classes loaded with a custom class loader and so not in the CLASSPATH?
You will find that when you use “Open Associated Workspace” it imports only the jars in the class path and and so other classes that might be explicitly loaded do not appear in the Trace Setup. This can be easily remedied. So long as the class loader follows the standard model for class loader inheritance (e.g. classes loaded by that loader have visibility to classes loaded by the application class loader) this is trivial: • From the Main Workspace menu choose the Setup->Class Path menu item o bring up the Class Path dialog. • In the Class Path dialog, add the path(s) to the class directories or jar files you will be loading from. Note that this does not have to be where they will be loaded from at runtime. This just gets them into the Trace Setup. If there is no physical representation of the class available, you can use wildcards: • Select the Root Java Module in the Trace Setup; • Right click to bring up the context menu; • Choose Edit Wildcards to pen the >Edit Wildcards dialog.
