I don't think your problem is related to those namespace, it's
probably more to do with the way arrays are encoded (using
soapenc:Array). You might want to try a document/literal approach
instead (style=DOCUMENT or WRAPPED in Java2Wsdl).
Regards,
Jan
On 6/2/05, Dave [EMAIL PROTECTED] wrote:
message is what Axis is generating for me now.
I would really appreciate it if someone could help me out with this,
even just letting me know that this isn't possible would already be
helpfull...
Many thanks,
Jan
PS: My old question (see below) is also still open...
On 5/25/05, Jan Delannoy
an intermediary XSLT transformation, or 2)
make Axis generate explicit namespaces. I'd rather go for 2...
Regards,
Jan
On 5/27/05, Tom Oinn [EMAIL PROTECTED] wrote:
Jan Delannoy wrote:
Hi again,
I would really appreciate it if someone could help me out with this,
even just letting me know
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: axis-user@ws.apache.org
Subject: namespace prefix question
Hi,
I'm using an Axis generated stub class
on the part definition.
- children of the accessor elements correspond to the structure
defined in the schema that defines the accessor element type
structures.
Anne
On 5/25/05, Jan Delannoy [EMAIL PROTECTED] wrote:
If I'm not mistaking, when the schema elementFormDefault is set to
qualified
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
Hi,
I'm a bit confused about sending SOAP messages over JMS using Axis. I
have a WSDL file describing a web service with a SOAP over JMS
binding, and I specified the address like in the JMS example included
with Axis 1.2, something like jms:/MyQ?myParams. I generated stubs
using WSDL2Java and
