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: > > > one > two > > > It should say this: > > > > A valid instance of this schema might look like this: > > > one > two > > 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: > > > > > > 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-user&m=112241677227703&w=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-user&m=111823412914728&w=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 > > > > > > > > > >
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:
one
two
It should say this:
A valid instance of this schema might look like this:
one
two
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:
>
>
> 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-user&m=112241677227703&w=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-user&m=111823412914728&w=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)
> >
> >
> >
> >
> >
> > ...
> >
> > same thing's happening on the request side as well -
> >
> >
> >
> > FooTest
> > Vo
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: one two It should say this: A valid instance of this schema might look like this: one two 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:> >> 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-user&m=112241677227703&w=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-user&m=111823412914728&w=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-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)> >> > > > amgen.com/freezer/data">> >> > > > ...> >> > same thing's happening on the request side as well - > >> > > > amgen.com/freezer/data ">> > FooTest> > Volume> > > > 1> > 2> > ...> >> > is it a WSDL issue? i import the type XSD thus:> > 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/">> > amgen.com/freezer/data ">> > amgen.com/freezer/data">> > amgen.com/freezer/data"> > schemaLocation="freezer-data.xsd"/>> > ...> > > >type="data:TFindVialsByAttributesRequest"/>> > > >type="data:TFindVialsByAttributesResponse"/>> > > > > > ...> > > > > > element="data:findVialsByAttributesRequest"/>> > > > > > > > element="data:findVialsByAttributesResponse"/>> > > > ...> >> > i noticed the XSD doesn't explicitly call ou
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: > > > 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-user&m=112241677227703&w=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-user&m=111823412914728&w=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) > > > > > > > > > > > > ... > > > > same thing's happening on the request side as well - > > > > > > > > FooTest > > Volume > > > > 1 > > 2 > > ... > > > > is it a WSDL issue? i import the type XSD thus: > > > 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/";> > > > > > >> schemaLocation="freezer-data.xsd"/> > > ... > >>type="data:TFindVialsByAttributesRequest"/> > >>type="data:TFindVialsByAttributesResponse"/> > > > > > > ... > > > > > element="data:findVialsByAttributesRequest"/> > > > > > > > element="data:findVialsByAttributesResponse"/> > > > > ... > > > > i noticed the XSD doesn't explicitly call out qualified elements: > > > targetNamespace="urn:amgen.com/freezer/data" > > xmlns:data ="urn:amgen.com/freezer/data" > > xmlns:xsd = "http://www.w3.org/2001/XMLSchema";> > > > > > > ... > > > > 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. > > > > == > > > > > > > -- Davanum Srinivas : http://wso2.com/blogs/
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: 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-user&m=112241677227703&w=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-user&m=111823412914728&w=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) > > > > > > ... > > same thing's happening on the request side as well - > > > > FooTest > Volume > > 1 > 2 > ... > > is it a WSDL issue? i import the type XSD thus: >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/";> > > >schemaLocation="freezer-data.xsd"/> > ... > type="data:TFindVialsByAttributesRequest"/> > type="data:TFindVialsByAttributesResponse"/> > > > ... > > element="data:findVialsByAttributesRequest"/> > > > element="data:findVialsByAttributesResponse"/> > > ... > > i noticed the XSD doesn't explicitly call out qualified elements: > targetNamespace="urn:amgen.com/freezer/data" > xmlns:data ="urn:amgen.com/freezer/data" > xmlns:xsd = "http://www.w3.org/2001/XMLSchema";> > > > ... > > 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: > > > 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-user&m=112241677227703&w=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-user&m=111823412914728&w=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) > > > > > > > > > > > > ... > > > > same thing's happening on the request side as well - > > > > > > > > FooTest > > Volume > > > > 1 > > 2 > > ... > > > > is it a WSDL issue? i import the type XSD thus: > > > 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/";> > > > > > >> schemaLocation="freezer-data.xsd"/> > > ... > >>type="data:TFindVialsByAttributesRequest"/> > >>type="data:TFindVialsByAttributesResponse"/> > > > > > > ... > > > > > element="data:findVialsByAttributesRequest"/> > > > > > > > element="data:findVialsByAttributesResponse"/> > > > > ... > > > > i noticed the XSD doesn't explicitly call out qualified elements: > > > targetNamespace="urn:amgen.com/freezer/data" > > xmlns:data ="urn:amgen.com/freezer/data" > > xmlns:xsd = "http://www.w3.org/2001/XMLSchema";> > > > > > > ... > > > > 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. > > == > > > > > > > -- Davanum Srinivas : http://wso2.com/blogs/
Re: only top-level element has namespace [RESOLVED]
that was exactly the email i was hunting for and it WORKED PERFECTLY: 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-user&m=112241677227703&w=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-user&m=111823412914728&w=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) > > > > > > ... > > same thing's happening on the request side as well - > > > > FooTest > Volume > > 1 > 2 > ... > > is it a WSDL issue? i import the type XSD thus: >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/";> > > >schemaLocation="freezer-data.xsd"/> > ... > type="data:TFindVialsByAttributesRequest"/> > type="data:TFindVialsByAttributesResponse"/> > > > ... > > element="data:findVialsByAttributesRequest"/> > > > element="data:findVialsByAttributesResponse"/> > > ... > > i noticed the XSD doesn't explicitly call out qualified elements: > targetNamespace="urn:amgen.com/freezer/data" > xmlns:data ="urn:amgen.com/freezer/data" > xmlns:xsd = "http://www.w3.org/2001/XMLSchema";> > > > ... > > 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. > == > >
