Wednesday, June 16, 2004

Trouble with QNames in AXIS SOAP service.

I am trying to access a SOAP service that I have previously accessed, but now I am more familiar with name spaces and how to use them. However, when the client tries to connect to the server I get the following error:

org.apache.axis.ConfigurationException: No service named http://www.ngdc.noaa.gov/gdsg/oseiSpatial is available
at org.apache.axis.configuration.FileProvider.getService(FileProvider.java:263)
at org.apache.axis.AxisEngine.getService(AxisEngine.java:322)
at org.apache.axis.MessageContext.setTargetService(MessageContext.java:794)
at org.apache.axis.client.Call.invoke(Call.java:2613)
at org.apache.axis.client.Call.invoke(Call.java:2355)
at org.apache.axis.client.Call.invoke(Call.java:2278)
at org.apache.axis.client.Call.invoke(Call.java:1772)
at gov.noaa.gdsg.oseiSpatialService.OseiSpatialUpdater.updateRecord(...

here is the the call.setOperationName() QName:
new QName("http://www.ngdc.noaa.gov/gdsg/oseiSpatial", "updateOseiRecord")

Here is the wsdl excert:
<wsdl:definitions targetNamespace="http://www.ngdc.noaa.gov/gdsg/oseiSpatial">






This does not seem to be the problem. The problem seems to be something dealing with threads. The server code works fine outside of Axis, but when used in Axis, it seems that some sort of threading issue is causing either deadlock or starvation.

No comments: