| Works fine in PDE but broken as standalone launcher? [message #313663] |
Wed, 21 March 2007 18:25  |
Eclipse User |
|
|
|
My apologies in advance if this has been answered already, but Google
was no help...
I'm working on a set of plugins that will eventually be part of an
Eclipse product (i.e. we're using Export > Plug-in Development > Eclipse
product).
I have a view that we're using for testing. If I run the plugins from
the PDE launcher then everything works: the branding, the test view, our
wizards, everything.
If I go through the export step the launcher gets created, all the
features & plugins are there, etc. When I actually use the launcher
Eclipse comes up, our branding is there, everything is looking good. I
go to Window > Show view > Other... and my new view category is there. I
expand our view category and the view is there, perfect.
I select the view, click OK and blammo:
Unable to create view: Plug-in
com.ibm.websphere.management.workbench.ui.test was unable to load class
com.ibm.ws.management.workbench.ui.test.views.ConfiguredConn ectorView.
java.lang.ClassNotFoundException:
com.ibm.ws.management.workbench.ui.test.views.ConfiguredConn ectorView
<rest of strack trace redacted; available on request>
I looked in the plugin directory & confirmed that the classes are there
in the bundle JAR. Clearly the plugin is being read, otherwise the
category wouldn't show up in the Show view dialog.
Does anyone have any idea what might be wrong? I've been tearing my hair
out for weeks now, twiddling every setting I can think of to no avail.
I'm pretty sure this is something I'm doing wrong but I just can't
figure out what it is.
Any help or pointers would be appreciated.
TIA,
JEC
--
Jeffrey E. (Jeff) Care carej@us.ibm.com
WebSphere Application Server Systems Management Development
|
|
|
| Re: Works fine in PDE but broken as standalone launcher? [message #313665 is a reply to message #313663] |
Wed, 21 March 2007 19:53  |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"Jeff Care" <carej@us.ibm.com> wrote in message
news:etsbde$ns0$1@utils.eclipse.org...
>
> I have a view that we're using for testing. If I run the plugins from the
> PDE launcher then everything works: the branding, the test view, our
> wizards, everything.
>
> If I go through the export step the launcher gets created, all the
> features & plugins are there, etc. When I actually use the launcher
> Eclipse comes up, our branding is there, everything is looking good. I go
> to Window > Show view > Other... and my new view category is there. I
> expand our view category and the view is there, perfect.
>
> I select the view, click OK and blammo:
>
>
> Unable to create view: Plug-in
> com.ibm.websphere.management.workbench.ui.test was unable to load class
> com.ibm.ws.management.workbench.ui.test.views.ConfiguredConn ectorView.
>
> java.lang.ClassNotFoundException:
> com.ibm.ws.management.workbench.ui.test.views.ConfiguredConn ectorView
> [...]
Make sure you've run eclipse with the -clean option, otherwise you may not
be running the most recent version of your deployed plug-in, which can be
very confusing.
Assuming that's not at issue, are you relying on any jar files, resources,
etc. that might not be in the same location at runtime as they are when
hosted in a workspace?
If you put some trace output in the constructor of the plug-in activator, is
it getting hit? CNFE can come from a failure to successfully load or
initialize the plug-in, which can happen if an exception is hit in the
constructor or startup().
Is there anything in the error log?
|
|
|
| Re: Works fine in PDE but broken as standalone launcher? [message #313669 is a reply to message #313665] |
Wed, 21 March 2007 23:32 |
| Eclipse User |
|
|
|
Walter Harley wrote:
> Assuming that's not at issue, are you relying on any jar files, resources,
> etc. that might not be in the same location at runtime as they are when
> hosted in a workspace?
It seems so obvious now (it always does), but the problem was that the
PDE launcher was using Java 5, while the default VM on this machine is
1.4.2; using the -vm flag with the standalone launcher solved the problem.
Thanks for getting me thinking in a different direction.
--
Jeffrey E. (Jeff) Care carej@us.ibm.com
WebSphere Application Server Systems Management Development
|
|
|
Powered by
FUDForum. Page generated in 0.07983 seconds
Home