Eclipse Community Forums: Rich Client Platform (RCP) » Tools for Debugging Class Loading within RCP

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » Tools for Debugging Class Loading within RCP

Show: Today's Messages :: Show Polls :: Message Navigator

Tools for Debugging Class Loading within RCP [message #436415]

Wed, 07 September 2005 18:54

joel

Messages: 17
Registered: July 2009

Junior Member

I've been working on wrapping the opengl library JOGL as an eclipse
RCP plugin based upon the configuration of the SWT Opengl plugin.
Basically took the SWT OpenGl plugin, replaced the jars, dlls,
and .so's and renamed all the packages and such in the manifest.mf,
plugin.xml, and fragment.xml files.

When I was all done, and used Require-Bundle bundle option to refer
to my new net.java.games.jogl plugin, it worked fine on Windows and
I could do JOGL rendering

The problem came on porting to linux. On that side, it gets "class
not found" errors when it tries to reference types from JOGL. Just
as with SWT Opengl, I've put the jogl.jar and associated shared
libraries into the fragment and using the plugin info button on
the rcp application's about dialog, I can see that the plugin,
and the fragment, are both listed as "resolved".

What next step can I take to trace what is happening? Is there
some way to turn on verbose output for the osgi classloader?

thanks,
Joel

Report message to a moderator

Re: Tools for Debugging Class Loading within RCP [message #436417 is a reply to message #436415]

Wed, 07 September 2005 22:40

joel

Messages: 17
Registered: July 2009

Junior Member

Answerwing my own questions:

1. My linux-side plugin fragment wasn't working because apparently
the classloader system on the linux side still requires the
<runtime> info in the fragment.xml file while the windows side
seems to rely solely on the manifest.mf file. Adding in the runtime
export stuff into the fragment .xml got it working for me.

2. I found my way to this by reading the voluminous debug output
provided by copying the .options file out of the org.eclipse.osgi
plugin into my RCP app's root directory and turning on most all
of the monitoring and tracing options. Basically I set all the
"false" values to "true" except for the one about "wiring" because
that caused a crash. Then I ran my rcp app with the "-debug" option.
This made for massive amounts of debug info on the stdout about
how things were being resolved and loaded.

joel

Report message to a moderator

Previous Topic:	Jobs API Feedback
Next Topic:	short cut key for saving the project is not working(ctrl+s)

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Dec 10 15:58:16 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter