I am running the following command:

wsdl2java -fe jaxws21 http://psis.catcert.net/wsdl/dss.wsdl

using cxf 2.6.2, 2.6.3 and 2.7 against the following wsdl:

http://psis.catcert.net/wsdl/dss.wsdl?wsdl
<http://psis.catcert.net/wsdl/dss.wsdl?wsdl>  

I saw a fix for 2.5.1 that addressed a similar problem 
https://issues.apache.org/jira/browse/CXF-3968
<https://issues.apache.org/jira/browse/CXF-3968>  .  I was able to
successfully map the wsdl via SOAP UI 4.5.1 and Axis 1.6.2.  Trying to run
wsdl2java causes:

[Fatal Error] oasis-sstc-saml-schema-protocol-1.1.xsd:1:50: White spaces are
required between publicId and systemId.

WSDLToJava Error: org.apache.cxf.wsdl11.WSDLRuntimeException: Fail to create
wsdl definition from : http://psis.catcert.net/wsdl/dss.wsdl
Caused by : WSDLException (at /definitions/types/xs:schema[4]):
faultCode=PARSER_ERROR: Problem parsing
'http://www.oasis-open.org/committees/download.php/3408/oasis-sstc-saml-schema-protocol-1.1.xsd'.:
org.xml.sax.SAXParseException: White spaces are required between publicId
and systemId.

I ended up taking the local system cached wsdls from SOAP UI and saw that
there was a duplicated xsd generated.  I removed it manually and the pointed
the references to the non-deleted one.  This seemed to fix the wsdl2java
script when running locally against the wsdl on the file system.

Since I was only helping out a client, I didn't dig into this any deeper. 
It is not a show stopper for me any longer, but I thought I would raise the
issue as it is consistently reproducible.  It very well might be something
malformed with their endpoint.  Not sure?!




--
View this message in context: 
http://cxf.547215.n5.nabble.com/Wsdl2java-white-space-publicId-and-systemId-issue-tp5718535.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to