Hi Mark, and the list,
I ran into this as well, just two days ago. I tried putting the
new xerces.jar in WEB-INF/lib as well as in orion/lib, with no
effect. Finally I simply replaced the $ORION_DIR/xerces.jar with
the new one as you are thinking about. It worked nicely, and I
have not seen any ill effects from it yet. JDOM is very nice!
I guess your question is still valid though: Are there any bad
effects from doing this that will surface along the road that I
haven't seen yet? Something that is not triggered by my current
code? Or is Orion compatible with newer versions of Xerces?
Oh, almost forgot, I took the opportunity to replace the old
Xalan with the latest one as well...
Regards,
David.
On Fri, 15 Dec 2000 [EMAIL PROTECTED] wrote:
>
> Hi all,
>
> I am trying to use the most excellent JDom in my web app on Orion (1.3.9) and
> running into a little snag. For certain parts of its funcationality, JDom
> requires a very recent version of Xerces. The datestamp on it is Sep 1, 2000
> and it is approx 1,464KBs. As you can tell this is almost three times as big as
> the xerces jar that is shiped with Orion. I have tried to include the new
> xerces.jar in the /WEB-INF/lib directory of my war file but to no avail. Orion
> seems content to pick up its version of the jar (I imagine its a classloader
> thing).
>
> So my question is, is it ok to swap out Orion's old xerces.jar for the new one?
> Will I run into unforseen trouble down the road? Is there another way of
> solving this problem that i am unaware of or too ignorant to figure out?
>
> thanks a bunch...
> mark
>
> Mark R Mascolino
> The Procter & Gamble Co.
> [EMAIL PROTECTED]
>
>
>
>
>
--------------------------------Reach me by--------------------------------
- Email: [EMAIL PROTECTED], WWW: http://www.dtek.chalmers.se/~d0dak/ -
----------------------------------/David-----------------------------------
