will report back.
Thanks,
J
From: Andreas Veithen
To: java-user@axis.apache.org
Sent: Monday, November 28, 2011 6:39 PM
Subject: Re: XML APIs JAR
Jack,
The point is that the entire argument behind solving the issue by
re-adding xml-apis to the WAR is f
seeable future.
> Thanks,
> J
>
> ____________
> From: Andreas Veithen
> To: java-user@axis.apache.org
> Sent: Monday, November 28, 2011 3:15 PM
> Subject: Re: XML APIs JAR
>
> Jack,
>
> If I understand this correctly, you are seeing exa
a few years and want to stick with it. We're tied to Websphere
for the foreseeable future.
Thanks,
J
From: Andreas Veithen
To: java-user@axis.apache.org
Sent: Monday, November 28, 2011 3:15 PM
Subject: Re: XML APIs JAR
Jack,
If I understand this co
Jack,
If I understand this correctly, you are seeing exactly the problem
described in the "Known issues" section, but you reject the proposed
solution on the grounds that IBM has told you that this won't fix the
problem, and without actually having tested the solution... If for a
problem with Axis
Thank you for the reply.
Most of that article does not apply to us. The Websphere Web Service feature
pack is not installed. The last paragraph entitled "Known Issues" matches our
problem exactly. 3 options are given:
1) Upgrade to most current Websphere fix pack - We're on the most current
Axis2 requires Java 1.5 and in that version, all the APIs defined by
xml-apis are already included in the JRE. Therefore xml-apis is no
longer necessary. Also note that the fact that the problem disappears
after adding xml-apis to the WAR doesn't necessarily mean that the
removal of the JAR in Axis
