No, unfortunately, even if you carefully set the prefixes, when you return the Document they are ignored and replaced by ns1, ns2, etc. (I'm using message style -- see my post earlier today.) Apparently it's not just me, as Ken is reporting the same problem.
I'm not saying there's not a way to do it, but the expected way (setting it in the DOM document) doesn't seem to work. I traced through the code and I can't see how it can work. Any friendly suggestions are appreciated. -- Fred -----Original Message----- From: Mark Galbreath [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 2:49 PM To: [EMAIL PROTECTED] Subject: RE: Doc/literal newbie needs help what do you mean? The ns prefixes are completely arbitrary and you have total control. Mark -----Original Message----- From: Barrett, Fred [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 2:43 PM To: '[EMAIL PROTECTED]' Cc: [EMAIL PROTECTED]; '[EMAIL PROTECTED]' Subject: RE: Doc/literal newbie needs help I just posted a message today complaining that I seem to have no control over the namespace prefixes. As usual, no responses... maybe you'll have better luck. -- Fred B. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 2:38 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Doc/literal newbie needs help I'm not sure I can do what I want to do and in frustration am hoping someone on this list can help me. I'm trying to use Axis as a client to a complex schema-defined web service. I have samples of the messages I should be sending, but I can't seem to get very close using the message format in Axis. For example, I want to put schemaLocation into the Envelope: <env:Envelope xmlns:sma="SMA" xmlns:env="http://www.w3.org/2001/09/soap-envelope"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation = "SMA /xmls/SMAS/SMAS.xsd http://www.w3.org/2001/09/soap-envelope /xmls/SMAS/soap-envelope.xsd"> But I can't seem to figure out how to get schemaLocation defined. I also can't seem to change the namespace for the document; it comes out "soapenv" no matter what I do. I know that's not a big deal, but it means I don't have control over it and I'm a control freak ;-> On to the header: Here's what I want to produce: <env:Header actor = "smas.prod.nscc.com" mustUnderstand = "1"> But the Axis methods only seem to provide for setting actor and mustUnderstand for a SOAPHeaderElement, so what I get is: <soapenv:Header> <ns1:SMA_RM soapenv:role="smas.prod.nscc.com" soapenv:mustUnderstand="1" xmlns :ns1="SMA_RM"/> </soapenv:Header> I don't know if they are functionally identical. Try as I might, I could not change the namespace here either ... probably because of my abject ignorance of most things XML. (I'm not a big fan of repeating "ns1" and "ns2" all over the place.) Am I trying to do the impossible? or am I missing the front door and trying to climb in through the chimney? Ken. -- Ken Kress [EMAIL PROTECTED] SAS, The Bank of New York 484.605.4834 ________________________________________________________________________ The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although The Bank of New York attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses.
