[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: WS SIP SOAP samples
Appendix C and the samples are non-normative.
I think the fix is probably to relax the wording of Section 2.5 itself since there is no schema that defines an element called “GetCase”. The alternative would be to update the schemas in the Core Specification. Do you agree?
__
Jim Cabral 502 509-4532 From: Gary
Graham
Sent: Tuesday, June 9, 2015 7:20 PM To: James E Cabral Cc: legalxml-courtfiling@lists.oasis-open.org See below
From: legalxml-courtfiling@lists.oasis-open.org [mailto:legalxml-courtfiling@lists.oasis-open.org]
On Behalf Of James E Cabral
Gary,
On the TC call today, you reported an incompatibility between Section 2.5 of the WS SIP specification and at least some of the SOAP samples, including GetCaseRequest.soap. I’m hoping you elaborate more on what you see as the incompatibility. The relevant snippets are included below. Are you saying that you would expect to see “GetCaseRequest” instead of “CaseQueryMessage” inside of the soapenv:Body? No, there are no ECF operations named GetCaseRequest or CaseQueryMessage. However there is an operation named GetCase that takes CaseQueryMessage as a parameter (see C.3.1 of the ECF specification). Hence, the first child element of <soapenv:Body> MUST be GetCase since ‘GetCase’ is the operation name.
------------------------------- WS SIP Section 2.5: Each message transmission MUST identify the operation being invoked within the SOAP Body only; the (qualified) operation name MUST be the qualified name of the first child element of the SOAP body element, as called for in section 7.1 of the [SOAP 1.1] specification. An MDE implementation MAY allow message transmissions that include a SOAPAction HTTP header. In compliance with the [WSI-I BP 1.1] specification, a receiving MDE MAY NOT rely on the value of the SOAPAction HTTP header in processing the message. ----------------------------- GetCaseRequest.soap: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"> <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> … </wsse:Security> <wsa:Action>urn:oasis:names:tc:legalxml-courtfiling:wsdl:WebServicesProfile-Definitions-4.0\CourtRecordMDEPort\GetCase</wsa:Action> <wsa:ReplyTo> <wsa:Address>https://JEC-SURFACEPRO2:8080/mockFilingAssemblyMDEPortSOAPBinding</wsa:Address> </wsa:ReplyTo> <wsa:MessageID>uuid:48a86134-9712-451b-a4ee-036d408b4f07</wsa:MessageID> <wsa:To>https://JEC-SURFACEPRO2/mockCourtRecordMDEPortSOAPBinding</wsa:To> </soapenv:Header> <soapenv:Body wsu:Id="id-53204E93D7C96443EC141342618529211" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <CaseQueryMessage xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseQueryMessage-4.0 ../../schemas/information/message/ECF-4.0-CaseQueryMessage.xsd" xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseQueryMessage-4.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> … </CaseQueryMessage> </soapenv:Body> </soapenv:Envelope>
__
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]