You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Jerry Cole <je...@vioma.com> on 2004/02/11 19:02:45 UTC
Problem with WSDL Validation when Generated by Apache-Axis Web Publisher.
Hi.
I'm checking out the Axis Web Publisher that runs as a webapp under
Tomcat. I'm using Axis 1.1 and Tomcat 5.0.
The WSDL generated by the AdminClient looks okay to me (I am not an
expert) and works when called through the Axis client libraries
(WSDL2Java).
However, a proxy server that we have complains that the WSDL is invalid
and I was able to verify that it is considered invalid by a few WSDL
validators I googled (e.g. the one under Tools at www.xmethods.net).
Unfortunately, these validators don't tell you anything about what's
wrong. ("Can't parse" is the usual message. It is NOT a problem with
finding the location.)
Even the Version example's WSDL (that comes with Axis) is considered to
be invalid by these tools.
Any thoughts as to why these are invalid and how to get around it?
Jerry Cole
206.769.9312 - mobile
206.374.4603 - office
206.720.6945 - home office
Problem with WSDL Validation when Generated by Apache-Axis Web Publisher.
Posted by Jerry Cole <je...@vioma.com>.
Sorry to re-send this note, but has no one had a problem with 3rd party
WSDL validators not liking WSDL generated by the Axis WS Publisher
running under Tomcat?
Hi.
I'm checking out the Axis Web Publisher that runs as a webapp under
Tomcat. I'm using Axis 1.1 and Tomcat 5.0.
The WSDL generated by the AdminClient looks okay to me (I am not an
expert) and works when called through the Axis client libraries
(WSDL2Java).
However, a proxy server that we have complains that the WSDL is invalid
and I was able to verify that it is considered invalid by a few WSDL
validators I googled (e.g. the one under Tools at www.xmethods.net).
Unfortunately, these validators don't tell you anything about what's
wrong. ("Can't parse" is the usual message. It is NOT a problem with
finding the location.)
Even the Version example's WSDL (that comes with Axis) is considered to
be invalid by these tools.
Any thoughts as to why these are invalid and how to get around it?
Jerry Cole
206.769.9312 - mobile
206.374.4603 - office
206.720.6945 - home office