Imo, calling a web service directly from a SE is not a good option.
You should try with the jsr181 proxy client.
Anyway, it seems the web service sends a fault, so i would try
to put a soap debugger (tcpmon, or any other) and see what happens ...

On 3/13/07, srika <[EMAIL PROTECTED]> wrote:


I created java type from wsdl, and by using that java type i am calling
that
service.
I use the below code in a LWContainer for invking the service.

IAETrackerWSClient service = new IAETrackerWSClient();
IAETrackerWSSoap client = (IAETrackerWSSoap)service.getIAETrackerWSSoap();
String fromTracker = client.submitOrder("<test>hi</test>", "test", true);

and while i test it using maven test i got the below error.

org.codehaus.xfire.XFireRuntimeException: Could not invoke service..
Nested
exception is org.codehaus.xfire.fault.XFireFault:
System.Web.Services.Protocols.SoapException: Tracker Error
   at IAETracker.IAETrackerWS.SubmitOrder(String XML, String Queue,
Boolean
ApplyPreferences)
org.codehaus.xfire.fault.XFireFault:
System.Web.Services.Protocols.SoapException: Tracker Error
   at IAETracker.IAETrackerWS.SubmitOrder(String XML, String Queue,
Boolean
ApplyPreferences)
        at
org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(
Soap11FaultSerializer.java:31)
        at
org.codehaus.xfire.fault.SoapFaultSerializer.readMessage(
SoapFaultSerializer.java:28)
        at
org.codehaus.xfire.soap.handler.ReadHeadersHandler.checkForFault(
ReadHeadersHandler.java:111)
        at
org.codehaus.xfire.soap.handler.ReadHeadersHandler.invoke(
ReadHeadersHandler.java:67)
        at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java
:131)
        at org.codehaus.xfire.client.Client.onReceive(Client.java:382)
        at
org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(
HttpChannel.java:139)
        at
org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
        at
org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java
:26)
        at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java
:131)
        at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:75)
        at org.codehaus.xfire.client.Client.invoke(Client.java:335)
        at
org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)
        at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
        at $Proxy13.submitOrder(Unknown Source)
        at

com.sterling.sif.ws.backgroundcheck.serviceclient.TrackerServiceClient.onMessageExchange
(TrackerServiceClient.java:70)
        at

org.apache.servicemix.components.util.ComponentAdaptorMEListener.onMessageExchange
(ComponentAdaptorMEListener.java:47)
        at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(
DeliveryChannelImpl.java:624)
        at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(
AbstractFlow.java:170)
        at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java
:177)
        at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java
:227)
        at
org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java
:291)
        at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:595)


Could anyone suggest me the remeady for this?

Thanks in advance.
srika.
--
View this message in context:
http://www.nabble.com/error-in-calling-wsdl-%28LWContainer%29-tf3394388s12049.html#a9449724
Sent from the ServiceMix - User mailing list archive at Nabble.com.




--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/

Reply via email to