Forum Discussion
ALI_G
14 years agoNew Contributor
I've missed one of the soapUI's log.
+ I've figured out, that my wsdl has a project specific namespace:
[tt:1y5p4iaa]xmlns:jms="http://abcd/fooo/v1.0"[/tt:1y5p4iaa]
which used here:
[tt:1y5p4iaa]<jms:binding defaultMessageType="BytesMessage">
<jms:encoding type="Hessian"/>
</jms:binding>[/tt:1y5p4iaa]
and with this, the wsdl is valid.
If I modify it to
[tt:1y5p4iaa]<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" defaultMessageType="BytesMessage">
<jms:encoding type="Hessian"/>
</soap:binding>[/tt:1y5p4iaa]
than soapUI will open this WSDL, but it won't good for us.
What should I do?
Mon Oct 11 05:06:39 PDT 2010:INFO:Finding importer for {urn:asdf:eee:platform:samples:something:sampleservice:v1:contract}SampleServiceJMS
Mon Oct 11 05:06:39 PDT 2010:INFO:Missing importer for {urn:asdf:eee:platform:samples:something:sampleservice:v1:contract}SampleServiceJMS
+ I've figured out, that my wsdl has a project specific namespace:
[tt:1y5p4iaa]xmlns:jms="http://abcd/fooo/v1.0"[/tt:1y5p4iaa]
which used here:
[tt:1y5p4iaa]<jms:binding defaultMessageType="BytesMessage">
<jms:encoding type="Hessian"/>
</jms:binding>[/tt:1y5p4iaa]
and with this, the wsdl is valid.
If I modify it to
[tt:1y5p4iaa]<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" defaultMessageType="BytesMessage">
<jms:encoding type="Hessian"/>
</soap:binding>[/tt:1y5p4iaa]
than soapUI will open this WSDL, but it won't good for us.
What should I do?
Related Content
- 2 years agojangid
- 7 months agod_bodenheimer