xsi:type in the SOAP body -- Is this a bug?

[Jason Dobies <jd...@gestalt-llc.com>]

Greetings All,
 
I am having an issue with the SOAP body that is sent from the Axis 1.2
generated stub. The issue surrounds the following schema element:
 
    <xs:simpleType name="DisclaimerIdentifier">
        <xs:restriction base="xs:long"/>
    </xs:simpleType>

When invoking the service through the stub, the SOAP body contains the
following:
 
<disclaimerId xsi:type="xsd:long">12345</disclaimerId>
 
The service on the other end is having trouble consuming this because of
the xsi:type attribute. While I am interested in the answer, whether or
not the server should accept this is out of my hands due to political
reasons (but like I said, if you can enlighten me either way I'd be
appreciative).
 
The following line is in my stub:
 
    _call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR,
Boolean.FALSE);
 
That was put there automatically when the stub was generated. From the
API, it looks like that should remove the xsi:type attributes from the
SOAP body, but I still see them in there. Is this a bug, or am I missing
something?
 
Thanks,
 
- Jason
 
Jason Dobies
Java Application Developer
Gestalt LLC
jdobies@gestalt-llc.com
856.614.5433