legalxml-courtfiling message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Groups - Document/Literal Wrapped WSDL uploaded
- From: Greg Zarkis<gzarkis@imagesoftinc.com>
- To: legalxml-courtfiling@lists.oasis-open.org
- Date: Tue, 8 Mar 2016 05:59:00 -0800 (PST)
Submitter's message
All-
I have uploaded a modified WSDL definition that follows a document/literal wrapped style. Some key updates from the existing WSDL:
* Each operation has a "type" for the request and response message. This type has is implemented by an element with the operation name for the request and operation name + "Response" for the response.
* I extracted the schema definition for the Web Service Profile types into it's own XSD and added an import to the WSDL definition file. This is something I end up doing often when working with other vendors to verify my outbound messages are schema-conformant, which also makes working with XMLSpy a lot easier. I would really like to see the SIP published this way.
* Each operation now has a SOAP Action defined in the binding.
I ran a few brief tests creating proxies with SoapUI, the Wizdler extension for Chrome, as well as the .NET wsdl.exe tool. They all seemed to like the new definition, but I still would like to go through some more ?fine tooth? testing. If anyone from the "non- .NET side" of development could take a look and verify, it would be greatly appreciated. :)
Finally, I am interested in discussing how this new patter man (or may not) help in the future with needs such as modifying these request/response messages with additional elements, and remaining Springboard compliant. For example, adding a PaymentMessage to the RecordFiling operation by modifying the schema of the Message type rather than modifying the schema of a "sub type" of the Message.
Regards,
-Greg
-- Greg Zarkis
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]