It should be possible. You have problem with jibx because "out"
element isn't configured in jibx mapping.So you can change response
name on server side or change jibx mapping to accept out as name of
response.
On 3/4/07, Irshad Buchh <[EMAIL PROTECTED]> wrote:
Hi,
Can we use different service factories for deploying a webservice and
consuming the same webservice. We deployed a webservice using xmlbeans+xfire
and one of our client tried to consume this webservice using xfire+Jibx
service factory. It does not work.
--Irshad.
===================================================
The error stack is:
Exception in thread "main" org.codehaus.xfire.XFireRuntimeException: Could
not invoke service.. Nested exception is
org.codehaus.xfire.fault.XFireFault: Could not read Jibx type.. Nested
exception is org.jibx.runtime.JiBXException: No unmarshaller for element
"{http://codehaus.xfire.org/services}out"; (line 1, col 241, in item)
org.codehaus.xfire.fault.XFireFault: Could not read Jibx type.. Nested
exception is org.jibx.runtime.JiBXException: No unmarshaller for element
"{http://codehaus.xfire.org/services}out"; (line 1, col 241, in item)Hello
Irshad
at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
at org.codehaus.xfire.client.Client.onReceive(Client.java:386)
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 $Proxy1.getItem(Unknown Source)
at
webservices.xfire.domain.OrderXFireClient.main(OrderXFireClient.java:43)
Caused by: org.codehaus.xfire.XFireRuntimeException: Could not read Jibx
type.. Nested exception is org.jibx.runtime.JiBXException: No unmarshaller
for element "{http://codehaus.xfire.org/services}out"; (line 1, col 241, in
item)
at org.codehaus.xfire.jibx.JibxType.readObject(JibxType.java:106)
at
org.codehaus.xfire.aegis.AegisBindingProvider.readParameter(AegisBindingProvider.java:162)
at
org.codehaus.xfire.service.binding.AbstractBinding.read(AbstractBinding.java:206)
at
org.codehaus.xfire.service.binding.WrappedBinding.readMessage(WrappedBinding.java:50)
at
org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Client.onReceive(Client.java:382)
... 10 more
Caused by: org.jibx.runtime.JiBXException: No unmarshaller for element
"{http://codehaus.xfire.org/services}out"; (line 1, col 241, in item)
at
org.jibx.runtime.impl.UnmarshallingContext.unmarshalElement(UnmarshallingContext.java:2535)
at org.codehaus.xfire.jibx.JibxType.readObject(JibxType.java:101)
... 16 more
--
View this message in context:
http://www.nabble.com/A-Simple-Question.-tf3342264.html#a9295401
Sent from the XFire - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
