scandihealth / lpr3-docs

https://scandihealth.github.io/lpr3-docs/
MIT License
11 stars 7 forks source link

Emtpy XOP attachment when sending CDA #271

Closed Remcovanderwerf closed 5 years ago

Remcovanderwerf commented 5 years ago

Hi,

When submitting the following CDA file CDA.txt

LPR3 responds with a SOAP response without an attachment. This could be the same issue as #248 but not sure.

Can you look into this? Thank you in advance!

Kind regards,

Remco van der Werf Enovation | The Netherlands Contractor: Region Syddanmark

Remcovanderwerf commented 5 years ago

Hi,

is there any way to get a response on the issue above?

Thank you in advance!

Kind regards,

Remco van der werf

TueCN commented 5 years ago

Hi @Remcovanderwerf, I don't entirely understand your issue. As far as I can tell there is 1 part in the response. Is that not as expected?

Here is LPR's response to your request, from our logs. Can you point me towards the issue?

--------------------------------------
2019-01-08 14:29:04,950 INFO  [org.apache.cxf.services.DocumentRepository_Service.DocumentRepository_Port_Soap12.DocumentRepository_PortType] (default task-32) Outbound Message
---------------------------
ID: 78913
Response-Code: 200
Encoding: UTF-8
Content-Type: multipart/related; type="application/xop+xml"; boundary="uuid:d695bb93-11a6-46ca-93c6-caaccd3dda82"; start="<root.message@cxf.apache.org>"; start-info="application/soap+xml"
Headers: {}
Payload: 
--uuid:d695bb93-11a6-46ca-93c6-caaccd3dda82
Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml"
Content-Transfer-Encoding: binary
Content-ID: <root.message@cxf.apache.org>

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-bResponse</Action><MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:47143fff-2817-4b32-a1a3-87bfa1a230b8</MessageID><To xmlns="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing/anonymous</To><RelatesTo xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:05d80c95-b5cb-4239-a3cd-0ee782fc98e7</RelatesTo><ns10:Header xmlns:ns10="http://www.medcom.dk/dgws/2006/04/dgws-1.0.xsd" xmlns:ns11="http://www.nsi.dk/hsuid/2016/08/hsuid-1.1.xsd" xmlns:ns12="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:ns13="urn:lpr" xmlns:ns2="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0" xmlns:ns4="urn:ihe:iti:xds-b:2007" xmlns:ns5="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0" xmlns:ns6="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:ns7="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:ns8="http://www.w3.org/2000/09/xmldsig#" xmlns:ns9="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><ns10:SecurityLevel>3</ns10:SecurityLevel><ns10:Linking><ns10:FlowID>wfRBwQEvD0XvEWOXAwHqOA==</ns10:FlowID><ns10:MessageID>AAABaC2m+7aWkD2Xx3NM61NPU0k=</ns10:MessageID></ns10:Linking><ns10:FlowStatus>flow_finalized_succesfully</ns10:FlowStatus><ns10:RequireNonRepudiationReceipt>no</ns10:RequireNonRepudiationReceipt></ns10:Header></soap:Header><soap:Body><ns2:RegistryResponse xmlns:ns10="http://www.medcom.dk/dgws/2006/04/dgws-1.0.xsd" xmlns:ns11="http://www.nsi.dk/hsuid/2016/08/hsuid-1.1.xsd" xmlns:ns12="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:ns13="urn:lpr" xmlns:ns2="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0" xmlns:ns4="urn:ihe:iti:xds-b:2007" xmlns:ns5="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0" xmlns:ns6="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:ns7="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:ns8="http://www.w3.org/2000/09/xmldsig#" xmlns:ns9="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure"><ns2:RegistryErrorList highestSeverity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error"><ns2:RegistryError codeContext="INTEGRITY_CHECK|||Procedure 632075ED-03E3-499F-A8E7-8BE27C392182 already exists in the registry|||PROCEDURE_ALREADY_EXISTS|||632075ED-03E3-499F-A8E7-8BE27C392182" errorCode="InvalidDocumentContent" location="6A98AE55-E6A3-504C-AA4C-D95E778DD8CD^5A58C7FC-8F0B-4935-BE22-828D4D987C07|||//*[local-name()='act' and @classCode='ACT' and @moodCode='EVN' and child::*[local-name()='templateId' and @root='1.2.208.176.7.1.10.25'] and child::*[local-name()='templateId' and @root='2.16.840.1.113883.10.12.301'] or local-name()='observation' and @classCode='OBS' and @moodCode='EVN' and child::*[local-name()='templateId' and @root='1.2.208.176.7.1.10.29'] and child::*[local-name()='templateId' and @root='2.16.840.1.113883.10.12.303'] or local-name()='act' and @classCode='PROC' and @moodCode='EVN' and child::*[local-name()='templateId' and @root='1.2.208.176.7.1.10.30'] and child::*[local-name()='templateId' and @root='2.16.840.1.113883.10.12.306']][child::*[local-name()='id' and @extension='632075ED-03E3-499F-A8E7-8BE27C392182']]" severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error"></ns2:RegistryError></ns2:RegistryErrorList></ns2:RegistryResponse></soap:Body></soap:Envelope>
--uuid:d695bb93-11a6-46ca-93c6-caaccd3dda82--
Remcovanderwerf commented 5 years ago

Hi Tue,

that is odd. Our receiving webservice was not able to process the message because the message multipart with the attachment/payload was empty. Apparently in your log it was actually there.

I will close the issue for now and I will reopen it if it reoccurs. Thank you for the investigation!