RE: Soap namespace problem

[Prakasa Nedunuri \(pnedunur\)]

Title: Nachricht

Hi Werner,

  Thanks for your email. I can understand if this is being done as part of the canonicalization but why

should the original message change after message is processed.

 

To precisely tell you, this is happening in EnvelopeIdResolver class by XMLUtils.circumventBug2650(doc) method.

When I perform signing on XML msg, using xmlsec library, I don't see namespaces getting added in the processed

XML message. So this problem seems to be unique to wss4j library.

 

rgds,

Prakasa

---

From: Dittmann, Werner [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 21, 2005 11:15 PM
To: Prakasa Nedunuri (pnedunur); wss4j-dev@ws.apache.org
Subject: AW: Soap namespace problem

Prakasa,

 

during processing of the doument this is true. The handlers perform

c14n before the hand back the SOAP request to Axis. This is implicitly

done via a helper method we use from the xml-sec library. Thus,

the message that is put "on the wire" should be c14n.

 

At which point of message processing do you trace?

 

Regards,

Werner

-----Ursprüngliche Nachricht-----
Von: Prakasa Nedunuri (pnedunur) [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 22. Juli 2005 03:02
An: wss4j-dev@ws.apache.org
Betreff: Soap namespace problem

Hi,

  I am trying to sign a soap body and after signing I see that wss4j adds all the namespaces existing in the soap message in each and every element.

I am trying to do canonicalization algorithm. Is there anyway I can signing done with adding namespaces or is this a known issue.

 

rgds,

Prakasa