The problem could be that WebSphere has an old version of xerces in its
classpath.
Did you change the static classpath of websphere ?
Try to delete the old xerces entry in the admin.config file of websphere and
add two new entries at the beginning for the fop versions of xerces and
xalan. I got it
einen
@nexum.de> cc:
Subject: AW: Problem with
[EMAIL PROTECTED] wrote:
I made the changes but still getting the same error.
It's driving me crazy. ANy help will be greatly appreciated.
Usually, WebSphere 3.5 comes with an ancient XML tool set.
You have to put Xerces-1.2.3.jar and Xalan-2.0.0.jar into the
classpath before the old tools.
If you
n" To: [EMAIL PROTECTED]
<[EMAIL PROTECTED]cc:
oo.de> Subjec
<[EMAIL PROTECTED]cc:
oo.de> Subject: Re: AW: Problem with servlet
[EMAIL PROTECTED] wrote:
Thanks for your help. I got the following from my websphere administrator.
We've tried to do the changes as mentioned at the end of your e-mail
(changing jars and updating admin.config), but the IBM admin server can't
restart.
If we remove xml4j.jar and the others and repl
: Problem with servlet
I got fop successfully running on websphere 3.5 just by adding saxon.jar at
the first place in the com.ibm.ejs.sm.adminserver.classpath record of
admin.config file (beware about strange syntax \:/), here is my line
(websphere 3.5.6, NT4
