Hi Anthony
I don't know if it is better, but another way is to copy the other jars into the Plug-in's jre\1.3.x\lib\ext subdirectory. I think this puts them before the classpath in any class search. However, it is easy to forget that the jars are still lurking in that directory, and I've sometimes spent a long time trying to track down problems related to old copies of the classes hiding out of sight there.
Regards
Matthew
Matthew,
Thanks for the advice. Unfortunately the way you sugguested will not work for me because the beans bridge stuff is just a small piece of the system that I will deploy. And I can't ask all the needed jars put into the Java plug-in's directory.
I know there is another way to setup the classpath just for the plug-in's. It is by using the Java Plug-in's console. But this looks work only in a development environment. I don't know how I can automate it as part of a product installation process.
I will deploy an enterpise applicaiton. So far I haven't found a better way to set the classpath than setting the environment variables (which is kind of rude).
Anthony