The MessageBinding isn't smart enough to determine the operation. The
MessageBinding doesn't read any of the message at all, it just assumes
one operation You can get around this by using SOAPActions,
WS-Addressing actions or writing a Handler that determines the operation.
- Dan
Tyler Nelson wrote:
Hi Guys,
I'm having an issue while using my own WSDL and MessageBinding with
xfire.
Looks like the SoapBodyHandler is looking for a message serializer
depending on the operation from the MessageExchange. However that
operation is always null. Then it looks for a default serializer,
however since ObjectServiceFactory sets the create default bindings to
false that is null also.
Then i get a null pointer when the serializer tries to read the message.
For now i extended ObjectFactory to set the default bindings, it is
kind of a hack but it works. :)
My question is where is the operation in MessageExchange suppose to be
set? Am i missing something obvious?
Thanks,
Tyler
--
Dan Diephouse
(616) 971-2053
Envoi Solutions LLC
http://netzooid.com
