| Classloading - how to get plugin/ OSGi classloader log? [message #207168] |
Sun, 07 March 2004 19:20  |
Eclipse User |
|
|
|
Originally posted by: asdf.nospam.com
Hi,
I've got an Eclipse plugin which works well in 3m5 and am trying to diagnose
why it won't load in 3m6. The problem is that neither from the command-line
console/ debug options nor the debug tracing options, can I seem to get info
or detail as to what classes are being loaded and what classloaders/ path
sets
are being created.
Perhaps someone with more expertise in the runtime core/ OSGi/ plugin and
classloading areas could help me get tracing/ logging info to diagnose this
problem.
Some of the command-line and debug runtime-workspace options are giving me
tracing. But the org.eclipse.core.runtime/loader/debug options, in many
varied sets,
don't seem to produce any debug output; nor does the source in this area
seem to
have reference to these properties.
I'm now looking at the org.eclipse.osgi options and setting these gives me
some
information as to the creation of 'BundleData' and the files (directories)
these
reference. But I still can't see what JARs are being referenced, by what
classloaders,
to know what's going wrong!
It seems to me that plugins and classloading are a little less than trivial,
and I'd really
like to stop mucking around and get the straight-forward log information
which I need
to diagnose this problem.
I'd like to deliver a high-quality plugin without being subject to breakage
on future
Eclipse releases. It works on m5 and currently on m7 but for me to be
satisfied with
the quality A) I want to know why it doesn't load in m6 and B) I want to be
able to
diagnose what's going wrong if it breaks in future releases.
Though I am primarily interested in how to diagnose this, I'll give a little
detail on
the plugs (two of them); one is the Eclipse integration plug and a other is
a 'library'
plugin containing the main body of the application. The symptom is that my
Action
(delegates) fail to load a class from the library plugin on which they
depend. This
is a simple utility class which does not reference other classes or have any
<clinit>
which might be prone to secondary failure.
Any assistance in this area would be appreciated,
Regards,
Thomas
|
|
|
| Re: Classloading - how to get plugin/ OSGi classloader log? [message #207175 is a reply to message #207168] |
Sun, 07 March 2004 19:34  |
| Eclipse User |
|
|
|
Originally posted by: pascal.ibm.canada
Thomas,
M6 was the first integration of the new runtime in eclipse, and although
stable, it was containing a few bugs and the logging was poorly done.
Most of these things have been fixed in M7 and we are still working on
it, making sure we do not miss important exceptions. The tracing
facility should be re-enabled for M8.
Regarding your specific problem, I think that putting a breakpoint on
NoClassDefFoundError may help you to catch the error. Otherwise you can
also try to catch the BundleException.
Note that this should not be the regular way of debugging plugins.
Therefore fell free to enter bugs if you find that we are not properly
catching some exceptions and reporting errors.
PaScaL
random_uv wrote:
> Hi,
>
> I've got an Eclipse plugin which works well in 3m5 and am trying to diagnose
> why it won't load in 3m6. The problem is that neither from the command-line
> console/ debug options nor the debug tracing options, can I seem to get info
> or detail as to what classes are being loaded and what classloaders/ path
> sets
> are being created.
>
> Perhaps someone with more expertise in the runtime core/ OSGi/ plugin and
> classloading areas could help me get tracing/ logging info to diagnose this
> problem.
>
> Some of the command-line and debug runtime-workspace options are giving me
> tracing. But the org.eclipse.core.runtime/loader/debug options, in many
> varied sets,
> don't seem to produce any debug output; nor does the source in this area
> seem to
> have reference to these properties.
>
> I'm now looking at the org.eclipse.osgi options and setting these gives me
> some
> information as to the creation of 'BundleData' and the files (directories)
> these
> reference. But I still can't see what JARs are being referenced, by what
> classloaders,
> to know what's going wrong!
>
> It seems to me that plugins and classloading are a little less than trivial,
> and I'd really
> like to stop mucking around and get the straight-forward log information
> which I need
> to diagnose this problem.
>
> I'd like to deliver a high-quality plugin without being subject to breakage
> on future
> Eclipse releases. It works on m5 and currently on m7 but for me to be
> satisfied with
> the quality A) I want to know why it doesn't load in m6 and B) I want to be
> able to
> diagnose what's going wrong if it breaks in future releases.
>
> Though I am primarily interested in how to diagnose this, I'll give a little
> detail on
> the plugs (two of them); one is the Eclipse integration plug and a other is
> a 'library'
> plugin containing the main body of the application. The symptom is that my
> Action
> (delegates) fail to load a class from the library plugin on which they
> depend. This
> is a simple utility class which does not reference other classes or have any
> <clinit>
> which might be prone to secondary failure.
>
> Any assistance in this area would be appreciated,
>
>
> Regards,
> Thomas
>
>
|
|
|
| Re: Classloading - how to get plugin/ OSGi classloader log? [message #207218 is a reply to message #207168] |
Mon, 08 March 2004 01:53 |
| Eclipse User |
|
|
|
If I am not mistaken, M6 had a number of issues, that were resolved with M7.
Perhaps you should go to M7 and try it first, see if it works again.
"random_uv" <asdf@nospam.com> wrote in message
news:c2ge3n$lu7$1@eclipse.org...
> Hi,
>
> I've got an Eclipse plugin which works well in 3m5 and am trying to
diagnose
> why it won't load in 3m6. The problem is that neither from the
command-line
> console/ debug options nor the debug tracing options, can I seem to get
info
> or detail as to what classes are being loaded and what classloaders/ path
> sets
> are being created.
>
> Perhaps someone with more expertise in the runtime core/ OSGi/ plugin and
> classloading areas could help me get tracing/ logging info to diagnose
this
> problem.
>
> Some of the command-line and debug runtime-workspace options are giving me
> tracing. But the org.eclipse.core.runtime/loader/debug options, in many
> varied sets,
> don't seem to produce any debug output; nor does the source in this area
> seem to
> have reference to these properties.
>
> I'm now looking at the org.eclipse.osgi options and setting these gives me
> some
> information as to the creation of 'BundleData' and the files (directories)
> these
> reference. But I still can't see what JARs are being referenced, by what
> classloaders,
> to know what's going wrong!
>
> It seems to me that plugins and classloading are a little less than
trivial,
> and I'd really
> like to stop mucking around and get the straight-forward log information
> which I need
> to diagnose this problem.
>
> I'd like to deliver a high-quality plugin without being subject to
breakage
> on future
> Eclipse releases. It works on m5 and currently on m7 but for me to be
> satisfied with
> the quality A) I want to know why it doesn't load in m6 and B) I want to
be
> able to
> diagnose what's going wrong if it breaks in future releases.
>
> Though I am primarily interested in how to diagnose this, I'll give a
little
> detail on
> the plugs (two of them); one is the Eclipse integration plug and a other
is
> a 'library'
> plugin containing the main body of the application. The symptom is that my
> Action
> (delegates) fail to load a class from the library plugin on which they
> depend. This
> is a simple utility class which does not reference other classes or have
any
> <clinit>
> which might be prone to secondary failure.
>
> Any assistance in this area would be appreciated,
>
>
> Regards,
> Thomas
>
>
|
|
|
| Re: Classloading - how to get plugin/ OSGi classloader log? [message #208267 is a reply to message #207175] |
Tue, 09 March 2004 18:03 |
| Eclipse User |
|
|
|
Originally posted by: asdf.nospam.com
Hi Pascal, also Spiderman,
Thanks for your help. It sounds like we may be able to regard the
issue with M6 as being transitory only, and wait to test reliability
with the M8 release.
Regards logging my interest would be to see what ClassLoaders
and jar lists/ delegation structures were being created; as well as to
diagnose what classes are being searched & loaded/ failed.
As you're probably aware Java classloading is difficult to diagnose
due to Sun's weak design of delegation and loader tree structure. So
adding robust logging/ tracing is important for the platform to meet
engineering quality.
Thanks again and best regards for your work on the Eclipse product,
Regards,
Thomas
|
|
|
Powered by
FUDForum. Page generated in 0.03515 seconds
Home