Eclipse Community Forums: Eclipse Platform » Class path order when running Eclipse plugin

Home » Eclipse Projects » Eclipse Platform » Class path order when running Eclipse plugin

Class path order when running Eclipse plugin [message #78614]

Thu, 19 June 2003 15:21

Eclipse User

Originally posted by: markus_huebscher.hotmail.com

I've written a plugin that uses the Saxon XSLT Processor. Saxon reimplements
the package javax.xml.transform, which is also present in Sun's JDK 1.4.1.

When I run the workbench with my plugin using JDK 1.4.1, Eclipse uses the
implementation of the package in JDK instead of Saxon's and my plugin does
not work corretly. If I start the workbench with IBM's JRE 1.3, which
doesn't implement the package, everything works fine.

I do I get Eclipse to use the right package implementation??

I've tried playing around with the Build Order in the properties of the
project, but it doesn't solve my problem.

Any suggestions greatly appreciated.

Markus Huebscher

Re: Class path order when running Eclipse plugin [message #78677 is a reply to message #78614]

Thu, 19 June 2003 17:06

Eclipse User

> I've written a plugin that uses the Saxon XSLT Processor. Saxon
reimplements
> the package javax.xml.transform, which is also present in Sun's JDK 1.4.1.
>
> When I run the workbench with my plugin using JDK 1.4.1, Eclipse uses the
> implementation of the package in JDK instead of Saxon's and my plugin does
> not work corretly. If I start the workbench with IBM's JRE 1.3, which
> doesn't implement the package, everything works fine.
>
> I do I get Eclipse to use the right package implementation??
>
> I've tried playing around with the Build Order in the properties of the
> project, but it doesn't solve my problem.
>
> Any suggestions greatly appreciated.
As far as I've learned I would track it to this issus:

JDK 1.4.1 comes with the library. Therefore it is up to the class loaders
how
to load classes. Therefore you have to bypass it (which is not really an
option).

Using JRE 1.3 makes it look right from the configuration point of view.
Therefore
I guess the classloader preferres (or had already loaded) classes of the
javax.xml.*
packages. Maybe the classloader only loads external libraries when the class
could not be found somewhere else.

Onething you might try is specifying the library in a classpath when
starting up
eclipse. It depends on the class loading mechanism used by eclipse/java.

Another rule of thumb would be reprogramming your application parts by
using the SDK 1.4.1 implementation of javax.xml... . (would be hit you
anyway).

My Conclusion:
1. try the additional classpath when starting eclipse.
1b) Someone has a better idea which works;)
2. Use JDK 1.3 until your application uses the library of Java 1.4.1

Hope I could help a bit,

Martin (Kersten)

Re: Class path order when running Eclipse plugin [message #78723 is a reply to message #78677]

Thu, 19 June 2003 17:33

Eclipse User

Originally posted by: george.sync.ro

Hi Markus,

If your plugin depends on Saxon and does not work with other Transformer
implementations then skip JAXP and instantiate directly the Saxon
implementation classes.

Hope that helps,
George
------------------------------------------------------------ -
George Cristian Bina mailto:george@sync.ro
COO - sync.ro
Phone +40-(0)251-461480, +40-(0)251-461481
Fax +40-(0)251-461482
Mobile +40-(0)723-224067
SyncRO Soft srl, Bd N. Titulescu 170, Craiova, 1100 - Romania
http://www.sync.ro
<oXygen/> XML Editor - http://www.oxygenxml.com/

Previous Topic:	ComboBoxPropertyDescriptor
Next Topic:	More Action Enablement

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 17 18:11:22 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter