|Issue with loading bundles from project directories with embedded equinox. [message #997760]
||Tue, 08 January 2013 12:25
| Michael Yara
Registered: July 2009
We have normal Java application that runs embedded Jetty and several instances of Equinox via the servlet bridge.
In order to streamline development I have set up a development mode in our application that causes our bundles to be loaded from the bundle project directories in our workspace so we do not have to export the bundles each time we make a change.
The issue I have run into is that when these bundles are loaded from the directory they throw ClassNotFoundExceptions for all the classes in the bundles. I have resolved this by adding the bundle's "bin" directory to the bundle's manifest classpath. This causes the bundles to load properly and our application to work, however all the linking in Eclipse is somewhat broken. For instance if I hit F3 on a class name to get to its definition it will open the class in the editor but it is not editable due to the fact that the .class is opened not the .java file. Attaching the source does work but still leaves the class un-editable.
My main question is how does eclipse accomplish running bundles out of the project directory without the need for bin to be on the bundle classpath? When I added bin to the bundle classpath is when I start to have issues with the linking in Eclipse. If I can get around the need for the "bin" directory in my classpath I should not have the linking issues.
It seems as if I am missing some sort of configuration option that eclipse uses but I cannot seem to determine what that is.
If anyone can shed some light on this issue it would be greatly appreciated.
[Updated on: Tue, 08 January 2013 12:45]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01655 seconds