You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2006/02/10 04:45:56 UTC

[jira] Created: (AXIS2-442) Better support for base64Binary/MTOM

Better support for base64Binary/MTOM 
-------------------------------------

         Key: AXIS2-442
         URL: http://issues.apache.org/jira/browse/AXIS2-442
     Project: Apache Axis 2.0 (Axis2)
        Type: Bug
  Components: databinding  
    Reporter: Davanum Srinivas
 Assigned to: 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Resolved: (AXIS2-442) Better support for base64Binary/MTOM

Posted by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-442?page=all ]
     
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: http://issues.apache.org/jira/browse/AXIS2-442
>      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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira