Looking for explanation of wsdl mapping problem

[teknokrat]

I am using the latest jbossWS to try and generate a JAX-WS client from a wsdl file, which I belive was generated via .NET. The problem is that the jboss wsconsume chokes wherever there exists a

<s:element ref="s:schema" />

element with a org.xml.sax.SAXParseException: undefined element declaration 's:schema'. And this wsdl has a lot of them, all like this:

<s:complexType>
 <s:sequence>
 <s:element ref="s:schema" />
 <s:any />
 </s:sequence>
 </s:complexType>
 </s:element>
 </s:sequence>
 </s:complexType>

s is the following namespace xmlns:s="http://www.w3.org/2001/XMLSchema".

If I remove the offending element, jbossws generates all the java classes just fine. Since I don't control the wsdl I can't go around editing it.

Can someone please explain to me what is the problem here? I can generate classes for this wsdl just fine using Axis, so is the problem with jbossws? Is this a valid wsdl element? Is there something I can do to make this problem go away?

thanks

[omatzura]

Hi!

The problem is that the .net generated wsdls probably dont actually import the xmlschema schema (via an s:import statement), which results in the wsconsume schema parser not being able to find the global element definition for the schema element.. (You'll get an error for this in for example eclipse wtp wsdl editor also..)

I don't really know if there is any way to work around this in jbossws.. what you can do otherwise is save the wsdl locally, add the import yourself and then try to run wsconsume on it..

Hope this helps!

regards,

/Ole
eviware.com

[teknokrat]

Thanks for the help. I did consider this but right at the beginning of all the element definitions is

<s:import namespace="http://www.w3.org/2001/XMLSchema" />

which I think is correct.

[omatzura]

Hi,

the import probably needs to specify the location for it to work, ie

<s:import namespace="http://www.w3.org/2001/XMLSchema" schemaLocation="http://www.w3.org/2001/XMLSchema.xsd" />

regards,

/Ole
eviware.com

[teknokrat]

That worked! Thank you very much.

Is this actually a mandatory requirement of some specification or a quirk of jbossws? If the wsdl is not being generated correctly I'd like to be able to tell the people involved.

Thank you

p.s

Is it possible to add this attribute using a binding file?

[omatzura]

Hi,

well, judging from the XML Schema spec for imports (http://www.w3.org/TR/2001/PR-xmlschema-1-20010316/#composition-schemaImport), there are actually rules/guidelines for how to locate an XML Schema when the schemaLocation attribute is missing.. I don't know though if they would have been applicable to this situation and/or if the schema parser in jbossws actually tries to follow them..

regards!

/Ole
eviware.com