This was due to a firewall issue. By adding proxy information to the
wsdl2java command line, I was able to move on to more challenging error
messages:
java -DproxySet=true -DproxyHost=myProxy.myCompany.com
-DproxyPort=myPort org.apache.cxf.tools.wsdlto.WSDLToJava -d ..
FileName.wsdl
Now I am battling "body part" errors such as:
In a port, operations must have unique operation signaure on the wire
for successful dispatch.
In port {http://www.myCo.com/wsdl/2007-06/abcd/efgh}HttpEndPoint,
Operations
"{http://www.myCo.com/wsdl/2007-06/abcd/efgh}Op1"; and
"{http://www.myCo.com/wsdl/2007-06/abcd/efgh}Op2";
have the same request body block
{http://www.myCo.com/schema/2007-06/abcd/ews/message}RequestMessage
I assume that we need to contact the web service provider and ask them
to modify the WSDL to have unique signatures for each operation.
Thanks,
Radu Manolescu
Morgan Stanley | Technology
2000 Westchester Ave, 1st Floor | Purchase, NY 10577
Phone: +1 914 225-5871
Mobile: +1 203 648-6964
[EMAIL PROTECTED]
-----Original Message-----
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2008 4:57 PM
To: [email protected]
Cc: cxf-ea
Subject: Re: WSDLToJava Error | xmldsig-core-schema.xsd | Connection
timed out
If eclipse is having problems reading it, most likely we cannot
either. I'm not exactly sure how you can get a connection timed
out error with a file URL. That seams a bit strange. Maybe a
permissions issue? Is the file really readable? (can you cat it?
load it in notepad?)
Dan
On Jun 5, 2008, at 11:14 AM, Manolescu, Radu (IT) wrote:
> I am trying to generate client code from a WSDL file, and I am getting
> the error below.
> My WSDL references an XSD (authored by our counterpart) which
> references the public file "oasis-200401-wss-wssecurity-
> secext-1.0.xsd", which references the public file "xmldsig-core-
> schema.xsd".
> I tried to use Eclipse to validate the WSDL and XSD files, and when
> Eclipse complained that it could not read some XSD files, I downloaded
> them locally and changed the "schemaLocation" references accordingly.
>
> The last errors, which I cannot seem to be able to remove, are:
> * "oasis-200401-wss-wssecurity-secext-1.0.xsd" does not pass
Eclipse
> validation. Eclipse complains about being unable to read
> "xmldsig-core-schema.xsd", whether that file is referenced locally or
> from the Internet
> * when using Ant to call wsdl2java to generate the client, I get
the
> exception below. Which program is trying to connect, and where?
> Is Ant trying to download files from the Internet while parsing
> "xmldsig-core-schema.xsd"?. If so, how can I make it connect? Define a
> proxy somewhere? Download the dependencies locally?
>
> wsdl2java:
>
> [java] WSDLToJava Error : java.lang.RuntimeException: Fail to create
> wsdl definition from : file:/U:/NonVerConPrj/MyProj/src/ide-bin/etc/
> Nodal.wsdl
>
> [java] Caused by : WSDLException (at /wsdl:definitions/wsdl:types/
> xs:schema/xsd:schema/xsd:schema): faultCode=PARSER_ERROR: Problem
> parsing 'file:/U:/NonVerConPrj/MyProj/src/ide-bin/etc/xmldsig-core-
> schema.xsd'.: java.net.ConnectException: Connection timed out: connect
>
>
> Public file references:
>
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-sec
> ext-1.0.xsd , saved locally as
> oasis-200401-wss-wssecurity-secext-1.0.xsd
> (attached)
>
> http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd, saved
> locally as xmldsig-core-schema.xsd (attached)
>
> http://www.w3.org/2001/xml.xsd, saved locally as xml.xsd
>
>
> Thanks,
>
>
> Radu Manolescu
> Morgan Stanley | Technology
> 2000 Westchester Ave, 1st Floor | Purchase, NY 10577
> Phone: +1 914 225-5871
> Mobile: +1 203 648-6964
> [EMAIL PROTECTED]
>
> NOTICE: If received in error, please destroy and notify sender.
> Sender does not intend to waive confidentiality or privilege. Use of
> this email is prohibited when received in error.
---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog
--------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not
intend to waive confidentiality or privilege. Use of this email is prohibited
when received in error.
