Announcement Announcement Module
Collapse
No announcement yet.
Can not link exeption to operation in WSDL generated by Spring Web Services Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Can not link exeption to operation in WSDL generated by Spring Web Services

    Sping Web Services can generate a WSDL from an XSD schema. But the operations generated in the WSDL file has no "fault" tag linked if the operation does have exception definition in the endpoint class. I think the reason is Sping Web Services only generate the WSDL from the XSD schema file, which does not refer to the corresponding JAVA endpoint class. This is the limit of contract-first method. So we can not get such result in the WSDL:
    <operation name="unregCard">
    <soap:operation soapAction=""/>
    <input>
    <soap:body use="literal"/>
    </input>
    <output>
    <soap:body use="literal"/>
    </output>
    <fault name="PersistException">
    <soap:fault name="PersistException" use="literal"/>
    </fault>
    <fault name="VolatileException">
    <soap:fault name="VolatileException" use="literal"/>
    </fault>
    </operation>

    Being a client of Sping Web Services, we can not catch defined exception like:

    try {
    getWebServiceTemplate().marshalSendAndReceive(requ est);
    } catch (PersistException pe) {
    } catch (VolatileException ve) {
    }

    We can only get the message from the exception and analyze it.

    I am a new user of Spring Web Services. Can anybody tell me if I am right?
    Last edited by bigriver73; Mar 15th, 2009, 08:40 PM.

  • #2
    Can anybody help me with my question

    Spring Web services do not support self-defined exception for operations?

    Comment

    Working...
    X