Xerces Classpath Issue

Discussion in 'Java' started by Praveen Chhangani, Oct 17, 2003.

  1. 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
     
    Praveen Chhangani, Oct 17, 2003
    #1
    1. Advertising

  2. 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
     
    David Zimmerman, Oct 18, 2003
    #2
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.

Share This Page