Re: only top-level element has namespace [RESOLVED]
Chris, I just noticed a bug in my response -- the page is immutable, so I can't change it. Could you fix it for me? The page says this: A valid instance of this schema might look like this: tns:foobar xmlns:foobar=some-uri fooone/foo bartwo/bar/tns:foobar It should say this: A valid instance of this schema might look like this: tns:foobar xmlns:tns=some-uri fooone/foo bartwo/bar/tns:foobar Thanks, AnneOn 11/3/05, Ebert, Chris [EMAIL PROTECTED] wrote: Addedhttp://wiki.apache.org/ws/FrontPage/Axis/OnlyTopLevelElementHasNamespaceI quoted Anne Thomas Manes and rummaged around in the 2001 Schema RFC to find a relavent bit.As a side note, the Wiki is faboo. Y'all should check it out if youhaven't.Chris-Original Message-From: Davanum Srinivas [mailto: [EMAIL PROTECTED]]Sent: Thursday, November 03, 2005 10:06To: axis-user@ws.apache.orgSubject: Re: only top-level element has namespace [RESOLVED]Could i bug one of you add this to the FAQ wiki? :) http://wiki.apache.org/ws/FrontPage/Axisthanks,dimsOn 11/3/05, Ron Reynolds [EMAIL PROTECTED] wrote: that was exactly the email i was hunting for and it WORKED PERFECTLY: xsd:schema ... elementFormDefault =qualified i knew this question had been asked and answered - just gotta get better at searching the archives i guess (the search form stripped the '=' from my search string and every email and its cousin has xmlns in it.) lots of thanks. :) .ron. I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema.See this post from Anne, where she gives an exampleof how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to everyelement! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED]To:axis-user@ws.apache.org com cc: Subject:onlytop-level element has namespace 11/02/2005 06:18 PM Please respond to axis-useri hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it?(my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn: amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue?i import the type XSD thus: wsdl:definitions targetNamespace= urn: amgen.com/freezer xmlns:tns= urn:amgen.com/freezer xmlns:data = urn:amgen.com/freezer/data xmlns:soap =http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd=http://www.w3.org/2001/XMLSchema xmlns:wsdl =http://schemas.xmlsoap.org/wsdl/ wsdl:types xmlns=urn:amgen.com/freezer/data xsd:schema targetNamespace=urn:amgen.com/freezer/data xsd:import namespace=urn: amgen.com/freezer/data schemaLocation=freezer-data.xsd/ ... xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/ xsd:element name=findVialsByAttributesResponse type=data:TFindVialsByAttributesResponse/ /xsd:schema /wsdl:types ... wsdl:message name=FindVialsByAttributesRequest wsdl:part name=request element=data:findVialsByAttributesRequest/ /wsdl:message wsdl:message name=FindVialsByAttributesResponse wsdl:part name=response element=data:findVialsByAttributesResponse/ /wsdl:message ... i noticed the XSD doesn't explicitly call out qualified elements: xsd:schema targetNamespace=urn:amgen.com/freezer/data xmlns:data =urn: amgen.com/freezer/data xmlns:xsd= http://www.w3.org/2001/XMLSchema xsd:complexType name=TLocation xsd:sequence ... could that be a problem?it still doesn't make sense why the SOAP message would EXPLICITLY strip the namespace from everything except the root element, or does it? :-/ never giving up, ;-) .ron. -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from
RE: only top-level element has namespace [RESOLVED]
I fixed it -- I'm not sure why it's 'Immutable'. I didn't do anything to make it so. It's much less fun to Wiki if others can't play :( Chris -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Monday, November 07, 2005 04:45 To: axis-user@ws.apache.org Subject: Re: only top-level element has namespace [RESOLVED] Chris, I just noticed a bug in my response -- the page is immutable, so I can't change it. Could you fix it for me? The page says this: A valid instance of this schema might look like this: tns:foobar xmlns:foobar=some-uri fooone/foo bartwo/bar /tns:foobar It should say this: A valid instance of this schema might look like this: tns:foobar xmlns:tns=some-uri fooone/foo bartwo/bar /tns:foobar Thanks, Anne On 11/3/05, Ebert, Chris [EMAIL PROTECTED] wrote: Added http://wiki.apache.org/ws/FrontPage/Axis/OnlyTopLevelElementHasNamespace I quoted Anne Thomas Manes and rummaged around in the 2001 Schema RFC to find a relavent bit. As a side note, the Wiki is faboo. Y'all should check it out if you haven't. Chris -Original Message- From: Davanum Srinivas [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Thursday, November 03, 2005 10:06 To: axis-user@ws.apache.org Subject: Re: only top-level element has namespace [RESOLVED] Could i bug one of you add this to the FAQ wiki? :) http://wiki.apache.org/ws/FrontPage/Axis thanks, dims On 11/3/05, Ron Reynolds [EMAIL PROTECTED] wrote: that was exactly the email i was hunting for and it WORKED PERFECTLY: xsd:schema ... elementFormDefault =qualified i knew this question had been asked and answered - just gotta get better at searching the archives i guess (the search form stripped the '=' from my search string and every email and its cousin has xmlns in it.) lots of thanks. :) .ron. I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema. See this post from Anne, where she gives an example of how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED]To: axis-user@ws.apache.org com cc: Subject: only top-level element has namespace 11/02/2005 06:18 PM Please respond to axis-user i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn: amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions targetNamespace = urn: amgen.com/freezer xmlns:tns= urn:amgen.com/freezer
Re: only top-level element has namespace [RESOLVED]
click on UserPreferences and create an id for yourself. -- dims On 11/7/05, Ebert, Chris [EMAIL PROTECTED] wrote: I fixed it -- I'm not sure why it's 'Immutable'. I didn't do anything to make it so. It's much less fun to Wiki if others can't play :( Chris -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Monday, November 07, 2005 04:45 To: axis-user@ws.apache.org Subject: Re: only top-level element has namespace [RESOLVED] Chris, I just noticed a bug in my response -- the page is immutable, so I can't change it. Could you fix it for me? The page says this: A valid instance of this schema might look like this: tns:foobar xmlns:foobar=some-uri fooone/foo bartwo/bar /tns:foobar It should say this: A valid instance of this schema might look like this: tns:foobar xmlns:tns=some-uri fooone/foo bartwo/bar /tns:foobar Thanks, Anne On 11/3/05, Ebert, Chris [EMAIL PROTECTED] wrote: Added http://wiki.apache.org/ws/FrontPage/Axis/OnlyTopLevelElementHasNamespace I quoted Anne Thomas Manes and rummaged around in the 2001 Schema RFC to find a relavent bit. As a side note, the Wiki is faboo. Y'all should check it out if you haven't. Chris -Original Message- From: Davanum Srinivas [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Thursday, November 03, 2005 10:06 To: axis-user@ws.apache.org Subject: Re: only top-level element has namespace [RESOLVED] Could i bug one of you add this to the FAQ wiki? :) http://wiki.apache.org/ws/FrontPage/Axis thanks, dims On 11/3/05, Ron Reynolds [EMAIL PROTECTED] wrote: that was exactly the email i was hunting for and it WORKED PERFECTLY: xsd:schema ... elementFormDefault =qualified i knew this question had been asked and answered - just gotta get better at searching the archives i guess (the search form stripped the '=' from my search string and every email and its cousin has xmlns in it.) lots of thanks. :) .ron. I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema. See this post from Anne, where she gives an example of how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED]To: axis-user@ws.apache.org com cc: Subject: only top-level element has namespace 11/02/2005 06:18 PM Please respond to axis-user i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn: amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions
Re: only top-level element has namespace
Ron, the schema for this document instance: foo xmlns=urn:foo bar xmlns=/bar /foo Would be described thus: schema targetNamespace=urn:foo xmlns=schemans element name=foo complexType sequence element name=bar type=string/ /sequence /complexType /element /schema In this definition, bar is defined as a local element (defined within another structure rather than defined as a direct child of the schema element), and therefore is by default in no namespace (It is not part of urn:foo. If you want to make it part of the targetNamespace, then you must add elementFormDefault=qualified to the schema definition, e.g., schema targetNamespace=urn:foo xmlns=schemans elementFormDefault=qualified element name=foo complexType sequence element name=bar type=string/ /sequence /complexType /element /schema In this instance: foo xmlns=urn:foo snafu xmlns=urn:snafu bar xmlns=/bar /snafu /foo There is no ambiguity. foo is in urn:foo; snafu is in urn:snafu; and bar is in no namespace. In terms of validation, the schema for foo must indicate that snafu is an expected child; and the schema for snafu must indicate that bar is an expected child. AnneOn 11/3/05, Ron Reynolds [EMAIL PROTECTED] wrote: that raises a schema question, since it seems that this:foo xmlns=urn:foobar xmlns=/bar/fooonly makes sense if you combine it with the schema for the namespace urn:foo and you find that it's elementFormDefault=unqualified and thus bar is stillin urn:foo (and not really in no namespace at all).but, what if you had 2 schemas and this XML:foo xmlns=urn:foo snafu xmlns=urn:snafu bar xmlns=/bar/snafu/fooand the schema for urn:snafu was also elementFormDefault=unqualified and also defined an element bar?you would have to specify the namespace onbar to clarify, despite the schema's elementFormDefault or you would havean ambiguity, no?does elementFormDefault only apply when the parent of the element is in the same namespace?(hope this isn't too off-topic for the axis-user@ list) :)ron. Axis sets the default namespace to null because your schema defines the child elements as unqualified. If it didn't set the default namespace to null, then the message would not match the schema. If you add elementFormDefault=qualified to your schema element, then the child elements will be defined as qualified. Anne On 11/3/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema. See this post from Anne, where she gives an example of how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED] To: axis-user@ws.apache.org com cc: Subject: only top-level element has namespace 11/02/2005 06:18 PM Please respond to axis-user i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn:amgen.com/freezer/data http://amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn: amgen.com/freezer/datahttp://amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions targetNamespace = urn:amgen.com/freezer http://amgen.com/freezer xmlns:tns = urn:amgen.com/freezer http://amgen.com/freezer xmlns:data = "" href="http://amgen.com/freezer/data">amgen.com/freezer/data http://amgen.com/freezer/data xmlns:soap = http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd = http://www.w3.org/2001/XMLSchema xmlns:wsdl = http://schemas.xmlsoap.org/wsdl/ wsdl:types xmlns=urn:amgen.com/freezer/datahttp://amgen.com/freezer/data xsd:schema targetNamespace=urn:amgen.com/freezer/datahttp://amgen.com/freezer/data xsd:import namespace=urn:amgen.com/freezer/datahttp://amgen.com/freezer/data schemaLocation=freezer-data.xsd/ ... xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/ xsd:element name=findVialsBy
Re: only top-level element has namespace
I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema. See this post from Anne, where she gives an example of how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED]To: axis-user@ws.apache.org com cc: Subject: only top-level element has namespace 11/02/2005 06:18 PM Please respond to axis-user i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn:amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions targetNamespace = urn:amgen.com/freezer xmlns:tns= urn:amgen.com/freezer xmlns:data = urn:amgen.com/freezer/data xmlns:soap = http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd= http://www.w3.org/2001/XMLSchema; xmlns:wsdl = http://schemas.xmlsoap.org/wsdl/; wsdl:types xmlns=urn:amgen.com/freezer/data xsd:schema targetNamespace=urn:amgen.com/freezer/data xsd:import namespace=urn:amgen.com/freezer/data schemaLocation=freezer-data.xsd/ ... xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/ xsd:element name=findVialsByAttributesResponse type=data:TFindVialsByAttributesResponse/ /xsd:schema /wsdl:types ... wsdl:message name=FindVialsByAttributesRequest wsdl:part name=request element=data:findVialsByAttributesRequest/ /wsdl:message wsdl:message name=FindVialsByAttributesResponse wsdl:part name=response element=data:findVialsByAttributesResponse/ /wsdl:message ... i noticed the XSD doesn't explicitly call out qualified elements: xsd:schema targetNamespace=urn:amgen.com/freezer/data xmlns:data =urn:amgen.com/freezer/data xmlns:xsd = http://www.w3.org/2001/XMLSchema; xsd:complexType name=TLocation xsd:sequence ... could that be a problem? it still doesn't make sense why the SOAP message would EXPLICITLY strip the namespace from everything except the root element, or does it? :-/ never giving up, ;-) .ron. -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended
Re: only top-level element has namespace [RESOLVED]
that was exactly the email i was hunting for and it WORKED PERFECTLY: xsd:schema ... elementFormDefault =qualified i knew this question had been asked and answered - just gotta get better at searching the archives i guess (the search form stripped the '=' from my search string and every email and its cousin has xmlns in it.) lots of thanks. :) .ron. I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema. See this post from Anne, where she gives an example of how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED]To: axis-user@ws.apache.org com cc: Subject: only top-level element has namespace 11/02/2005 06:18 PM Please respond to axis-user i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn:amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions targetNamespace = urn:amgen.com/freezer xmlns:tns= urn:amgen.com/freezer xmlns:data = urn:amgen.com/freezer/data xmlns:soap = http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd= http://www.w3.org/2001/XMLSchema; xmlns:wsdl = http://schemas.xmlsoap.org/wsdl/; wsdl:types xmlns=urn:amgen.com/freezer/data xsd:schema targetNamespace=urn:amgen.com/freezer/data xsd:import namespace=urn:amgen.com/freezer/data schemaLocation=freezer-data.xsd/ ... xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/ xsd:element name=findVialsByAttributesResponse type=data:TFindVialsByAttributesResponse/ /xsd:schema /wsdl:types ... wsdl:message name=FindVialsByAttributesRequest wsdl:part name=request element=data:findVialsByAttributesRequest/ /wsdl:message wsdl:message name=FindVialsByAttributesResponse wsdl:part name=response element=data:findVialsByAttributesResponse/ /wsdl:message ... i noticed the XSD doesn't explicitly call out qualified elements: xsd:schema targetNamespace=urn:amgen.com/freezer/data xmlns:data =urn:amgen.com/freezer/data xmlns:xsd = http://www.w3.org/2001/XMLSchema; xsd:complexType name=TLocation xsd:sequence ... could that be a problem? it still doesn't make sense why the SOAP message would EXPLICITLY strip the namespace from everything except the root element, or does it? :-/ never giving up, ;-) .ron. -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
Re: only top-level element has namespace [RESOLVED]
Could i bug one of you add this to the FAQ wiki? :) http://wiki.apache.org/ws/FrontPage/Axis thanks, dims On 11/3/05, Ron Reynolds [EMAIL PROTECTED] wrote: that was exactly the email i was hunting for and it WORKED PERFECTLY: xsd:schema ... elementFormDefault =qualified i knew this question had been asked and answered - just gotta get better at searching the archives i guess (the search form stripped the '=' from my search string and every email and its cousin has xmlns in it.) lots of thanks. :) .ron. I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema. See this post from Anne, where she gives an example of how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED]To: axis-user@ws.apache.org com cc: Subject: only top-level element has namespace 11/02/2005 06:18 PM Please respond to axis-user i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn:amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions targetNamespace = urn:amgen.com/freezer xmlns:tns= urn:amgen.com/freezer xmlns:data = urn:amgen.com/freezer/data xmlns:soap = http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd= http://www.w3.org/2001/XMLSchema; xmlns:wsdl = http://schemas.xmlsoap.org/wsdl/; wsdl:types xmlns=urn:amgen.com/freezer/data xsd:schema targetNamespace=urn:amgen.com/freezer/data xsd:import namespace=urn:amgen.com/freezer/data schemaLocation=freezer-data.xsd/ ... xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/ xsd:element name=findVialsByAttributesResponse type=data:TFindVialsByAttributesResponse/ /xsd:schema /wsdl:types ... wsdl:message name=FindVialsByAttributesRequest wsdl:part name=request element=data:findVialsByAttributesRequest/ /wsdl:message wsdl:message name=FindVialsByAttributesResponse wsdl:part name=response element=data:findVialsByAttributesResponse/ /wsdl:message ... i noticed the XSD doesn't explicitly call out qualified elements: xsd:schema targetNamespace=urn:amgen.com/freezer/data xmlns:data =urn:amgen.com/freezer/data xmlns:xsd = http://www.w3.org/2001/XMLSchema; xsd:complexType name=TLocation xsd:sequence ... could that be a problem? it still doesn't make sense why the SOAP message would EXPLICITLY strip the namespace from everything except the root element, or does it? :-/ never giving up, ;-) .ron. -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation
RE: only top-level element has namespace [RESOLVED]
Worked for me, too -- Yay! I'm sure ATM will be glad to see that someone remembers what she says :) I'm still left with puzzlement about why Axis happily deserialized XML that, so far as I could tell, had elements in the wrong namespace (the xmlns= means all my lovely sub-elements are in no namespace...), but the idleness of the curiosity has increased considerably... Chris -Original Message- From: Ron Reynolds [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 09:03 To: axis-user@ws.apache.org Subject: Re: only top-level element has namespace [RESOLVED] that was exactly the email i was hunting for and it WORKED PERFECTLY: xsd:schema ... elementFormDefault =qualified i knew this question had been asked and answered - just gotta get better at searching the archives i guess (the search form stripped the '=' from my search string and every email and its cousin has xmlns in it.) lots of thanks. :) .ron. I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema. See this post from Anne, where she gives an example of how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED]To: axis-user@ws.apache.org com cc: Subject: only top-level element has namespace 11/02/2005 06:18 PM Please respond to axis-user i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn:amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions targetNamespace = urn:amgen.com/freezer xmlns:tns= urn:amgen.com/freezer xmlns:data = urn:amgen.com/freezer/data xmlns:soap = http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd= http://www.w3.org/2001/XMLSchema; xmlns:wsdl = http://schemas.xmlsoap.org/wsdl/; wsdl:types xmlns=urn:amgen.com/freezer/data xsd:schema targetNamespace=urn:amgen.com/freezer/data xsd:import namespace=urn:amgen.com/freezer/data schemaLocation=freezer-data.xsd/ ... xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/ xsd:element name=findVialsByAttributesResponse type=data:TFindVialsByAttributesResponse/ /xsd:schema /wsdl:types ... wsdl:message name=FindVialsByAttributesRequest wsdl:part name=request element=data:findVialsByAttributesRequest/ /wsdl:message wsdl:message name=FindVialsByAttributesResponse wsdl:part name=response element=data:findVialsByAttributesResponse/ /wsdl:message ... i noticed the XSD doesn't explicitly call out qualified elements: xsd:schema targetNamespace=urn:amgen.com/freezer/data xmlns:data =urn:amgen.com/freezer/data xmlns:xsd = http://www.w3.org/2001/XMLSchema; xsd:complexType name=TLocation xsd:sequence ... could that be a problem? it still doesn't make sense why the SOAP message would EXPLICITLY strip the namespace from everything except the root element, or does it? :-/ never giving up, ;-) .ron. -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally
Re: only top-level element has namespace
Axis sets the default namespace to null because your schema defines the child elements as unqualified. If it didn't set the default namespace to null, then the message would not match the schema. If you add elementFormDefault=qualified to your schema element, then the child elements will be defined as qualified. AnneOn 11/3/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over thepast few months and I wonder if the behavior you're seeing is because ofthe default unqualified setting that you have in your schema.See this post from Anne, where she gives an example of how this might work:http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite ofyours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2Hope this helps--Meghan_Meghan PietilaJava Middleware ArchitectSales Service Management Program US BankGold 4(651) 205-0904(651) 271-2815 cell[EMAIL PROTECTED]Ron Reynolds[EMAIL PROTECTED]To: axis-user@ws.apache.orgcom cc: Subject:only top-level element has namespace11/02/2005 06:18PMPlease respond toaxis-useri hate to ask a duplicate question but 5 minuets digging in the listarchives was leading nowhere.my question is, what's causing this 'xmlns=' to be added and how do i prevent it?(my service is document-literal) soapenv:BodyfindVialsByAttributesResponse xmlns=urn:amgen.com/freezer/data locations xmlns= location id=1...same thing's happening on the request side as well -soapenv:Body xmlns:wsu=... wsu:Id=id-21465667findVialsByAttributesRequest xmlns=urn: amgen.com/freezer/datamaterialTypeName xmlns=FooTest/materialTypeNameattributeName xmlns=Volume/attributeName attributeValues xmlns=value1/valuevalue2/value...is it a WSDL issue?i import the type XSD thus:wsdl:definitions targetNamespace= urn: amgen.com/freezerxmlns:tns= urn:amgen.com/freezerxmlns:data = urn:amgen.com/freezer/dataxmlns:soap = http://schemas.xmlsoap.org/wsdl/soap/xmlns:xsd= http://www.w3.org/2001/XMLSchemaxmlns:wsdl = http://schemas.xmlsoap.org/wsdl/wsdl:types xmlns=urn:amgen.com/freezer/dataxsd:schema targetNamespace=urn: amgen.com/freezer/dataxsd:import namespace=urn:amgen.com/freezer/dataschemaLocation=freezer-data.xsd /...xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/xsd:element name=findVialsByAttributesResponse type=data:TFindVialsByAttributesResponse//xsd:schema/wsdl:types...wsdl:message name=FindVialsByAttributesRequestwsdl:part name=request element=data:findVialsByAttributesRequest//wsdl:messagewsdl:message name=FindVialsByAttributesResponsewsdl:part name=responseelement=data:findVialsByAttributesResponse/ /wsdl:message...i noticed the XSD doesn't explicitly call out qualified elements:xsd:schematargetNamespace=urn:amgen.com/freezer/data xmlns:data =urn:amgen.com/freezer/dataxmlns:xsd= http://www.w3.org/2001/XMLSchema xsd:complexType name=TLocationxsd:sequence...could that be a problem?it still doesn't make sense why the SOAP messagewould EXPLICITLY strip the namespace from everything except the root element, or does it? :-/never giving up, ;-).ron.--Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation.==
Re: only top-level element has namespace
that raises a schema question, since it seems that this: foo xmlns=urn:foo bar xmlns=/bar /foo only makes sense if you combine it with the schema for the namespace urn:foo and you find that it's elementFormDefault=unqualified and thus bar is still in urn:foo (and not really in no namespace at all). but, what if you had 2 schemas and this XML: foo xmlns=urn:foo snafu xmlns=urn:snafu bar xmlns=/bar /snafu /foo and the schema for urn:snafu was also elementFormDefault=unqualified and also defined an element bar? you would have to specify the namespace on bar to clarify, despite the schema's elementFormDefault or you would have an ambiguity, no? does elementFormDefault only apply when the parent of the element is in the same namespace? (hope this isn't too off-topic for the axis-user@ list) :) ron. Axis sets the default namespace to null because your schema defines the child elements as unqualified. If it didn't set the default namespace to null, then the message would not match the schema. If you add elementFormDefault=qualified to your schema element, then the child elements will be defined as qualified. Anne On 11/3/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema. See this post from Anne, where she gives an example of how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED] To: axis-user@ws.apache.org com cc: Subject: only top-level element has namespace 11/02/2005 06:18 PM Please respond to axis-user i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn:amgen.com/freezer/datahttp://amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/datahttp://amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions targetNamespace = urn:amgen.com/freezerhttp://amgen.com/freezer xmlns:tns = urn:amgen.com/freezer http://amgen.com/freezer xmlns:data = urn:amgen.com/freezer/data http://amgen.com/freezer/data xmlns:soap = http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd = http://www.w3.org/2001/XMLSchema; xmlns:wsdl = http://schemas.xmlsoap.org/wsdl/; wsdl:types xmlns=urn:amgen.com/freezer/datahttp://amgen.com/freezer/data xsd:schema targetNamespace=urn:amgen.com/freezer/datahttp://amgen.com/freezer/data xsd:import namespace=urn:amgen.com/freezer/datahttp://amgen.com/freezer/data schemaLocation=freezer-data.xsd/ ... xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/ xsd:element name=findVialsByAttributesResponse type=data:TFindVialsByAttributesResponse/ /xsd:schema /wsdl:types ... wsdl:message name=FindVialsByAttributesRequest wsdl:part name=request element=data:findVialsByAttributesRequest/ /wsdl:message wsdl:message name=FindVialsByAttributesResponse wsdl:part name=response element=data:findVialsByAttributesResponse/ /wsdl:message ... i noticed the XSD doesn't explicitly call out qualified elements: xsd:schema targetNamespace=urn:amgen.com/freezer/datahttp://amgen.com/freezer/data xmlns:data =urn:amgen.com/freezer/data http://amgen.com/freezer/data xmlns:xsd = http://www.w3.org/2001/XMLSchema; xsd:complexType name=TLocation xsd:sequence ... could that be a problem? it still doesn't make sense why the SOAP message would EXPLICITLY strip the namespace from everything except the root element, or does it? :-/ never giving up, ;-) .ron. -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you
RE: only top-level element has namespace [RESOLVED]
Added http://wiki.apache.org/ws/FrontPage/Axis/OnlyTopLevelElementHasNamespace I quoted Anne Thomas Manes and rummaged around in the 2001 Schema RFC to find a relavent bit. As a side note, the Wiki is faboo. Y'all should check it out if you haven't. Chris -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 10:06 To: axis-user@ws.apache.org Subject: Re: only top-level element has namespace [RESOLVED] Could i bug one of you add this to the FAQ wiki? :) http://wiki.apache.org/ws/FrontPage/Axis thanks, dims On 11/3/05, Ron Reynolds [EMAIL PROTECTED] wrote: that was exactly the email i was hunting for and it WORKED PERFECTLY: xsd:schema ... elementFormDefault =qualified i knew this question had been asked and answered - just gotta get better at searching the archives i guess (the search form stripped the '=' from my search string and every email and its cousin has xmlns in it.) lots of thanks. :) .ron. I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema. See this post from Anne, where she gives an example of how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED]To: axis-user@ws.apache.org com cc: Subject: only top-level element has namespace 11/02/2005 06:18 PM Please respond to axis-user i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn:amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions targetNamespace = urn:amgen.com/freezer xmlns:tns= urn:amgen.com/freezer xmlns:data = urn:amgen.com/freezer/data xmlns:soap = http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd= http://www.w3.org/2001/XMLSchema; xmlns:wsdl = http://schemas.xmlsoap.org/wsdl/; wsdl:types xmlns=urn:amgen.com/freezer/data xsd:schema targetNamespace=urn:amgen.com/freezer/data xsd:import namespace=urn:amgen.com/freezer/data schemaLocation=freezer-data.xsd/ ... xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/ xsd:element name=findVialsByAttributesResponse type=data:TFindVialsByAttributesResponse/ /xsd:schema /wsdl:types ... wsdl:message name=FindVialsByAttributesRequest wsdl:part name=request element=data:findVialsByAttributesRequest/ /wsdl:message wsdl:message name=FindVialsByAttributesResponse wsdl:part name=response element=data:findVialsByAttributesResponse/ /wsdl:message ... i noticed the XSD doesn't explicitly call out qualified elements: xsd:schema targetNamespace=urn:amgen.com/freezer/data xmlns:data =urn:amgen.com/freezer/data xmlns:xsd = http://www.w3.org/2001/XMLSchema; xsd:complexType name=TLocation xsd:sequence ... could that be a problem? it still doesn't make sense why the SOAP message would EXPLICITLY strip the namespace from everything except the root element, or does it? :-/ never giving up, ;-) .ron. -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered
Wikis are faboo (was RE: only top-level element has namespace)
i did and i was thinking about adding it too, but then i ran into the problem of figuring out where to put it - is it client-side? not just - it's server-side too. is it interop? yes, and no. troubleshooting? not really - it didn't create any trouble to being with. common question? i dunno - maybe, maybe not. unfortunately i have no suggestion for a better format, but i agree 100% - Wiki's are great, even if one of my book-writing friends wrote The one problem with wikis is that, like most things maintained by the populous at large (as wikis are), it doesn't necessarily show you what's *right*, just what most people *believe* is right. [A wiki's] definitions of some terms with popular definitions don't always match up to what the creators of the term or the concept intended. but then maybe the creators of these concepts had it wrong and it took the rest of us to get it straight. :) Added http://wiki.apache.org/ws/FrontPage/Axis/OnlyTopLevelElementHasNamespace I quoted Anne Thomas Manes and rummaged around in the 2001 Schema RFC to find a relavent bit. As a side note, the Wiki is faboo. Y'all should check it out if you haven't. Chris -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 10:06 To: axis-user@ws.apache.org Subject: Re: only top-level element has namespace [RESOLVED] Could i bug one of you add this to the FAQ wiki? :) http://wiki.apache.org/ws/FrontPage/Axis thanks, dims On 11/3/05, Ron Reynolds [EMAIL PROTECTED] wrote: that was exactly the email i was hunting for and it WORKED PERFECTLY: xsd:schema ... elementFormDefault =qualified i knew this question had been asked and answered - just gotta get better at searching the archives i guess (the search form stripped the '=' from my search string and every email and its cousin has xmlns in it.) lots of thanks. :) .ron. I'm hoping that Anne Manes or someone more knowledgable will step forward on this one, but I've seen similar questions come up on this list over the past few months and I wonder if the behavior you're seeing is because of the default unqualified setting that you have in your schema. See this post from Anne, where she gives an example of how this might work: http://marc.theaimsgroup.com/?l=axis-userm=112241677227703w=2 Here's another response from Anne, to a question that's the opposite of yours--how to suppress the namespaces being added to every element! http://marc.theaimsgroup.com/?l=axis-userm=111823412914728w=2 Hope this helps-- Meghan _ Meghan Pietila Java Middleware Architect Sales Service Management Program US Bank Gold 4 (651) 205-0904 (651) 271-2815 cell [EMAIL PROTECTED] Ron Reynolds [EMAIL PROTECTED]To: axis-user@ws.apache.org com cc: Subject: only top-level element has namespace 11/02/2005 06:18 PM Please respond to axis-user i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn:amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions targetNamespace = urn:amgen.com/freezer xmlns:tns= urn:amgen.com/freezer xmlns:data = urn:amgen.com/freezer/data xmlns:soap http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsdhttp://www.w3.org/2001/XMLSchema; xmlns:wsdl http://schemas.xmlsoap.org/wsdl/; wsdl:types xmlns=urn:amgen.com/freezer/data xsd:schema targetNamespace=urn:amgen.com/freezer/data xsd:import namespace=urn:amgen.com/freezer/data schemaLocation=freezer-data.xsd/ ... xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/ xsd:element name=findVialsByAttributesResponse type=data:TFindVialsByAttributesResponse/ /xsd:schema /wsdl:types ... wsdl:message name=FindVialsByAttributesRequest wsdl:part name=request element
only top-level element has namespace
i hate to ask a duplicate question but 5 minuets digging in the list archives was leading nowhere. my question is, what's causing this 'xmlns=' to be added and how do i prevent it? (my service is document-literal) soapenv:Body findVialsByAttributesResponse xmlns=urn:amgen.com/freezer/data locations xmlns= location id=1 ... same thing's happening on the request side as well - soapenv:Body xmlns:wsu=... wsu:Id=id-21465667 findVialsByAttributesRequest xmlns=urn:amgen.com/freezer/data materialTypeName xmlns=FooTest/materialTypeName attributeName xmlns=Volume/attributeName attributeValues xmlns= value1/value value2/value ... is it a WSDL issue? i import the type XSD thus: wsdl:definitions targetNamespace = urn:amgen.com/freezer xmlns:tns= urn:amgen.com/freezer xmlns:data = urn:amgen.com/freezer/data xmlns:soap = http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd= http://www.w3.org/2001/XMLSchema; xmlns:wsdl = http://schemas.xmlsoap.org/wsdl/; wsdl:types xmlns=urn:amgen.com/freezer/data xsd:schema targetNamespace=urn:amgen.com/freezer/data xsd:import namespace=urn:amgen.com/freezer/data schemaLocation=freezer-data.xsd/ ... xsd:element name=findVialsByAttributesRequest type=data:TFindVialsByAttributesRequest/ xsd:element name=findVialsByAttributesResponse type=data:TFindVialsByAttributesResponse/ /xsd:schema /wsdl:types ... wsdl:message name=FindVialsByAttributesRequest wsdl:part name=request element=data:findVialsByAttributesRequest/ /wsdl:message wsdl:message name=FindVialsByAttributesResponse wsdl:part name=response element=data:findVialsByAttributesResponse/ /wsdl:message ... i noticed the XSD doesn't explicitly call out qualified elements: xsd:schema targetNamespace=urn:amgen.com/freezer/data xmlns:data =urn:amgen.com/freezer/data xmlns:xsd = http://www.w3.org/2001/XMLSchema; xsd:complexType name=TLocation xsd:sequence ... could that be a problem? it still doesn't make sense why the SOAP message would EXPLICITLY strip the namespace from everything except the root element, or does it? :-/ never giving up, ;-) .ron.
