axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajith Harshana Ranabahu (JIRA)" <>
Subject [jira] Resolved: (AXIS2-442) Better support for base64Binary/MTOM
Date Thu, 20 Apr 2006 10:35:07 GMT
     [ ]
Ajith Harshana Ranabahu resolved AXIS2-442:

    Resolution: Fixed

The ADB codegen has been modified to always generate a data handler for base64binary content.
The converters has also been modified do the conversion properly.
The parsers (ADBPullParsers) has been added two new properties "Axiom.DataHandler" and "Axiom.IsBinary".
The users can call getProperty with Axiom.DataHandler key and get the Datahandler directly.

> Better support for base64Binary/MTOM
> ------------------------------------
>          Key: AXIS2-442
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: databinding
>     Reporter: Davanum Srinivas
>     Assignee: Ajith Harshana Ranabahu

> If we have a complexType as follows:
> 	<xs:complexType name="XRayRecord">
> 		<xs:sequence>
> 			<xs:element name="FirstName" type="xs:string" nillable="true" minOccurs="0"/>
> 			<xs:element name="LastName" type="xs:string" nillable="true" minOccurs="0"/>
> 			<xs:element name="TimeStamp" type="xs:dateTime" minOccurs="0"/>
> 			<xs:element name="XRay" type="xs:base64Binary" nillable="true" minOccurs="0"/>
> 		</xs:sequence>
> 	</xs:complexType>
> The generated code uses byte[] for XRay:
>             /**
>             * field for XRay
>             */
>             protected byte[] localXRay ;
> Can we please add an optional switch to generate DataHandler's instead of byte arrays?
Also support will have to be added to avoid converting this into a string and directly using
the data handler for MTOM/XOP.
> thanks,
> dims

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