@Alaistair: It would surprise me if the example you cite conformed to
the XML specs, because it would break compatibility with non namespace
aware parsers. Anyway, this has nothing to do with the problem Andrew
faces.
@Andrew: The value of the namespace prefix (soapenv or SOAP-ENV)
indeed doesn't matter. The only thing that is relevant is the
namespace URI it is bound to (http://schemas.xmlsoap.org/soap/
envelope/). Do you have any idea what Web service framework the server
uses?
Regards,
Andreas
On 11 Jan 2008, at 20:39, Alastair FETTES wrote:
Hi Andrew.
Theoretically soapenv should be perfectly acceptable. Irregardless of
what the prefix is, as long as the actual namespace is the same it
should recognize things appropriately.
Take this silly example:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
...
</SOAP-ENV:Envelope>
Theoretically that should work without error.
Cheers.
Alastair
-----Original Message-----
From: Andrew Wood [mailto:[EMAIL PROTECTED]
Sent: Friday, January 11, 2008 11:32 AM
To: [email protected]
Subject: SOAP-ENV versus soapenv
When creating SOAP tags is there a choice of using either SOAP-ENV or
soapenv? I thought it had to be SOAP-ENV but my Axis client is using
soapenv, and I think this is probably the cause for the server moaning
that the start or end tags of the SOAP message are missing.
For example Axis sends
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/
envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soapenv:Body>........
And the server (not Axis) says
<SOAP-ENV:faultcode>Client.ImproperlyFormattedMessage</SOAP-
ENV:faultcode>
<SOAP-ENV:faultstring>The message either has no begin tag or is
missing
the end tag. In either case, the message was not formatted
correctly.</SOAP-ENV:faultstring>
Am I right or is soapenv perfectly acceptable?
Thanks
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
