Home » Archived » OHF » non stored query error against NIST server
| non stored query error against NIST server [message #38106] |
Wed, 05 December 2007 17:35  |
 Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi,
I've been trying to run an XDS.a non stored query against the NIST public
server for a week or so, but keep getting an error from the bridge. At
first I figured it was the NIST server so I thought I'd wait a while and
see if it got fixed, but now that the Test Log browser is up I can see
that NIST shows the response returned and seems to think there's no
problem.
It appears the bridge doesn't parse the response for some reason. I'm not
sure if the response is bad, or the bridge parser is bad. I grabbed the
message link, hopefully someone knows where the disconnect is from this
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
The exception returned is:
query documents returned an error: The following is the list of messages
returned: <br/>
Error parsing ebXML 2. 1 response with EMF. Response is:
/norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing ebXML
2. 1 response with EMF. Response is:
at
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
at
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
at
org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
at
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
at
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
at
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
at
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
at
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)
Caused by: org.eclipse.emf.ecore.resource.Resource$IOWrappedException:
Feature 'ExtrinsicObject' not found.
(urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
at
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
at
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
at
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
... 42 more
Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature
'ExtrinsicObject' not found.
(urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
at
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
at
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
at
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
at
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
at
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
... 45 more
thanks,
Jesse
|
|
|
| Re: non stored query error against NIST server [message #38206 is a reply to message #38106] |
Wed, 05 December 2007 18:57  |
No real name
Messages: 292
Registered: July 2009 |
Senior Member |
|
|
Hi Jesse,
This error gets thrown when OHF cannot parse the ebXML response with EMF
(Eclipse Modeling Framework). This typically happens when there is a
schema compliance error. From the link below, the response looks schema
valid. The only other thing I can think of is that you requested a
'LeafClass' return and you got back both ExtrinsicObjects and ObjectRefs
.... which I believe is not correct and will cause problems in OHF. I
have a NIST bug for this:
http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
In any event ... can you please submit a bug to the XDS Consumer and put
your debug log trace in there? I'd like to see what this thing looks
like when coming back across the wire ... maybe there is something
funny there.
Thanks!
- Sarah
Jesse Pangburn wrote:
> Hi,
> I've been trying to run an XDS.a non stored query against the NIST
> public server for a week or so, but keep getting an error from the
> bridge. At first I figured it was the NIST server so I thought I'd wait
> a while and see if it got fixed, but now that the Test Log browser is up
> I can see that NIST shows the response returned and seems to think
> there's no problem.
>
> It appears the bridge doesn't parse the response for some reason. I'm
> not sure if the response is bad, or the bridge parser is bad. I grabbed
> the message link, hopefully someone knows where the disconnect is from
> this
> http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>
>
> The exception returned is:
> query documents returned an error: The following is the list of messages
> returned: <br/>
> Error parsing ebXML 2. 1 response with EMF. Response is:
> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
> ebXML 2. 1 response with EMF. Response is:
>
> at
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>
> at
> org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>
> at
> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
> at
> org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>
> at
> org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>
> at
> org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>
> at
> org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>
> at
> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
> at
> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at
> org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>
> at
> org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
> at
> org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.eclipse.emf.ecore.resource.Resource$IOWrappedException:
> Feature 'ExtrinsicObject' not found.
> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>
> at
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>
> ... 42 more
> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature
> 'ExtrinsicObject' not found.
> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
> ... 45 more
>
> thanks,
> Jesse
>
|
|
|
| Re: non stored query error against NIST server [message #38238 is a reply to message #38106] |
Wed, 05 December 2007 18:59 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi,
I see from Sarah's links that there is already a defect against the non
stored query "finddocuments". You guys can delete this post if you like
:-)
thanks,
Jesse
Jesse Pangburn wrote:
> Hi,
> I've been trying to run an XDS.a non stored query against the NIST public
> server for a week or so, but keep getting an error from the bridge. At
> first I figured it was the NIST server so I thought I'd wait a while and
> see if it got fixed, but now that the Test Log browser is up I can see
> that NIST shows the response returned and seems to think there's no
> problem.
> It appears the bridge doesn't parse the response for some reason. I'm not
> sure if the response is bad, or the bridge parser is bad. I grabbed the
> message link, hopefully someone knows where the disconnect is from this
>
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
> The exception returned is:
> query documents returned an error: The following is the list of messages
> returned: <br/>
> Error parsing ebXML 2. 1 response with EMF. Response is:
> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing ebXML
> 2. 1 response with EMF. Response is:
> at
>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
> at
>
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
> at
> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
> at
>
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
> at
>
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
> at
>
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
> at
>
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
> at
> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
> at
>
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
> at
> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at
>
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
>
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
> at
>
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
> at
>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
> at
>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
>
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
> at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
> at
>
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
> at
>
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
> at
>
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
> at
>
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
> at
>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
> at
>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
> at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.eclipse.emf.ecore.resource.Resource$IOWrappedException:
> Feature 'ExtrinsicObject' not found.
> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
> at
>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
> at
>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
> ... 42 more
> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature
> 'ExtrinsicObject' not found.
> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
> at
>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
> at
>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
> ... 45 more
> thanks,
> Jesse
|
|
|
| Re: non stored query error against NIST server [message #38271 is a reply to message #38206] |
Wed, 05 December 2007 19:07 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi Sarah,
I see from your Mesa test status page that you already have a bug "166"
for FindDocuments. That's the one I'm using, FindDocuments non stored
query from the bridge. Should I still submit a bug despite your belief
that NIST is returning the wrong thing?
thanks,
Jesse
Sarah Knoop wrote:
> Hi Jesse,
> This error gets thrown when OHF cannot parse the ebXML response with EMF
> (Eclipse Modeling Framework). This typically happens when there is a
> schema compliance error. From the link below, the response looks schema
> valid. The only other thing I can think of is that you requested a
> 'LeafClass' return and you got back both ExtrinsicObjects and ObjectRefs
> .... which I believe is not correct and will cause problems in OHF. I
> have a NIST bug for this:
> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
> In any event ... can you please submit a bug to the XDS Consumer and put
> your debug log trace in there? I'd like to see what this thing looks
> like when coming back across the wire ... maybe there is something
> funny there.
> Thanks!
> - Sarah
> Jesse Pangburn wrote:
>> Hi,
>> I've been trying to run an XDS.a non stored query against the NIST
>> public server for a week or so, but keep getting an error from the
>> bridge. At first I figured it was the NIST server so I thought I'd wait
>> a while and see if it got fixed, but now that the Test Log browser is up
>> I can see that NIST shows the response returned and seems to think
>> there's no problem.
>>
>> It appears the bridge doesn't parse the response for some reason. I'm
>> not sure if the response is bad, or the bridge parser is bad. I grabbed
>> the message link, hopefully someone knows where the disconnect is from
>> this
>>
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>>
>>
>> The exception returned is:
>> query documents returned an error: The following is the list of messages
>> returned: <br/>
>> Error parsing ebXML 2. 1 response with EMF. Response is:
>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>> ebXML 2. 1 response with EMF. Response is:
>>
>> at
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>>
>> at
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>>
>> at
>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>> at
>>
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>>
>> at
>>
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>>
>> at
>>
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at
>>
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>>
>> at
>>
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>>
>> at
>> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>> at
>>
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>>
>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>> at
>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>> at
>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>> at
>>
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>> at
>>
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>>
>> at
>>
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>>
>> at
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>>
>> at
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>> at
>>
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>> at
>>
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>>
>> at
>>
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>>
>> at
>>
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>>
>> at
>>
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>>
>> at
>>
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>>
>> at
>>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>>
>> at
>>
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>>
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>> at
>> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>> at
>>
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>>
>> at
>>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>>
>> at
>>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>>
>> at
>>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>>
>> at java.lang.Thread.run(Unknown Source)
>> Caused by: org.eclipse.emf.ecore.resource.Resource$IOWrappedException:
>> Feature 'ExtrinsicObject' not found.
>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>>
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>>
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>>
>> at
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>>
>> ... 42 more
>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature
>> 'ExtrinsicObject' not found.
>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>>
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>>
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>>
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>>
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>> ... 45 more
>>
>> thanks,
>> Jesse
>>
|
|
|
| Re: non stored query error against NIST server [message #38304 is a reply to message #38271] |
Wed, 05 December 2007 19:18 |
No real name
Messages: 292
Registered: July 2009 |
Senior Member |
|
|
Yes please. I just want to make sure that this is the 'same wrong thing'
and not a new 'wrong thing' :-)
- Sarah
Jesse Pangburn wrote:
> Hi Sarah,
> I see from your Mesa test status page that you already have a bug "166"
> for FindDocuments. That's the one I'm using, FindDocuments non stored
> query from the bridge. Should I still submit a bug despite your belief
> that NIST is returning the wrong thing?
>
> thanks,
> Jesse
>
> Sarah Knoop wrote:
>
>> Hi Jesse,
>
>
>> This error gets thrown when OHF cannot parse the ebXML response with
>> EMF (Eclipse Modeling Framework). This typically happens when there is
>> a schema compliance error. From the link below, the response looks
>> schema valid. The only other thing I can think of is that you
>> requested a 'LeafClass' return and you got back both ExtrinsicObjects
>> and ObjectRefs .... which I believe is not correct and will cause
>> problems in OHF. I have a NIST bug for this:
>
>
>> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
>
>
>> In any event ... can you please submit a bug to the XDS Consumer and
>> put your debug log trace in there? I'd like to see what this thing
>> looks like when coming back across the wire ... maybe there is
>> something funny there.
>
>
>> Thanks!
>> - Sarah
>
>
>
>
>
>> Jesse Pangburn wrote:
>>
>>> Hi,
>>> I've been trying to run an XDS.a non stored query against the NIST
>>> public server for a week or so, but keep getting an error from the
>>> bridge. At first I figured it was the NIST server so I thought I'd
>>> wait a while and see if it got fixed, but now that the Test Log
>>> browser is up I can see that NIST shows the response returned and
>>> seems to think there's no problem.
>>>
>>> It appears the bridge doesn't parse the response for some reason.
>>> I'm not sure if the response is bad, or the bridge parser is bad. I
>>> grabbed the message link, hopefully someone knows where the
>>> disconnect is from this
>
> http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>
>
>>>
>>>
>>> The exception returned is:
>>> query documents returned an error: The following is the list of
>>> messages returned: <br/>
>>> Error parsing ebXML 2. 1 response with EMF. Response is:
>>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>>> ebXML 2. 1 response with EMF. Response is:
>>>
>>> at
>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>
>
>>>
>>> at
>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>
>
>>>
>>> at
>>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>>> at
>
> org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>
>
>>>
>>> at
>
> org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>
>
>>>
>>> at
>
> org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>
>
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>> Source)
>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>> at
>
> org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>
>
>>>
>>> at
>
> org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>
>
>>>
>>> at
>>> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>>>
>>> at
>
> org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>
>
>>>
>>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>> at
>>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>>> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>>> at
>>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>>> at
>
> org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>
>
>>>
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>> at
>
> org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>
>
>>>
>>> at
>
> org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>
>
>>>
>>> at
>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>
>
>>>
>>> at
>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>
>
>>>
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>> at
>
> org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>
>
>>>
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>
>
>>>
>>> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>
>
>>>
>>> at
>
> org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>
>
>>>
>>> at
>
> org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>
>
>>>
>>> at
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>
>
>>>
>>> at
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>
>
>>>
>>> at
>
> org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>
>
>>>
>>> at
>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>>>
>>> at
>>> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>>>
>>> at
>
> org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>
>
>>>
>>> at
>
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>
>
>>>
>>> at
>
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>
>
>>>
>>> at
>
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>
>
>>>
>>> at java.lang.Thread.run(Unknown Source)
>>> Caused by:
>>> org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature
>>> 'ExtrinsicObject' not found.
>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>
>
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>
>
>>>
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>
>
>>>
>>> at
>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>
>
>>>
>>> ... 42 more
>>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
>>> Feature 'ExtrinsicObject' not found.
>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>
>
>>>
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>
>
>>>
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>
>
>>>
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>
>
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>>> ... 45 more
>>>
>>> thanks,
>>> Jesse
>>>
>
>
|
|
|
| Re: non stored query error against NIST server [message #38337 is a reply to message #38304] |
Wed, 05 December 2007 20:02 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
You got it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=212061
If you need anything else on this, any way I can help, please let me know.
thanks,
Jesse
Sarah Knoop wrote:
> Yes please. I just want to make sure that this is the 'same wrong thing'
> and not a new 'wrong thing' :-)
> - Sarah
> Jesse Pangburn wrote:
>> Hi Sarah,
>> I see from your Mesa test status page that you already have a bug "166"
>> for FindDocuments. That's the one I'm using, FindDocuments non stored
>> query from the bridge. Should I still submit a bug despite your belief
>> that NIST is returning the wrong thing?
>>
>> thanks,
>> Jesse
>>
>> Sarah Knoop wrote:
>>
>>> Hi Jesse,
>>
>>
>>> This error gets thrown when OHF cannot parse the ebXML response with
>>> EMF (Eclipse Modeling Framework). This typically happens when there is
>>> a schema compliance error. From the link below, the response looks
>>> schema valid. The only other thing I can think of is that you
>>> requested a 'LeafClass' return and you got back both ExtrinsicObjects
>>> and ObjectRefs .... which I believe is not correct and will cause
>>> problems in OHF. I have a NIST bug for this:
>>
>>
>>> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
>>
>>
>>> In any event ... can you please submit a bug to the XDS Consumer and
>>> put your debug log trace in there? I'd like to see what this thing
>>> looks like when coming back across the wire ... maybe there is
>>> something funny there.
>>
>>
>>> Thanks!
>>> - Sarah
>>
>>
>>
>>
>>
>>> Jesse Pangburn wrote:
>>>
>>>> Hi,
>>>> I've been trying to run an XDS.a non stored query against the NIST
>>>> public server for a week or so, but keep getting an error from the
>>>> bridge. At first I figured it was the NIST server so I thought I'd
>>>> wait a while and see if it got fixed, but now that the Test Log
>>>> browser is up I can see that NIST shows the response returned and
>>>> seems to think there's no problem.
>>>>
>>>> It appears the bridge doesn't parse the response for some reason.
>>>> I'm not sure if the response is bad, or the bridge parser is bad. I
>>>> grabbed the message link, hopefully someone knows where the
>>>> disconnect is from this
>>
>>
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>>
>>
>>>>
>>>>
>>>> The exception returned is:
>>>> query documents returned an error: The following is the list of
>>>> messages returned: <br/>
>>>> Error parsing ebXML 2. 1 response with EMF. Response is:
>>>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>>>> ebXML 2. 1 response with EMF. Response is:
>>>>
>>>> at
>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>>
>>
>>>>
>>>> at
>>>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>>>> at
>>
>>
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>>
>>
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>>> Source)
>>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>>> at
>>
>>
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>>
>>
>>>>
>>>> at
>>>> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>>>>
>>>> at
>>
>>
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>>
>>
>>>>
>>>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>>> at
>>>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>>>> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>>>> at
>>>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>>>> at
>>
>>
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>>
>>
>>>>
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>> at
>>
>>
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>>
>>
>>>>
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>> at
>>
>>
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>>
>>
>>>>
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>> at
>>
>>
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>>
>>
>>>>
>>>> at
>>>>
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>>>>
>>>> at
>>>>
org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>>>>
>>>> at
>>
>>
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>>
>>
>>>>
>>>> at java.lang.Thread.run(Unknown Source)
>>>> Caused by:
>>>> org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature
>>>> 'ExtrinsicObject' not found.
>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>>
>>
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>>
>>
>>>>
>>>> ... 42 more
>>>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
>>>> Feature 'ExtrinsicObject' not found.
>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>>
>>
>>>>
>>>> at
>>>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>>>>
>>>> at
>>>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>>>> ... 45 more
>>>>
>>>> thanks,
>>>> Jesse
>>>>
>>
>>
|
|
|
| Re: non stored query error against NIST server [message #38403 is a reply to message #38337] |
Thu, 06 December 2007 00:15 |
No real name
Messages: 292
Registered: July 2009 |
Senior Member |
|
|
AHHH... I see now ...
Thanks for the log.
The registry response has the wrong namespace declaration for
'ExtrinsicObject'
.... which is in the rim namespace. This needs to be fixed by the. This is
documented in my flyspray bug:
http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
... below the initial bug report. I'll add another comment to this bug
post and
see if that gets it up in the queue.
- Sarah
Jesse Pangburn wrote:
> You got it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=212061
>
> If you need anything else on this, any way I can help, please let me know.
>
> thanks,
> Jesse
> Sarah Knoop wrote:
>
>> Yes please. I just want to make sure that this is the 'same wrong
>> thing' and not a new 'wrong thing' :-)
>
>
>> - Sarah
>
>
>> Jesse Pangburn wrote:
>>
>>> Hi Sarah,
>>> I see from your Mesa test status page that you already have a bug
>>> "166" for FindDocuments. That's the one I'm using, FindDocuments non
>>> stored query from the bridge. Should I still submit a bug despite
>>> your belief that NIST is returning the wrong thing?
>>>
>>> thanks,
>>> Jesse
>>>
>>> Sarah Knoop wrote:
>>>
>>>> Hi Jesse,
>>>
>>>
>>>
>>>> This error gets thrown when OHF cannot parse the ebXML response with
>>>> EMF (Eclipse Modeling Framework). This typically happens when there
>>>> is a schema compliance error. From the link below, the response
>>>> looks schema valid. The only other thing I can think of is that you
>>>> requested a 'LeafClass' return and you got back both
>>>> ExtrinsicObjects and ObjectRefs .... which I believe is not correct
>>>> and will cause problems in OHF. I have a NIST bug for this:
>>>
>>>
>>>
>>>> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
>>>
>>>
>>>
>>>> In any event ... can you please submit a bug to the XDS Consumer and
>>>> put your debug log trace in there? I'd like to see what this thing
>>>> looks like when coming back across the wire ... maybe there is
>>>> something funny there.
>>>
>>>
>>>
>>>> Thanks!
>>>> - Sarah
>>>
>>>
>>>
>>>
>>>
>>>
>>>> Jesse Pangburn wrote:
>>>>
>>>>> Hi,
>>>>> I've been trying to run an XDS.a non stored query against the NIST
>>>>> public server for a week or so, but keep getting an error from the
>>>>> bridge. At first I figured it was the NIST server so I thought I'd
>>>>> wait a while and see if it got fixed, but now that the Test Log
>>>>> browser is up I can see that NIST shows the response returned and
>>>>> seems to think there's no problem.
>>>>>
>>>>> It appears the bridge doesn't parse the response for some reason.
>>>>> I'm not sure if the response is bad, or the bridge parser is bad.
>>>>> I grabbed the message link, hopefully someone knows where the
>>>>> disconnect is from this
>>>
>>>
>>>
> http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>
>
>>>
>>>
>>>>>
>>>>>
>>>>> The exception returned is:
>>>>> query documents returned an error: The following is the list of
>>>>> messages returned: <br/>
>>>>> Error parsing ebXML 2. 1 response with EMF. Response is:
>>>>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>>>>> ebXML 2. 1 response with EMF. Response is:
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>
>
>>>
>>>
>>>>>
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>>>> Source)
>>>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>>>> at
>>>
>>>
>>>
> org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>>> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>
>
>>>
>>>
>>>>>
>>>>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>>>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>>>> at
>>>>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>>>>> at
>>>>> org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>>>>> at
>>>>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>>>>>
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>>>>> at
>>>
>>>
>>>
> org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>
>
>>>
>>>
>>>>>
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>> at
>>>
>>>
>>>
> org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>
>
>>>
>>>
>>>>>
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>> at
>>>
>>>
>>>
> org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>
>
>>>
>>>
>>>>>
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>
>
>>>
>>>
>>>>>
>>>>> at
>
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>
>>>>>
>>>>> at
>
> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>
>
>>>
>>>
>>>>>
>>>>> at java.lang.Thread.run(Unknown Source)
>>>>> Caused by:
>>>>> org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature
>>>>> 'ExtrinsicObject' not found.
>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>
>
>>>
>>>
>>>>>
>>>>> ... 42 more
>>>>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
>>>>> Feature 'ExtrinsicObject' not found.
>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>
>
>>>
>>>
>>>>>
>>>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>
>>>>>
>>>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>>>>> ... 45 more
>>>>>
>>>>> thanks,
>>>>> Jesse
>>>>>
>>>
>>>
>
>
|
|
|
| Re: non stored query error against NIST server [message #38436 is a reply to message #38403] |
Thu, 06 December 2007 00:32 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Awesome! Thank *you* for figuring out the problem :-)
Jesse
Sarah Knoop wrote:
> AHHH... I see now ...
> Thanks for the log.
> The registry response has the wrong namespace declaration for
> 'ExtrinsicObject'
> .... which is in the rim namespace. This needs to be fixed by the. This is
> documented in my flyspray bug:
> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
> ... below the initial bug report. I'll add another comment to this bug
> post and
> see if that gets it up in the queue.
> - Sarah
> Jesse Pangburn wrote:
>> You got it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=212061
>>
>> If you need anything else on this, any way I can help, please let me know.
>>
>> thanks,
>> Jesse
>> Sarah Knoop wrote:
>>
>>> Yes please. I just want to make sure that this is the 'same wrong
>>> thing' and not a new 'wrong thing' :-)
>>
>>
>>> - Sarah
>>
>>
>>> Jesse Pangburn wrote:
>>>
>>>> Hi Sarah,
>>>> I see from your Mesa test status page that you already have a bug
>>>> "166" for FindDocuments. That's the one I'm using, FindDocuments non
>>>> stored query from the bridge. Should I still submit a bug despite
>>>> your belief that NIST is returning the wrong thing?
>>>>
>>>> thanks,
>>>> Jesse
>>>>
>>>> Sarah Knoop wrote:
>>>>
>>>>> Hi Jesse,
>>>>
>>>>
>>>>
>>>>> This error gets thrown when OHF cannot parse the ebXML response with
>>>>> EMF (Eclipse Modeling Framework). This typically happens when there
>>>>> is a schema compliance error. From the link below, the response
>>>>> looks schema valid. The only other thing I can think of is that you
>>>>> requested a 'LeafClass' return and you got back both
>>>>> ExtrinsicObjects and ObjectRefs .... which I believe is not correct
>>>>> and will cause problems in OHF. I have a NIST bug for this:
>>>>
>>>>
>>>>
>>>>> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
>>>>
>>>>
>>>>
>>>>> In any event ... can you please submit a bug to the XDS Consumer and
>>>>> put your debug log trace in there? I'd like to see what this thing
>>>>> looks like when coming back across the wire ... maybe there is
>>>>> something funny there.
>>>>
>>>>
>>>>
>>>>> Thanks!
>>>>> - Sarah
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Jesse Pangburn wrote:
>>>>>
>>>>>> Hi,
>>>>>> I've been trying to run an XDS.a non stored query against the NIST
>>>>>> public server for a week or so, but keep getting an error from the
>>>>>> bridge. At first I figured it was the NIST server so I thought I'd
>>>>>> wait a while and see if it got fixed, but now that the Test Log
>>>>>> browser is up I can see that NIST shows the response returned and
>>>>>> seems to think there's no problem.
>>>>>>
>>>>>> It appears the bridge doesn't parse the response for some reason.
>>>>>> I'm not sure if the response is bad, or the bridge parser is bad.
>>>>>> I grabbed the message link, hopefully someone knows where the
>>>>>> disconnect is from this
>>>>
>>>>
>>>>
>>
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>>
>>
>>>>
>>>>
>>>>>>
>>>>>>
>>>>>> The exception returned is:
>>>>>> query documents returned an error: The following is the list of
>>>>>> messages returned: <br/>
>>>>>> Error parsing ebXML 2. 1 response with EMF. Response is:
>>>>>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>>>>>> ebXML 2. 1 response with EMF. Response is:
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>>>>> Source)
>>>>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>>
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>>>>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>>>>> at
>>>>>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>>>>>> at
>>>>>> org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>>>>>> at
>>>>>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>>
>>>>>>
>>>>>> at
>>
>> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at java.lang.Thread.run(Unknown Source)
>>>>>> Caused by:
>>>>>> org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature
>>>>>> 'ExtrinsicObject' not found.
>>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> ... 42 more
>>>>>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
>>>>>> Feature 'ExtrinsicObject' not found.
>>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>>
>>>>>>
>>>>>> at
>>
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>>
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>>>>>> ... 45 more
>>>>>>
>>>>>> thanks,
>>>>>> Jesse
>>>>>>
>>>>
>>>>
>>
>>
|
|
|
| Re: non stored query error against NIST server [message #38800 is a reply to message #38403] |
Tue, 11 December 2007 00:35 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi Sarah,
I just tried the non stored query from the bridge for my audit log
testing. Lo and behold it worked :-) Apparently Bill or someone changed
the public registry.
thanks,
Jesse
Sarah Knoop wrote:
> AHHH... I see now ...
> Thanks for the log.
> The registry response has the wrong namespace declaration for
> 'ExtrinsicObject'
> .... which is in the rim namespace. This needs to be fixed by the. This is
> documented in my flyspray bug:
> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
> ... below the initial bug report. I'll add another comment to this bug
> post and
> see if that gets it up in the queue.
> - Sarah
> Jesse Pangburn wrote:
>> You got it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=212061
>>
>> If you need anything else on this, any way I can help, please let me know.
>>
>> thanks,
>> Jesse
>> Sarah Knoop wrote:
>>
>>> Yes please. I just want to make sure that this is the 'same wrong
>>> thing' and not a new 'wrong thing' :-)
>>
>>
>>> - Sarah
>>
>>
>>> Jesse Pangburn wrote:
>>>
>>>> Hi Sarah,
>>>> I see from your Mesa test status page that you already have a bug
>>>> "166" for FindDocuments. That's the one I'm using, FindDocuments non
>>>> stored query from the bridge. Should I still submit a bug despite
>>>> your belief that NIST is returning the wrong thing?
>>>>
>>>> thanks,
>>>> Jesse
>>>>
>>>> Sarah Knoop wrote:
>>>>
>>>>> Hi Jesse,
>>>>
>>>>
>>>>
>>>>> This error gets thrown when OHF cannot parse the ebXML response with
>>>>> EMF (Eclipse Modeling Framework). This typically happens when there
>>>>> is a schema compliance error. From the link below, the response
>>>>> looks schema valid. The only other thing I can think of is that you
>>>>> requested a 'LeafClass' return and you got back both
>>>>> ExtrinsicObjects and ObjectRefs .... which I believe is not correct
>>>>> and will cause problems in OHF. I have a NIST bug for this:
>>>>
>>>>
>>>>
>>>>> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
>>>>
>>>>
>>>>
>>>>> In any event ... can you please submit a bug to the XDS Consumer and
>>>>> put your debug log trace in there? I'd like to see what this thing
>>>>> looks like when coming back across the wire ... maybe there is
>>>>> something funny there.
>>>>
>>>>
>>>>
>>>>> Thanks!
>>>>> - Sarah
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Jesse Pangburn wrote:
>>>>>
>>>>>> Hi,
>>>>>> I've been trying to run an XDS.a non stored query against the NIST
>>>>>> public server for a week or so, but keep getting an error from the
>>>>>> bridge. At first I figured it was the NIST server so I thought I'd
>>>>>> wait a while and see if it got fixed, but now that the Test Log
>>>>>> browser is up I can see that NIST shows the response returned and
>>>>>> seems to think there's no problem.
>>>>>>
>>>>>> It appears the bridge doesn't parse the response for some reason.
>>>>>> I'm not sure if the response is bad, or the bridge parser is bad.
>>>>>> I grabbed the message link, hopefully someone knows where the
>>>>>> disconnect is from this
>>>>
>>>>
>>>>
>>
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>>
>>
>>>>
>>>>
>>>>>>
>>>>>>
>>>>>> The exception returned is:
>>>>>> query documents returned an error: The following is the list of
>>>>>> messages returned: <br/>
>>>>>> Error parsing ebXML 2. 1 response with EMF. Response is:
>>>>>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>>>>>> ebXML 2. 1 response with EMF. Response is:
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>>>>> Source)
>>>>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>>
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>>>>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>>>>> at
>>>>>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>>>>>> at
>>>>>> org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>>>>>> at
>>>>>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>>
>>>>>>
>>>>>> at
>>
>> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at java.lang.Thread.run(Unknown Source)
>>>>>> Caused by:
>>>>>> org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature
>>>>>> 'ExtrinsicObject' not found.
>>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> ... 42 more
>>>>>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
>>>>>> Feature 'ExtrinsicObject' not found.
>>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>>
>>>>>>
>>>>>> at
>>
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>>
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>>>>>> ... 45 more
>>>>>>
>>>>>> thanks,
>>>>>> Jesse
>>>>>>
>>>>
>>>>
>>
>>
|
|
|
| Re: non stored query error against NIST server [message #583560 is a reply to message #38106] |
Wed, 05 December 2007 18:57 |
No real name
Messages: 292
Registered: July 2009 |
Senior Member |
|
|
Hi Jesse,
This error gets thrown when OHF cannot parse the ebXML response with EMF
(Eclipse Modeling Framework). This typically happens when there is a
schema compliance error. From the link below, the response looks schema
valid. The only other thing I can think of is that you requested a
'LeafClass' return and you got back both ExtrinsicObjects and ObjectRefs
.... which I believe is not correct and will cause problems in OHF. I
have a NIST bug for this:
http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
In any event ... can you please submit a bug to the XDS Consumer and put
your debug log trace in there? I'd like to see what this thing looks
like when coming back across the wire ... maybe there is something
funny there.
Thanks!
- Sarah
Jesse Pangburn wrote:
> Hi,
> I've been trying to run an XDS.a non stored query against the NIST
> public server for a week or so, but keep getting an error from the
> bridge. At first I figured it was the NIST server so I thought I'd wait
> a while and see if it got fixed, but now that the Test Log browser is up
> I can see that NIST shows the response returned and seems to think
> there's no problem.
>
> It appears the bridge doesn't parse the response for some reason. I'm
> not sure if the response is bad, or the bridge parser is bad. I grabbed
> the message link, hopefully someone knows where the disconnect is from
> this
> http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>
>
> The exception returned is:
> query documents returned an error: The following is the list of messages
> returned: <br/>
> Error parsing ebXML 2. 1 response with EMF. Response is:
> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
> ebXML 2. 1 response with EMF. Response is:
>
> at
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>
> at
> org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>
> at
> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
> at
> org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>
> at
> org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>
> at
> org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>
> at
> org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>
> at
> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
> at
> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at
> org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>
> at
> org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
> at
> org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.eclipse.emf.ecore.resource.Resource$IOWrappedException:
> Feature 'ExtrinsicObject' not found.
> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>
> at
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>
> ... 42 more
> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature
> 'ExtrinsicObject' not found.
> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
> ... 45 more
>
> thanks,
> Jesse
>
|
|
|
| Re: non stored query error against NIST server [message #583572 is a reply to message #38106] |
Wed, 05 December 2007 18:59 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi,
I see from Sarah's links that there is already a defect against the non
stored query "finddocuments". You guys can delete this post if you like
:-)
thanks,
Jesse
Jesse Pangburn wrote:
> Hi,
> I've been trying to run an XDS.a non stored query against the NIST public
> server for a week or so, but keep getting an error from the bridge. At
> first I figured it was the NIST server so I thought I'd wait a while and
> see if it got fixed, but now that the Test Log browser is up I can see
> that NIST shows the response returned and seems to think there's no
> problem.
> It appears the bridge doesn't parse the response for some reason. I'm not
> sure if the response is bad, or the bridge parser is bad. I grabbed the
> message link, hopefully someone knows where the disconnect is from this
>
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
> The exception returned is:
> query documents returned an error: The following is the list of messages
> returned: <br/>
> Error parsing ebXML 2. 1 response with EMF. Response is:
> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing ebXML
> 2. 1 response with EMF. Response is:
> at
>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
> at
>
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
> at
> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
> at
>
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
> at
>
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
> at
>
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
> at
>
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
> at
> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
> at
>
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
> at
> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at
>
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
>
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
> at
>
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
> at
>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
> at
>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
>
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
> at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
> at
>
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
> at
>
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
> at
>
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
> at
>
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
> at
>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
> at
>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
> at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.eclipse.emf.ecore.resource.Resource$IOWrappedException:
> Feature 'ExtrinsicObject' not found.
> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
> at
>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
> at
>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
> ... 42 more
> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature
> 'ExtrinsicObject' not found.
> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
> at
>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
> at
>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
> at
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
> ... 45 more
> thanks,
> Jesse
|
|
|
| Re: non stored query error against NIST server [message #583579 is a reply to message #38206] |
Wed, 05 December 2007 19:07 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi Sarah,
I see from your Mesa test status page that you already have a bug "166"
for FindDocuments. That's the one I'm using, FindDocuments non stored
query from the bridge. Should I still submit a bug despite your belief
that NIST is returning the wrong thing?
thanks,
Jesse
Sarah Knoop wrote:
> Hi Jesse,
> This error gets thrown when OHF cannot parse the ebXML response with EMF
> (Eclipse Modeling Framework). This typically happens when there is a
> schema compliance error. From the link below, the response looks schema
> valid. The only other thing I can think of is that you requested a
> 'LeafClass' return and you got back both ExtrinsicObjects and ObjectRefs
> .... which I believe is not correct and will cause problems in OHF. I
> have a NIST bug for this:
> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
> In any event ... can you please submit a bug to the XDS Consumer and put
> your debug log trace in there? I'd like to see what this thing looks
> like when coming back across the wire ... maybe there is something
> funny there.
> Thanks!
> - Sarah
> Jesse Pangburn wrote:
>> Hi,
>> I've been trying to run an XDS.a non stored query against the NIST
>> public server for a week or so, but keep getting an error from the
>> bridge. At first I figured it was the NIST server so I thought I'd wait
>> a while and see if it got fixed, but now that the Test Log browser is up
>> I can see that NIST shows the response returned and seems to think
>> there's no problem.
>>
>> It appears the bridge doesn't parse the response for some reason. I'm
>> not sure if the response is bad, or the bridge parser is bad. I grabbed
>> the message link, hopefully someone knows where the disconnect is from
>> this
>>
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>>
>>
>> The exception returned is:
>> query documents returned an error: The following is the list of messages
>> returned: <br/>
>> Error parsing ebXML 2. 1 response with EMF. Response is:
>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>> ebXML 2. 1 response with EMF. Response is:
>>
>> at
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>>
>> at
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>>
>> at
>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>> at
>>
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>>
>> at
>>
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>>
>> at
>>
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at
>>
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>>
>> at
>>
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>>
>> at
>> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>> at
>>
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>>
>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>> at
>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>> at
>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>> at
>>
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>> at
>>
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>>
>> at
>>
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>>
>> at
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>>
>> at
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>> at
>>
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>> at
>>
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>>
>> at
>>
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>>
>> at
>>
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>>
>> at
>>
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>>
>> at
>>
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>>
>> at
>>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>>
>> at
>>
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>>
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>> at
>> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>> at
>>
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>>
>> at
>>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>>
>> at
>>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>>
>> at
>>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>>
>> at java.lang.Thread.run(Unknown Source)
>> Caused by: org.eclipse.emf.ecore.resource.Resource$IOWrappedException:
>> Feature 'ExtrinsicObject' not found.
>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>>
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>>
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>>
>> at
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>>
>> ... 42 more
>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature
>> 'ExtrinsicObject' not found.
>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>>
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>>
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>>
>> at
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>>
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>> at
>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>> ... 45 more
>>
>> thanks,
>> Jesse
>>
|
|
|
| Re: non stored query error against NIST server [message #583592 is a reply to message #38271] |
Wed, 05 December 2007 19:18 |
No real name
Messages: 292
Registered: July 2009 |
Senior Member |
|
|
Yes please. I just want to make sure that this is the 'same wrong thing'
and not a new 'wrong thing' :-)
- Sarah
Jesse Pangburn wrote:
> Hi Sarah,
> I see from your Mesa test status page that you already have a bug "166"
> for FindDocuments. That's the one I'm using, FindDocuments non stored
> query from the bridge. Should I still submit a bug despite your belief
> that NIST is returning the wrong thing?
>
> thanks,
> Jesse
>
> Sarah Knoop wrote:
>
>> Hi Jesse,
>
>
>> This error gets thrown when OHF cannot parse the ebXML response with
>> EMF (Eclipse Modeling Framework). This typically happens when there is
>> a schema compliance error. From the link below, the response looks
>> schema valid. The only other thing I can think of is that you
>> requested a 'LeafClass' return and you got back both ExtrinsicObjects
>> and ObjectRefs .... which I believe is not correct and will cause
>> problems in OHF. I have a NIST bug for this:
>
>
>> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
>
>
>> In any event ... can you please submit a bug to the XDS Consumer and
>> put your debug log trace in there? I'd like to see what this thing
>> looks like when coming back across the wire ... maybe there is
>> something funny there.
>
>
>> Thanks!
>> - Sarah
>
>
>
>
>
>> Jesse Pangburn wrote:
>>
>>> Hi,
>>> I've been trying to run an XDS.a non stored query against the NIST
>>> public server for a week or so, but keep getting an error from the
>>> bridge. At first I figured it was the NIST server so I thought I'd
>>> wait a while and see if it got fixed, but now that the Test Log
>>> browser is up I can see that NIST shows the response returned and
>>> seems to think there's no problem.
>>>
>>> It appears the bridge doesn't parse the response for some reason.
>>> I'm not sure if the response is bad, or the bridge parser is bad. I
>>> grabbed the message link, hopefully someone knows where the
>>> disconnect is from this
>
> http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>
>
>>>
>>>
>>> The exception returned is:
>>> query documents returned an error: The following is the list of
>>> messages returned: <br/>
>>> Error parsing ebXML 2. 1 response with EMF. Response is:
>>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>>> ebXML 2. 1 response with EMF. Response is:
>>>
>>> at
>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>
>
>>>
>>> at
>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>
>
>>>
>>> at
>>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>>> at
>
> org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>
>
>>>
>>> at
>
> org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>
>
>>>
>>> at
>
> org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>
>
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>> Source)
>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>> at
>
> org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>
>
>>>
>>> at
>
> org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>
>
>>>
>>> at
>>> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>>>
>>> at
>
> org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>
>
>>>
>>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>> at
>>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>>> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>>> at
>>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>>> at
>
> org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>
>
>>>
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>> at
>
> org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>
>
>>>
>>> at
>
> org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>
>
>>>
>>> at
>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>
>
>>>
>>> at
>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>
>
>>>
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>> at
>
> org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>
>
>>>
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>
>
>>>
>>> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>
>
>>>
>>> at
>
> org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>
>
>>>
>>> at
>
> org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>
>
>>>
>>> at
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>
>
>>>
>>> at
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>
>
>>>
>>> at
>
> org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>
>
>>>
>>> at
>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>>>
>>> at
>>> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>>>
>>> at
>
> org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>
>
>>>
>>> at
>
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>
>
>>>
>>> at
>
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>
>
>>>
>>> at
>
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>
>
>>>
>>> at java.lang.Thread.run(Unknown Source)
>>> Caused by:
>>> org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature
>>> 'ExtrinsicObject' not found.
>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>
>
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>
>
>>>
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>
>
>>>
>>> at
>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>
>
>>>
>>> ... 42 more
>>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
>>> Feature 'ExtrinsicObject' not found.
>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>
>
>>>
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>
>
>>>
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>
>
>>>
>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>
>
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>
>>> at
>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>>> ... 45 more
>>>
>>> thanks,
>>> Jesse
>>>
>
>
|
|
|
| Re: non stored query error against NIST server [message #583605 is a reply to message #38304] |
Wed, 05 December 2007 20:02 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
You got it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=212061
If you need anything else on this, any way I can help, please let me know.
thanks,
Jesse
Sarah Knoop wrote:
> Yes please. I just want to make sure that this is the 'same wrong thing'
> and not a new 'wrong thing' :-)
> - Sarah
> Jesse Pangburn wrote:
>> Hi Sarah,
>> I see from your Mesa test status page that you already have a bug "166"
>> for FindDocuments. That's the one I'm using, FindDocuments non stored
>> query from the bridge. Should I still submit a bug despite your belief
>> that NIST is returning the wrong thing?
>>
>> thanks,
>> Jesse
>>
>> Sarah Knoop wrote:
>>
>>> Hi Jesse,
>>
>>
>>> This error gets thrown when OHF cannot parse the ebXML response with
>>> EMF (Eclipse Modeling Framework). This typically happens when there is
>>> a schema compliance error. From the link below, the response looks
>>> schema valid. The only other thing I can think of is that you
>>> requested a 'LeafClass' return and you got back both ExtrinsicObjects
>>> and ObjectRefs .... which I believe is not correct and will cause
>>> problems in OHF. I have a NIST bug for this:
>>
>>
>>> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
>>
>>
>>> In any event ... can you please submit a bug to the XDS Consumer and
>>> put your debug log trace in there? I'd like to see what this thing
>>> looks like when coming back across the wire ... maybe there is
>>> something funny there.
>>
>>
>>> Thanks!
>>> - Sarah
>>
>>
>>
>>
>>
>>> Jesse Pangburn wrote:
>>>
>>>> Hi,
>>>> I've been trying to run an XDS.a non stored query against the NIST
>>>> public server for a week or so, but keep getting an error from the
>>>> bridge. At first I figured it was the NIST server so I thought I'd
>>>> wait a while and see if it got fixed, but now that the Test Log
>>>> browser is up I can see that NIST shows the response returned and
>>>> seems to think there's no problem.
>>>>
>>>> It appears the bridge doesn't parse the response for some reason.
>>>> I'm not sure if the response is bad, or the bridge parser is bad. I
>>>> grabbed the message link, hopefully someone knows where the
>>>> disconnect is from this
>>
>>
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>>
>>
>>>>
>>>>
>>>> The exception returned is:
>>>> query documents returned an error: The following is the list of
>>>> messages returned: <br/>
>>>> Error parsing ebXML 2. 1 response with EMF. Response is:
>>>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>>>> ebXML 2. 1 response with EMF. Response is:
>>>>
>>>> at
>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>>
>>
>>>>
>>>> at
>>>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>>>> at
>>
>>
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>>
>>
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>>> Source)
>>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>>> at
>>
>>
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>>
>>
>>>>
>>>> at
>>>> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>>>>
>>>> at
>>
>>
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>>
>>
>>>>
>>>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>>> at
>>>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>>>> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>>>> at
>>>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>>>> at
>>
>>
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>>
>>
>>>>
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>> at
>>
>>
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>>
>>
>>>>
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>> at
>>
>>
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>>
>>
>>>>
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>> at
>>
>>
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>>
>>
>>>>
>>>> at
>>>>
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>>>>
>>>> at
>>>>
org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>>>>
>>>> at
>>
>>
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>>
>>
>>>>
>>>> at
>>
>>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>>
>>
>>>>
>>>> at java.lang.Thread.run(Unknown Source)
>>>> Caused by:
>>>> org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature
>>>> 'ExtrinsicObject' not found.
>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>>
>>
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>>
>>
>>>>
>>>> ... 42 more
>>>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
>>>> Feature 'ExtrinsicObject' not found.
>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>>
>>
>>>>
>>>> at
>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>>
>>
>>>>
>>>> at
>>>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>>>>
>>>> at
>>>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>
>>>> at
>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>>>> ... 45 more
>>>>
>>>> thanks,
>>>> Jesse
>>>>
>>
>>
|
|
|
| Re: non stored query error against NIST server [message #583619 is a reply to message #38337] |
Thu, 06 December 2007 00:15 |
No real name
Messages: 292
Registered: July 2009 |
Senior Member |
|
|
AHHH... I see now ...
Thanks for the log.
The registry response has the wrong namespace declaration for
'ExtrinsicObject'
.... which is in the rim namespace. This needs to be fixed by the. This is
documented in my flyspray bug:
http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
... below the initial bug report. I'll add another comment to this bug
post and
see if that gets it up in the queue.
- Sarah
Jesse Pangburn wrote:
> You got it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=212061
>
> If you need anything else on this, any way I can help, please let me know.
>
> thanks,
> Jesse
> Sarah Knoop wrote:
>
>> Yes please. I just want to make sure that this is the 'same wrong
>> thing' and not a new 'wrong thing' :-)
>
>
>> - Sarah
>
>
>> Jesse Pangburn wrote:
>>
>>> Hi Sarah,
>>> I see from your Mesa test status page that you already have a bug
>>> "166" for FindDocuments. That's the one I'm using, FindDocuments non
>>> stored query from the bridge. Should I still submit a bug despite
>>> your belief that NIST is returning the wrong thing?
>>>
>>> thanks,
>>> Jesse
>>>
>>> Sarah Knoop wrote:
>>>
>>>> Hi Jesse,
>>>
>>>
>>>
>>>> This error gets thrown when OHF cannot parse the ebXML response with
>>>> EMF (Eclipse Modeling Framework). This typically happens when there
>>>> is a schema compliance error. From the link below, the response
>>>> looks schema valid. The only other thing I can think of is that you
>>>> requested a 'LeafClass' return and you got back both
>>>> ExtrinsicObjects and ObjectRefs .... which I believe is not correct
>>>> and will cause problems in OHF. I have a NIST bug for this:
>>>
>>>
>>>
>>>> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
>>>
>>>
>>>
>>>> In any event ... can you please submit a bug to the XDS Consumer and
>>>> put your debug log trace in there? I'd like to see what this thing
>>>> looks like when coming back across the wire ... maybe there is
>>>> something funny there.
>>>
>>>
>>>
>>>> Thanks!
>>>> - Sarah
>>>
>>>
>>>
>>>
>>>
>>>
>>>> Jesse Pangburn wrote:
>>>>
>>>>> Hi,
>>>>> I've been trying to run an XDS.a non stored query against the NIST
>>>>> public server for a week or so, but keep getting an error from the
>>>>> bridge. At first I figured it was the NIST server so I thought I'd
>>>>> wait a while and see if it got fixed, but now that the Test Log
>>>>> browser is up I can see that NIST shows the response returned and
>>>>> seems to think there's no problem.
>>>>>
>>>>> It appears the bridge doesn't parse the response for some reason.
>>>>> I'm not sure if the response is bad, or the bridge parser is bad.
>>>>> I grabbed the message link, hopefully someone knows where the
>>>>> disconnect is from this
>>>
>>>
>>>
> http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>
>
>>>
>>>
>>>>>
>>>>>
>>>>> The exception returned is:
>>>>> query documents returned an error: The following is the list of
>>>>> messages returned: <br/>
>>>>> Error parsing ebXML 2. 1 response with EMF. Response is:
>>>>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>>>>> ebXML 2. 1 response with EMF. Response is:
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>
>
>>>
>>>
>>>>>
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>>>> Source)
>>>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>>>> at
>>>
>>>
>>>
> org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>>> org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>
>
>>>
>>>
>>>>>
>>>>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>>>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>>>> at
>>>>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>>>>> at
>>>>> org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>>>>> at
>>>>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>>>>>
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>>>>> at
>>>
>>>
>>>
> org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>
>
>>>
>>>
>>>>>
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>> at
>>>
>>>
>>>
> org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>
>
>>>
>>>
>>>>>
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>> at
>>>
>>>
>>>
> org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>
>
>>>
>>>
>>>>>
>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>
>
>>>
>>>
>>>>>
>>>>> at
>
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>
>>>>>
>>>>> at
>
> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>
>
>>>
>>>
>>>>>
>>>>> at java.lang.Thread.run(Unknown Source)
>>>>> Caused by:
>>>>> org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature
>>>>> 'ExtrinsicObject' not found.
>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>
>
>>>
>>>
>>>>>
>>>>> ... 42 more
>>>>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
>>>>> Feature 'ExtrinsicObject' not found.
>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>
>
>>>
>>>
>>>>>
>>>>> at
>>>
>>>
>>>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>
>
>>>
>>>
>>>>>
>>>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>
>>>>>
>>>>> at
>
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>
>>>>> at
>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>>>>> ... 45 more
>>>>>
>>>>> thanks,
>>>>> Jesse
>>>>>
>>>
>>>
>
>
|
|
|
| Re: non stored query error against NIST server [message #583637 is a reply to message #38403] |
Thu, 06 December 2007 00:32 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Awesome! Thank *you* for figuring out the problem :-)
Jesse
Sarah Knoop wrote:
> AHHH... I see now ...
> Thanks for the log.
> The registry response has the wrong namespace declaration for
> 'ExtrinsicObject'
> .... which is in the rim namespace. This needs to be fixed by the. This is
> documented in my flyspray bug:
> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
> ... below the initial bug report. I'll add another comment to this bug
> post and
> see if that gets it up in the queue.
> - Sarah
> Jesse Pangburn wrote:
>> You got it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=212061
>>
>> If you need anything else on this, any way I can help, please let me know.
>>
>> thanks,
>> Jesse
>> Sarah Knoop wrote:
>>
>>> Yes please. I just want to make sure that this is the 'same wrong
>>> thing' and not a new 'wrong thing' :-)
>>
>>
>>> - Sarah
>>
>>
>>> Jesse Pangburn wrote:
>>>
>>>> Hi Sarah,
>>>> I see from your Mesa test status page that you already have a bug
>>>> "166" for FindDocuments. That's the one I'm using, FindDocuments non
>>>> stored query from the bridge. Should I still submit a bug despite
>>>> your belief that NIST is returning the wrong thing?
>>>>
>>>> thanks,
>>>> Jesse
>>>>
>>>> Sarah Knoop wrote:
>>>>
>>>>> Hi Jesse,
>>>>
>>>>
>>>>
>>>>> This error gets thrown when OHF cannot parse the ebXML response with
>>>>> EMF (Eclipse Modeling Framework). This typically happens when there
>>>>> is a schema compliance error. From the link below, the response
>>>>> looks schema valid. The only other thing I can think of is that you
>>>>> requested a 'LeafClass' return and you got back both
>>>>> ExtrinsicObjects and ObjectRefs .... which I believe is not correct
>>>>> and will cause problems in OHF. I have a NIST bug for this:
>>>>
>>>>
>>>>
>>>>> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
>>>>
>>>>
>>>>
>>>>> In any event ... can you please submit a bug to the XDS Consumer and
>>>>> put your debug log trace in there? I'd like to see what this thing
>>>>> looks like when coming back across the wire ... maybe there is
>>>>> something funny there.
>>>>
>>>>
>>>>
>>>>> Thanks!
>>>>> - Sarah
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Jesse Pangburn wrote:
>>>>>
>>>>>> Hi,
>>>>>> I've been trying to run an XDS.a non stored query against the NIST
>>>>>> public server for a week or so, but keep getting an error from the
>>>>>> bridge. At first I figured it was the NIST server so I thought I'd
>>>>>> wait a while and see if it got fixed, but now that the Test Log
>>>>>> browser is up I can see that NIST shows the response returned and
>>>>>> seems to think there's no problem.
>>>>>>
>>>>>> It appears the bridge doesn't parse the response for some reason.
>>>>>> I'm not sure if the response is bad, or the bridge parser is bad.
>>>>>> I grabbed the message link, hopefully someone knows where the
>>>>>> disconnect is from this
>>>>
>>>>
>>>>
>>
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>>
>>
>>>>
>>>>
>>>>>>
>>>>>>
>>>>>> The exception returned is:
>>>>>> query documents returned an error: The following is the list of
>>>>>> messages returned: <br/>
>>>>>> Error parsing ebXML 2. 1 response with EMF. Response is:
>>>>>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>>>>>> ebXML 2. 1 response with EMF. Response is:
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>>>>> Source)
>>>>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>>
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>>>>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>>>>> at
>>>>>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>>>>>> at
>>>>>> org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>>>>>> at
>>>>>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>>
>>>>>>
>>>>>> at
>>
>> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at java.lang.Thread.run(Unknown Source)
>>>>>> Caused by:
>>>>>> org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature
>>>>>> 'ExtrinsicObject' not found.
>>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> ... 42 more
>>>>>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
>>>>>> Feature 'ExtrinsicObject' not found.
>>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>>
>>>>>>
>>>>>> at
>>
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>>
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>>>>>> ... 45 more
>>>>>>
>>>>>> thanks,
>>>>>> Jesse
>>>>>>
>>>>
>>>>
>>
>>
|
|
|
| Re: non stored query error against NIST server [message #583789 is a reply to message #38403] |
Tue, 11 December 2007 00:35 |
Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi Sarah,
I just tried the non stored query from the bridge for my audit log
testing. Lo and behold it worked :-) Apparently Bill or someone changed
the public registry.
thanks,
Jesse
Sarah Knoop wrote:
> AHHH... I see now ...
> Thanks for the log.
> The registry response has the wrong namespace declaration for
> 'ExtrinsicObject'
> .... which is in the rim namespace. This needs to be fixed by the. This is
> documented in my flyspray bug:
> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
> ... below the initial bug report. I'll add another comment to this bug
> post and
> see if that gets it up in the queue.
> - Sarah
> Jesse Pangburn wrote:
>> You got it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=212061
>>
>> If you need anything else on this, any way I can help, please let me know.
>>
>> thanks,
>> Jesse
>> Sarah Knoop wrote:
>>
>>> Yes please. I just want to make sure that this is the 'same wrong
>>> thing' and not a new 'wrong thing' :-)
>>
>>
>>> - Sarah
>>
>>
>>> Jesse Pangburn wrote:
>>>
>>>> Hi Sarah,
>>>> I see from your Mesa test status page that you already have a bug
>>>> "166" for FindDocuments. That's the one I'm using, FindDocuments non
>>>> stored query from the bridge. Should I still submit a bug despite
>>>> your belief that NIST is returning the wrong thing?
>>>>
>>>> thanks,
>>>> Jesse
>>>>
>>>> Sarah Knoop wrote:
>>>>
>>>>> Hi Jesse,
>>>>
>>>>
>>>>
>>>>> This error gets thrown when OHF cannot parse the ebXML response with
>>>>> EMF (Eclipse Modeling Framework). This typically happens when there
>>>>> is a schema compliance error. From the link below, the response
>>>>> looks schema valid. The only other thing I can think of is that you
>>>>> requested a 'LeafClass' return and you got back both
>>>>> ExtrinsicObjects and ObjectRefs .... which I believe is not correct
>>>>> and will cause problems in OHF. I have a NIST bug for this:
>>>>
>>>>
>>>>
>>>>> http://ihe.univ-rennes1.fr/flyspray/?do=details&id=167
>>>>
>>>>
>>>>
>>>>> In any event ... can you please submit a bug to the XDS Consumer and
>>>>> put your debug log trace in there? I'd like to see what this thing
>>>>> looks like when coming back across the wire ... maybe there is
>>>>> something funny there.
>>>>
>>>>
>>>>
>>>>> Thanks!
>>>>> - Sarah
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Jesse Pangburn wrote:
>>>>>
>>>>>> Hi,
>>>>>> I've been trying to run an XDS.a non stored query against the NIST
>>>>>> public server for a week or so, but keep getting an error from the
>>>>>> bridge. At first I figured it was the NIST server so I thought I'd
>>>>>> wait a while and see if it got fixed, but now that the Test Log
>>>>>> browser is up I can see that NIST shows the response returned and
>>>>>> seems to think there's no problem.
>>>>>>
>>>>>> It appears the bridge doesn't parse the response for some reason.
>>>>>> I'm not sure if the response is bad, or the bridge parser is bad.
>>>>>> I grabbed the message link, hopefully someone knows where the
>>>>>> disconnect is from this
>>>>
>>>>
>>>>
>>
http://129.6.24.109:9080/LogReader/message.html?message=1196 87549741524.176.186.195&target=new
>>
>>
>>>>
>>>>
>>>>>>
>>>>>>
>>>>>> The exception returned is:
>>>>>> query documents returned an error: The following is the list of
>>>>>> messages returned: <br/>
>>>>>> Error parsing ebXML 2. 1 response with EMF. Response is:
>>>>>> /norg.eclipse.ohf.ihe.xds.XDSResponseParserException: Error parsing
>>>>>> ebXML 2. 1 response with EMF. Response is:
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:136)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.processResponse(XD SResponseParser.java:64)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ohf.ihe.xds.consumer.Consumer.query(Consumer.jav a:139)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.ihe.IheXdsBridge.goQueryDocumentsByPa tientId(IheXdsBridge.java:154)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.xds.AbstractXdsBridge.queryDocumentsB yPatientId(AbstractXdsBridge.java:49)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.bridge.ws.OHFBridge.QueryDocumentsByPatientI d(OHFBridge.java:97)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>>>>> Source)
>>>>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:413)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>>
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>>>>>> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>>>>>> at
>>>>>> org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:454)
>>>>>> at
>>>>>> org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 )
>>>>>> at
>>>>>> org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699)
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.registry.internal.ServletManager$Se rvletWrapper.service(ServletManager.java:129)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:91)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:110)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:68)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.equinox.servletbridge.BridgeServlet.service(Brid geServlet.java:95)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148)
>>
>>>>>>
>>>>>> at
>>
>> org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869)
>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt( LeaderFollowerWorkerThread.java:80)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:684)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at java.lang.Thread.run(Unknown Source)
>>>>>> Caused by:
>>>>>> org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature
>>>>>> 'ExtrinsicObject' not found.
>>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLL oadImpl.java:81)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:422)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:614)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.load(XMLResou rceImpl.java:578)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.ohf.ihe.xds.XDSResponseParser.parseEbXML_2_1(XDS ResponseParser.java:134)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> ... 42 more
>>>>>> Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException:
>>>>>> Feature 'ExtrinsicObject' not found.
>>>>>> (urn:oasis:names:tc:ebxml-regrep:registry:xsd:2.1, -1, -1)
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeatu re(XMLHandler.java:1856)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeatu re(XMLHandler.java:1820)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1764)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>>>
>>>>
>>>>
>>
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:974)
>>
>>
>>>>
>>>>
>>>>>>
>>>>>> at
>>
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:953)
>>
>>>>>>
>>>>>> at
>>
>> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:684)
>>
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:561)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>>
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.traverse(XMLLoadI mpl.java:566)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:398)
>>>>>> ... 45 more
>>>>>>
>>>>>> thanks,
>>>>>> Jesse
>>>>>>
>>>>
>>>>
>>
>>
|
|
|
Goto Forum:
Current Time: Sat Apr 20 03:21:21 GMT 2024
Powered by FUDForum. Page generated in 0.04826 seconds |
] 
Search
Help
Register
Login
Home
