[
http://jira.codehaus.org/browse/XFIRE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Diephouse updated XFIRE-706:
--------------------------------
Fix Version/s: (was: 1.2.6)
1.2.7
> SoapSerializerHandler doesn't consult the binding to set the serializer on
> the OutMessage
> -----------------------------------------------------------------------------------------
>
> Key: XFIRE-706
> URL: http://jira.codehaus.org/browse/XFIRE-706
> Project: XFire
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: n/a
> Reporter: Ryan Heaton
> Assignee: Dan Diephouse
> Fix For: 1.2.7
>
>
> When setting the serializer on the out message, the SoapSerializerHandler
> doesn't consult the binding for the serializer for the specific operation,
> like it does in the PostInvocationHandler. This causes client-side
> invocations using the XFireProxyFactory to not serialize the client-side
> messages correctly if the serializer for an operation was specifically set
> (like it is for the JAXWSServiceFactory).
> It might not be a problem with the SoapSerializerHandler... maybe the
> binding-specified serializer should be set by another handler?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
