I've created a jira issue and attached the SOAP messages:
http://jira.codehaus.org/browse/XFIRE-1035. The only significant
difference I see is the xmlns:ns1="urn:XXXX:schemas:XXX:1.0" at the Body
element. Thanks again.
This is my first jira issue, so I hope it is all right.
Thanks.
Jorge Rodríguez Sacristán escribió:
Hi again,
I've got the xml that the server receives. The xml generated by xfire
1.2.6 adds a new namespace with prefix ns1 at the root element. That
namespace is already defined with a different prefix. Why is this
happening? Is there anyway to solve it?
Thanks.
Jorge Rodríguez Sacristán escribió:
Hi there!
I'm using xfire and xmlbeans with a webservice that receives a signed
xml. I was working with xfire 1.2.3 and it worked fine, but when I've
changed it to xfire 1.2.6 I have a problem as it seems that the
signature is not valid. I haven't changed anything else. I was
working with one webservice with xfire 1.2.6 and two clients, one
with 1.2.3, working fine, and the other with 1.2.6, which didn't
work. I've updated from 1.2.3 to 1.2.6 and now none of the clients
work. Is it possible that it is changing the underlying xml in some
way it didn't before? As I'm signing the xml before sending it, any
change on the xml would turn into a non valid signature.
Thanx!
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
