axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anup bansal <>
Subject Re: Problem with the namespace prefix in Axis
Date Sat, 03 Mar 2007 08:38:49 GMT
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
  Please help me.. Its really very urgent.
  Thanks & regards,

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.


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:
For additional commands, e-mail:

 Here’s a new way to find what you're looking for - Yahoo! Answers 
View raw message