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:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:SOAP-ENV="http://schemas.xmlsoap.
om SOAP
headers as appropriate.
Once again, thanks very much for your time and efforts on this project.
Sincerely,
Alastair Fettes
This e-mail and any attachments are intended solely for the use of the
intended recipient(s) and may contain legally privileged, proprietary
and/or confidential inform
hat I return back.
- http://edge.avaya.com/xsd";>
-
0
Success
This is what they expect
- http://edge.avaya.com/xsd";>
-
http://edge.avaya.com/xsd";>0
http://edge.avaya.com/xsd";>Success
Samir
--- Alastair FETTES <[EMAIL PROTECTED]>
wrote
Samir.
If your clients can't handle the difference between 0 and 0
then I wouldn't bother using SOAP or web services. These are equivalent
in XML. I can understand suppressing the prefix in regards to efficency
and the size of the message but not to support a client that doesn't
handle XML prope
I suggest using commons-logging as your wrapper around log4j.
Make sure to code it for optimization:
if (log.isDebugEnabled())
{
log.log("Message");
}
Things like that.
Cheers.
From: Rachel Primrose [mailto:[EMAIL PROTECTED]
Sent: Monday, December 10,
ate manually I can set their qname, etc
but how do I set the _contents_ of this header?
Example header:
bar.server.com
Thanks in advance.
Alastair Fettes
MacDonald, Dettwiler and Associates
afettes at mdacorporation dot com
This e-mail and any attachments are intended solely for the use of
