[ http://jira.codehaus.org/browse/XFIRE-706?page=comments#action_79988 ] Dan Diephouse commented on XFIRE-706: -------------------------------------
I checked in to this - the SoapSerializerHandler doesn't need to consult the binding. The SoapSerializer wraps the serializer provide by the binding. So in essence its equivalent to: MessageSerializer ser = binding.getSerializer(operation); ser = new SoapSerializer(ser); I looked at the source code and I don't think there is any place where we aren't calling binding.getSerializer(operation) correctly. Are you sure there is an issue here? > 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 > Assigned To: Dan Diephouse > Fix For: 1.2.3 > > > 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
