axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jongjin Choi (JIRA)" <>
Subject [jira] Commented: (AXIS-2098) xsi:type added to derived simple types
Date Mon, 01 Aug 2005 16:54:36 GMT
    [ ] 

Jongjin Choi commented on AXIS-2098:

Dims and all.

I fixed the AXIS-2098 and AXIS-2103. 
I'd like you to review the patches before I commit. 
All-tests passed with the latest cvs.
The patch and test-case will be attached.

This is the change log.
Fix for AXIS-2098, 2103
- WSDDTypeMapping : Register exact type mapping for primtive type at the server-side. (primitive
type instead of primitive wrapper)
- JavaStubWriter : Register exact type mapping for schema derived types in the client side.
- Serialization : Pass the java class to the SerializationContext to determine actual java
type for serialization
- TypeMappingImpl : find serializer using xml type. (for schema derived types)
- JavaBeanHelperWriter : write exact type qname for schema ref'ed element. (AXIS-2103)

> xsi:type added to derived simple types
> --------------------------------------
>          Key: AXIS-2098
>          URL:
>      Project: Apache Axis
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.2.1
>     Reporter: David Kocher
>     Priority: Blocker
>  Attachments: helloworld.tar.gz, src_2005_08_01.patch
> Given a simple type such as
>     <xs:simpleType name="LogicType">
>         <xs:restriction base="xs:boolean">
>             <xs:pattern value="true"/>
>             <xs:pattern value="false"/>
>         </xs:restriction>
>     </xs:simpleType>
> Axis will serialize this as 
>                <Logic xsi:type="xsd:boolean">true</Logic>
> which won't validate because
> Type 'xsd:boolean' is not validly derived from the type definition, 'LogicType', of element
> This is only the case in the request message; the response message of the same type is
sent correctly.
> See the attached sample project.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message