bridge success status not working [message #587521] |
Wed, 10 September 2008 16:09 |
Jesse Pangburn Messages: 166 Registered: July 2009 |
Senior Member |
|
|
Hi,
Using the bridge, I sent a FindDocuments query to an initiating gateway.
In the gateway I forced a bogus error (told it not to recognize the query
id) and sent this error back. Here is the relevant portion of my log:
[DEBUG][09:00:39][hf.ihe.xds.consumer.B_Consumer] Got response :
<ns5:AdhocQuery
Response
status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure "
xmlns:ns2="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
xmlns:ns4="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0"
xmlns:ns5="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
xmlns:ns6="urn:ihe
:iti:xds-b:2007">
<ns3:RegistryErrorList>
<ns3:RegistryError
codeContext="Initiating Gateway Error: query id
'urn:uuid:14d4debf-8
f97-4251-9a74-a90016b0af0d' is unknown to the gateway"
errorCode="XDSUnknownStoredQuery"
severity="urn:oasis:names:tc:ebxml
-regrep:ErrorSeverityType:Error"/>
</ns3:RegistryErrorList>
<ns2:RegistryObjectList/>
</ns5:AdhocQueryResponse>
[DEBUG][09:00:39][.ohf.ihe.xds.XDSResponseParser] Loading response in EMF.
[DEBUG][09:00:39][.ohf.ihe.xds.XDSResponseParser] Failure.
[INFO ][09:00:39][.ohf.ihe.xds.XDSResponseParser] Error #0
Severity=Error
Code=XDSUnknownStoredQuery
Code Context=Initiating Gateway Error: query id
'urn:uuid:14d4debf-8f97-
4251-9a74-a90016b0af0d' is unknown to the gateway
Location= null
- Error #0
Severity=Error
Code=XDSUnknownStoredQuery
Code Context=Initiating Gateway Error: query id
'urn:uuid:14d4debf-8f97-
4251-9a74-a90016b0af0d' is unknown to the gateway
Location= null
The problem comes in when I check the QueryDocumentsResponseType object
for the success status. In this case, the success status is true when it
should be false. There are no error entries in the
QueryDocumentsResponseType object either. I'm wondering if anyone knows
if this is the bridge's fault or the initiating gateway's error response
is not technically correct? Maybe the status isn't quite the right urn
string?
thanks,
Jesse
|
|
|
Powered by
FUDForum. Page generated in 0.03356 seconds