| ClassNotFound Exception [message #287618] |
Tue, 05 July 2005 09:58  |
Eclipse User |
|
|
|
I hope someone can help me. I have been trying to export my RCP from
eclipse. My RCP executes just fine in Eclipse. When I try to execute it
after I have exported it I receive from BundleLoader, ClassNotFound
Execpetions.
Is there a way to debug what is going on? All my class files are there in
the plugins directory. I am using Eclipse 3.1 with Java 1.5b4.
|
|
|
|
|
| Re: ClassNotFound Exception{FIXED] [message #287809 is a reply to message #287762] |
Thu, 07 July 2005 04:17  |
| Eclipse User |
|
|
|
Rafael Chaves wrote:
> Kevin wrote:
>
>> The moment I added a second plugin, which the first plugin required,
>> to that RCP I could no longer export the plugin or run it. I could
>> still execute it with in the Eclipse Framework using Run.
>
>
> Where was the dependency between the first and second plug-in specified?
> If it was done in the plugin.xml, that would explain it. Once you have a
> MANIFEST.MF, the plugin.xml is used only for declaring extensions and
> extension points. Any runtime-relate information is completely ignored.
>
> Otherwise, if you have steps to recreate the original problematic
> scenario, by all means report it on bugzilla.
I can at least report the same experiences (problems) with the new OSGI
plugin manifest. We are working in a team, which since two days used the
old pure plugin.xml manifest and our product export worked fine all the
time.
Now a collegue started the first time to add a new plugin using the new
(recommended) OSGI plugin manifest and we were not able to realize an
exported RCP which successfully runs - ClassNotFound or resolution
problems all the time!
It might be worth adding that we did not touch the plugin.xml directly
to express dependencies, but used the dependencies page for that.
Although it is a good idea to provide a conversion utility **to** the
new osgi manifest, at least a reverse conversion to the pure 3.0
plugin.xml would be great. I fear, we have to do the same thing as the
OP to convert the new osgi manifests to the pure plugin.xml format....
Greetings from Bremen,
Daniel Krügler
|
|
|
| Re: ClassNotFound Exception{FIXED] [message #287842 is a reply to message #287809] |
Thu, 07 July 2005 10:10 |
| Eclipse User |
|
|
|
Originally posted by: chaves-do-not-spam.inf.ufsc.br
Note that all plug-ins end up having OSGi manifests (this was true even in
3.0). If you don't provide one, one will be automatically generated for
you during startup. There is no loss of functionality in doing that.
What may be occurring is that users are not familiar with the manifest
format (which is more complicated, because it is more powerful), so
mistakes tend to happen more often due to manual tweaking (not saying this
is your case).
Of course, it is not impossible that the tooling for composing or
generating manifests (which includes components from the OSGi runtime)
have issues. If you found any, please let the team know by reporting it on
Bugzilla.
Rafael
Daniel Krügler wrote:
> I can at least report the same experiences (problems) with the new OSGI
> plugin manifest. We are working in a team, which since two days used the
> old pure plugin.xml manifest and our product export worked fine all the
> time.
> Now a collegue started the first time to add a new plugin using the new
> (recommended) OSGI plugin manifest and we were not able to realize an
> exported RCP which successfully runs - ClassNotFound or resolution
> problems all the time!
> It might be worth adding that we did not touch the plugin.xml directly
> to express dependencies, but used the dependencies page for that.
>
> Although it is a good idea to provide a conversion utility **to** the
> new osgi manifest, at least a reverse conversion to the pure 3.0
> plugin.xml would be great. I fear, we have to do the same thing as the
> OP to convert the new osgi manifests to the pure plugin.xml format....
> Greetings from Bremen,
> Daniel Krügler
|
|
|
|
|
|
| Re: ClassNotFound Exception{FIXED] [message #287993 is a reply to message #287871] |
Mon, 11 July 2005 05:25 |
| Eclipse User |
|
|
|
Hello Rafael Chaves and Rich Kulp,
thank you very much for your efforts. Taking your proposals into account
I finally found the differences and thus the missing entries by
comparison with the mentioned generated manifest files.
Interestingly in the corresponding manifest files the
Bundle-ClassPath entry was completely missing. In the moment I can't say
whether this was explicitly done by the programer or simply was the
default setting.
Luckily export now works!
Daniel
|
|
|
Powered by
FUDForum. Page generated in 0.04387 seconds
Home