Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > Java > Xerces Classpath Issue

Reply
Thread Tools

Xerces Classpath Issue

 
 
Praveen Chhangani
Guest
Posts: n/a
 
      10-17-2003
Folks,

I have run into a bit of an issue, so let me see if I can explain this
to the best of ability.

I currently have a thick application (java) that contains mini java
programs within (plug-ins). Each plugin requires a set of .jar files
that it makes use of. I have a particular plug-in (mini java program)
that calls an EJB to generate .pdf files. - The developers who
support the EJB have upgraded the xerces.jar to a newer version and
this requires that we upgrade our classpath to contain the new
xerces.jar package as well. The problem is that when we do that we
have other java plug-ins with the thick java application that start
throwing out exceptions. The reason for this is because IBM
apparently hard-coded a lot of the stuff in the older xerces.jar,
whereas in the new xerces.jar a lot of the hard-coded code has been
removed.

So here's the question of the day, how to I fix this? I have come up
with a quick fix for this and that is to run separate instances of the
thick java application, however that is not something I want to do for
too long.

Can anything think of a way to fix this issue? Any input is
appreciated!

Thanks,
Praveen
 
Reply With Quote
 
 
 
 
David Zimmerman
Guest
Posts: n/a
 
      10-17-2003
Load your plug-ins each with its own classloader. That way each can use
the version of xerces it needs. Look at URLClassLoader

Praveen Chhangani wrote:

> Folks,
>
> I have run into a bit of an issue, so let me see if I can explain this
> to the best of ability.
>
> I currently have a thick application (java) that contains mini java
> programs within (plug-ins). Each plugin requires a set of .jar files
> that it makes use of. I have a particular plug-in (mini java program)
> that calls an EJB to generate .pdf files. - The developers who
> support the EJB have upgraded the xerces.jar to a newer version and
> this requires that we upgrade our classpath to contain the new
> xerces.jar package as well. The problem is that when we do that we
> have other java plug-ins with the thick java application that start
> throwing out exceptions. The reason for this is because IBM
> apparently hard-coded a lot of the stuff in the older xerces.jar,
> whereas in the new xerces.jar a lot of the hard-coded code has been
> removed.
>
> So here's the question of the day, how to I fix this? I have come up
> with a quick fix for this and that is to run separate instances of the
> thick java application, however that is not something I want to do for
> too long.
>
> Can anything think of a way to fix this issue? Any input is
> appreciated!
>
> Thanks,
> Praveen


 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
.classpath file instead of the CLASSPATH Environment variable. dontspammenow@yahoo.com Java 2 03-02-2008 08:19 AM
problem compiling project, classpath in xml ".classpath" "<classpathentry...>" jameshanley39@yahoo.co.uk Java 2 03-02-2007 12:37 PM
Upgrade of Xalan 1.2.2 and Xerces 1.4.4 to Xalan 2.6 and Xerces 2.6.2 cvissy XML 0 11-16-2004 07:06 AM
while using javac -classpath some.jar some.java (Where does classpath get stored?) Gabe Java 3 08-27-2004 07:02 PM
CLASSPATH, -cp and -classpath misunderstanding? Flip Java 3 02-09-2004 10:09 PM



Advertisments