Thanks, Mark.  I'm afraid your suspicion is correct, though.  I looked
into this SerializationContext class and it looks like the right place
indeed, except that there doesn't seem to be a way to configure this
SerializationContext using the createCall - invoke way of calling a
service... Looks like I'll have to go with the XSLT transformation for
now.

Regards,
Jan


On 5/26/05, Mark Ford <[EMAIL PROTECTED]> wrote:
> The only place where I've seen something like this is in the
> SerializationContext.getPrefixForURI(String uri, String defaultPrefix). When
> calling this, you'll get the existing prefix mapped to the namespace or the
> default prefix you passed in. If you passed null for the default and there
> is no existing mapping, then you'll get a generated prefix of the form "ns"
> + counter.
> 
> This worked out well for me since I'm using the axis serialization classes
> directly as opposed to generated stubs. I'm not sure if it's much help to
> you though.
> 
> -----Original Message-----
> From: Jan Delannoy [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 25, 2005 12:46 PM
> To: [email protected]
> Subject: namespace prefix question
> 
> Hi,
> 
> I'm using an Axis generated stub class to call a web service. The generated
> messages use namespace prefixes like ns1, ns2, ns3, etc.
> even when it's the same namespace.  Can I force Axis to use a namespace
> prefix of my choice for a given namespace? I'm using Axis
> 1.2 final.
> 
> Many thanks,
> Jan
> 
> 
>

Reply via email to