Can you post the SOAP message you receive, and the wsdl and jaxrpc-mapping of
your service?
-Jason
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981179#3981179
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981179
__
as said, in previous posts, I migrated to jbossws1.0.3.G.A.
But no luck either..
Can anyone please help me out. It seems it is not that straight forward as I
thought.
Ramana
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979599#3979599
Reply to the post :
Hi,
Please help me.Anyone solved this problem.
I am also getting similar exception..
at
org.jboss.ws.server.ServiceEndpointInvoker.getDispatchDestination(ServiceEndpointInvoker.java:175)
at
org.jboss.ws.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:110)
at
This mesage would occur if the endpoint receives a message that cannot be
dispatched (i.e. it does not conform to the abstract contract defined in
wsdl+schema)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977725#3977725
Reply to the post :
http://www.jbos
Anybody have a solution for this? I'm having the same problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975866#3975866
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975866
___
Turns out I was using version 1.0.2 of wstools on a server running 1.0.3 and
that didn't work too well..
No problems when switching to the right wstools.
:P
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971893#3971893
Reply to the post :
http://www.jboss
