[
http://jira.codehaus.org/browse/XFIRE-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99345
]
Jorge RodrÃguez commented on XFIRE-1035:
----------------------------------------
The code where the client is instantiated:
Service serviceModel = new
XmlBeansServiceFactory().create(IncomingService.class);
IncomingService service = (IncomingService) new
XFireProxyFactory().create(serviceModel, host+serviceURL);
> Different SOAP message from version 1.2.3 to 1.2.6
> --------------------------------------------------
>
> Key: XFIRE-1035
> URL: http://jira.codehaus.org/browse/XFIRE-1035
> Project: XFire
> Issue Type: Bug
> Affects Versions: 1.2.6
> Reporter: Jorge RodrÃguez
> Assignee: Dan Diephouse
> Priority: Minor
> Attachments: SOAPv123.xml, SOAPv126.xml
>
>
> I have a client working with Xfire 1.2.3 that is sending a XML and a
> signature for this XML. It was working fine but when I've updated to XFire
> 1.2.6 the webservice fails to validate the signature. I've seen that there's
> an useless namespace declaration at the SOAP Body, wich doesn't appear with
> XFire 1.2.3.
> I'm using XMLBeans for binding.
> I attach the two SOAP messages.
--
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