Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
..
Failed to load latest commit information.
src
Readme.md
pom.xml
validate-xml.jpg

Readme.md

Introduction

This quickstart demonstrates the usage of the XML validator. The service is almost same as the one in the transform-xslt quickstart. The service contained in this quickstart is a dummy service (OrderService) which simply returns the order object so that it can be processed by the transformer. The object is then transformed from an Order object to an OrderAck object using XSLT. The only one difference is that XML validator of message contents is enabled in this service. So SOAP Fault is caught when you submit a invalid SOAP request against XML Schema.

Validate XML Quickstart

This example is invoked through a SOAP gateway binding.

Note: When importing this quickstart into Eclipse you will see the following error:

src-resolve: Cannot resolve the name 'base:order.base' to a(n) 'element declaration' component.

To eliminate this error you need to import src/main/resources/xsd/catalog.xml via File -> Import… -> XML -> XML Catalog and then rebuild the project.

Running the quickstart

EAP

  1. Start EAP in standalone mode:

     ${AS}/bin/standalone.sh
    
  2. Build and deploy the Quickstart :

     mvn install -Pdeploy
    
  3. Submit a webservice request to invoke the SOAP gateway. There are a number of ways to do this :

    • Submit a request with your preferred SOAP client - src/test/resources/xml contains sample requests and the responses that you should see
    • Use the simple bundled SOAP client and the sample request XML e.g.

Send a valid request using src/test/resources/xml/soap-request.xml ``` mvn exec:java ``` Or send an invalid request using src/test/resouces/xml/soap-request-with-invalid-element.xml ``` mvn exec:java -Dexec.args="invalid" ```
- SOAP-UI : Use the wsdl for this project (src/main/resources/wsdl/OrderService.wsdl) to create a soap-ui project. Use the sample request (src/test/resources/xml/soap-request.xml) as an example of a sample request. Check the "Expected Output" section below for the expected results.
  1. Undeploy the quickstart:

     mvn clean -Pdeploy
    

Wildfly

  1. Start Wildfly in standalone mode:

${AS}/bin/standalone.sh

  1. Build and deploy the Quickstart :

mvn install -Pdeploy -Pwildfly

  1. Submit a webservice request to invoke the SOAP gateway. There are a number of ways to do this :
  • Submit a request with your preferred SOAP client - src/test/resources/xml contains sample requests and the responses that you should see
  • Use the simple bundled SOAP client and the sample request XML e.g.

Send a valid request using src/test/resources/xml/soap-request.xml ``` mvn exec:java ``` Or send an invalid request using src/test/resouces/xml/soap-request-with-invalid-element.xml ``` mvn exec:java -Dexec.args="invalid" ```
- SOAP-UI : Use the wsdl for this project (src/main/resources/wsdl/OrderService.wsdl) to create a soap-ui project. Use the sample request (src/test/resources/xml/soap-request.xml) as an example of a sample request. Check the "Expected Output" section below for the expected results.
  1. Undeploy the quickstart:

mvn clean -Pdeploy -Pwildfly

Karaf

  1. Start the Karaf server :

${KARAF_HOME}/bin/karaf

  1. Add the features URL for the respective version of SwitchYard. Replace {SWITCHYARD-VERSION} with the version of SwitchYard that you are using (ex. 2.0.0):

karaf@root> features:addurl mvn:org.switchyard.karaf/switchyard/{SWITCHYARD-VERSION}/xml/features

  1. Install the feature for the validate-xml quickstart :

karaf@root> features:install switchyard-quickstart-validate-xml

  1. Submit a webservice request to invoke the SOAP gateway. There are a number of ways to do this :
  • Submit a request with your preferred SOAP client - src/test/resources/xml contains sample requests and the responses that you should see
  • Use the simple bundled SOAP client and the sample request XML e.g.

Send a valid request using src/test/resources/xml/soap-request.xml ``` mvn exec:java -Pkaraf ``` Or send an invalid request using src/test/resouces/xml/soap-request-with-invalid-element.xml ``` mvn exec:java -Dexec.args="invalid" -Pkaraf ```
5. Undeploy the quickstart:

karaf@root> features:uninstall switchyard-quickstart-validate-xml

Expected Output

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<orders:orderAck xmlns:orders="urn:switchyard-quickstart:validate-xml:0.1.0">
<orderId>PO-19838-XYZ</orderId>
<accepted>true</accepted>
<status>Order Accepted</status>
</orders:orderAck>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

If you run the SOAP client with a different request e.g. (src/test/resources/xml/soap-request-with-invalid-element.xml) the below is expected:

Expected Output (for -Dexec.args="invalid")

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>SWITCHYARD014000: Validator 'org.switchyard.validate.xml.internal.XmlValidator' failed: 1 validation error(s): 
org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was found starting with element 'invalid-element'. No child element is expected at this point.</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>

And you can see the details of this error in the server.log. Note you also can see the normal response when you disable the validator in switchyard.xml.

Further Reading

  1. Validation Documentation
  2. XML Validator Documentation