-
1. Re: Add input schema validation before invoking a SoapProxy action
crizom85 Nov 14, 2012 4:19 AM (in response to crizom85)No idea? is that so hard in Jboss ESB?
-
2. Re: Add input schema validation before invoking a SoapProxy action
tcunning Nov 15, 2012 12:22 AM (in response to crizom85)I'd take a look at the publish_as_webservice example. It's close to what you want, and you should be able to substitute in your xsd files and test with SOAPUI.
-
3. Re: Add input schema validation before invoking a SoapProxy action
crizom85 Nov 15, 2012 5:35 AM (in response to tcunning)In the publish_as_webservice example, it doesn't call an external system
I want call an external web service using the ESB action SoapProxy (without write additional java code), buf before calling this external web service I want to enable XSD schema validation on the input payload to the ESB service im writing. If i put the inXsd and outXsd on the "actions" tag, it expose a new web service based on those xsds i believe
-
4. Re: Add input schema validation before invoking a SoapProxy action
munimanjunath Dec 13, 2012 3:04 PM (in response to crizom85)Hi crizom85,
I extended the out of box schemavalidation class and enhanced it to accept the input request both with soap envelope and without ( for proxies on ebws you dont get soap tags) by adding a boolean property issoap. If the soap envelope tag exists extracted the body content and validated against the schema. The challenge here is namespaces you need to extract the namespaces from the envelope tag and add those namespaces to the extracted body otherwise validation will fail. You also need to further customize to support schema with multiple includes
-
5. Re: Add input schema validation before invoking a SoapProxy action
munimanjunath Dec 13, 2012 3:10 PM (in response to crizom85)Have you tried only validate=true and not providing inxsd and outxsd ?
-
6. Re: Add input schema validation before invoking a SoapProxy action
crizom85 Dec 13, 2012 3:23 PM (in response to munimanjunath)1) I dont want to extend classes...if I have to write custom code, then what is the purpose to use an ESB product? I will prefer write my custom java web services than extend class on jboss esb only to performs basic things
2) I don't "try" to do things...I follow the documentation..
3) I solved by using the action soapclient without schema validation, since the schema validation doesn't work as expected