Wanting xsd:unsignedByte[] as short[] and not UnsignedByte[]
------------------------------------------------------------
Key: AXIS-1930
URL: http://issues.apache.org/jira/browse/AXIS-1930
Project: Axis
Type: Bug
Components: WSDL processing
Versions: 1.2RC3
Environment: Running on Windows XP Professional
Using Java 1.5.0_02, JWSDP 1.4, Axis 1.2RC3
Reporter: Mike Moran
Attachments: UnsignedByteExample.zip
A section from my original email to axis-user
(http://marc.theaimsgroup.com/?l=axis-user&m=111349169401343&w=2)
can be seen below. I will attach a full example once this bug is created.
Email:
"I am currently moving over from a Java client api generated from WSDL using
JAX-RPC 1.4 to instead use Axis 1.2-RC3. I have existing code which uses the
JAX-RPC generated API so I was hoping that the JAX-RPC binding 'standard' would
make this fairly easy i.e I could regenerate and compile against the same
interface but with a different underlying implementation.
However, I am finding that 'xsd:unsignedByte' is being bound to
'org.apache.axis.types.UnsignedByte' as opposed to 'short'. This then leads to
the arrays of this type also being unusable.
I notice that JAXB defaults 'xsd:unsignedByte' to be mapped to 'short'. Is it
possible to get Axis to do the same? Is this a bug in Axis or a
misunderstanding of a spec, or just a decision left open in a spec? Can I
override Axis's choice of what to map to?
[ ... ]
FYO, an example of the input WSDL is:
<complexType name="Array4OfunsignedByte">
<complexContent>
<restriction base="SOAP-ENC:Array">
<attribute ref="SOAP-ENC:arrayType" WSDL:arrayType="xsd:unsignedByte[]"/>
</restriction>
</complexContent>
</complexType>
This is using rpc/encoded btw, if that matters.
"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
