1 Reply Latest reply on May 10, 2013 1:46 AM by mageshbk

wsdl breaks using 1.0.0-SNAPSHOT

jbride May 9, 2013 6:41 PM

Hi,

attached to this post is an example SY app (packaged as a jar) that exposes a soap service and deploys just fine in SY-0.8.0.Final on EAP6.0.1

the same SY app does not deploy using SY-1.0.0-SNAPSHOT on EAP6.1 ER7. The following exception is thrown:

Unexpected element parsing vfs:/content/purchasing-CreditAgency-0.0.1-SNAPSHOT.jar/wsdl/schema/creditAgency.xsd:   schema

modification to the wsdl in the jar such that the schema is embedded in the wsdl does correct the problem. (please see zip attachment).

However, folks already have working SY apps with wsdls/XSDs as demonstrated in the SY jar file.

It would be helpful if their existing SY apps do not break due to this problem when they upgrade to the version of SOA-6 built on SY1.0.0 .

thanks!

jeff

1. Re: wsdl breaks using 1.0.0-SNAPSHOT

mageshbk May 10, 2013 1:46 AM (in response to jbride)
Jeff,

You have used a wsdl import definition, hence JBossWS is throwing that as it expects wsdl:definitions in that file. You should use xs:import for schemas, where xmlns:xs="http://www.w3.org/2001/XMLSchema". Morevover, schemas should be imported inside a xs:schema element. I don't know how it could have worked in 0.8.
<wsdl:types> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:import schemaLocation="schema/creditAgency.xsd" namespace="http://www.jboss.org/examples/creditAgency"/> </xs:schema> </wsdl:types>

regards,
Magesh
Actions