axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ebert, Chris" <>
Subject RE: only top-level element has namespace
Date Thu, 03 Nov 2005 01:59:40 GMT
I've wondered this myself.

It resets the 'default' namespace to nothing -- the enclosing message
element usually has your namespace. As far as I can tell, it works for
Axis and gSOAP this way. I'm a little mystified: when I define my
_schema_ all the sub-elements are in my namespace, but it still works.

Are you just curious, or do you have a problem you're trying to track


-----Original Message-----
From: Ron Reynolds [] 
Sent: Wednesday, November 02, 2005 16:18
Subject: 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)

  <findVialsByAttributesResponse xmlns="">
   <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="">
  <materialTypeName xmlns="">FooTest</materialTypeName>
  <attributeName xmlns="">Volume</attributeName>
  <attributeValues xmlns="">

is it a WSDL issue?  i import the type XSD thus:
<wsdl:definitions targetNamespace  = ""
                  xmlns:tns        = ""
                  xmlns:data       = ""
                  xmlns:soap       =
                  xmlns:xsd        = ""
                  xmlns:wsdl       = "">
  <wsdl:types xmlns="">
    <xsd:schema targetNamespace="">
      <xsd:import namespace=""
      <xsd:element name="findVialsByAttributesRequest"
      <xsd:element name="findVialsByAttributesResponse"
  <wsdl:message name="FindVialsByAttributesRequest">
    <wsdl:part name="request"
  <wsdl:message name="FindVialsByAttributesResponse">
    <wsdl:part name="response"

i noticed the XSD doesn't explicitly call out qualified elements:
    xmlns:data     =""
    xmlns:xsd      = "">
  <xsd:complexType name="TLocation">

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, ;-)

View raw message