Dear Anne, I am not using WSSJ. We use a common service within our institution for signing and verification of messages. I am using the SAAJ APIs to extract the element tags from the SOAP message I receive. However when extracting the elements, the message is serialized by AXIS and it is during this process that the origiinal prefix values are ignored. Can using WSS4J solve my problem? You have mentioned the following: If the application needs to maintain the contents of the original SOAP message in its pure form, then you must use the Messaging API and process the raw XML. So does that mean the only way to overcome the problem is: I need to write my own HTTPSender class. The entire message I response I receive in the bytes, will have to be converted to an XML and then the data extracted without the interferrence of AXIS? Thanks regards, Anup Anne Thomas Manes <[EMAIL PROTECTED]> wrote: Prefixes are significant when the XML message or a portion thereof is being signed.
Anup -- you have to make sure you process the signature before Axis begins to process it. Are you using WSS4J to process the signature? If the application needs to maintain the contents of the original SOAP message in its pure form, then you must use the Messaging API and process the raw XML. Anne On 3/8/07, Tom Jordahl wrote: > > > > > No, namespace prefixes are not significant in SOAP messages. They are just > a shorthand. > > Axis doesn't preserve them in any way (nor do most other toolkits that I am > aware of). > > > > > -- > > Tom Jordahl > > Adobe ColdFusion Team > > ________________________________ > > > From: anup bansal [mailto:[EMAIL PROTECTED] > Sent: Saturday, March 03, 2007 3:39 AM > To: axis-dev@ws.apache.org > Subject: Re: Problem with the namespace prefix in Axis > > > > > > Hi All, > > > > > > Has anyone never faced this problem before? > > > I debugged the Axis 1.4 code and found that during serialization of the > input > > > received, (Client respone handler), the URIs are mapped to default namespace > prefix values and the original prefixes received with the mesages are > ignored. > > > Is there a way to get around this and make Axis use the same prefixes as > recevied? Can I set some prameter in my client-config.wsdd to disable this? > > > I have already tried the > "enableNamespacePrefixOptimization" property but it too > does not work? > > > > > > Please help me.. Its really very urgent. > > > > > > Thanks & regards, > > > Anup > > Anne Thomas Manes wrote: > > > As long as the prefix maps to the correct namespace URI, the messages > are semantically identical. Your handler should be to handle any > prefix string. > > Anne > > On 2/27/07, anup bansal wrote: > > Hi All, > > > > I am using Axis 1.4 for accessing a third party weservice. I am able to > > connect to the service and receive the response. > > > > The prefixes in the response I receive is not the same as the the one > sent > > by the service. The difference lies in the name space prefix values. > > As a result the response header is not being validated. > > > > Axis is replacing the namespace prefixes with its own prefix values. > > For e.g. the prefix value sent for the SOAP Body is soap12, where as Axis > > converts it into soapenv. > > > > Is this a bug in Axis or is there a way to get around this problem? Can > you > > please help? > > > > Regards, > > Anup > > > > ________________________________ > > Here's a new way to find what you're looking for - Yahoo! Answers > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > ________________________________ > > > Here's a new way to find what you're looking for - Yahoo! Answers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------- Heres a new way to find what you're looking for - Yahoo! Answers
