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 "Deepak Bhole (JIRA)" <ji...@apache.org> on 2006/04/19 05:02:18 UTC

[jira] Updated: (AXIS2-588) Support for streaming attachments without having to buffer first

     [ http://issues.apache.org/jira/browse/AXIS2-588?page=all ]

Deepak Bhole updated AXIS2-588:
-------------------------------

    Attachment: axiom-attachmentstreaming.patch
                axiom-attachmentstreaming-new-files.tar.gz
                axiom-attachmentstreaming-sample-service.tar.gz

Attached patch+files add streaming support for axis2. This enables users to access attachment (excluding base SOAP stream) streams directly, thus causing them to be read only once, and only when needed. A lot of the code comes from the axis1 tree, modified for use in axis2 (with any found bugs fixed).

Part based access and stream based access are mutually exclusive, and only one or the other can be used.

Also attached are AxisTest* service and client files in the axiom-attachmentstreaming-sample-service.tar.gz archive. mtomSample() shows how to access items by part, while mtomSample2() shows how to use stream based access. 

The patch also makes header handling more generic to provide a get/set header for PartOnFile items. 

Furthermore, there are a range of new test cases to test all the changes made by this patch.

> Support for streaming attachments without having to buffer first
> ----------------------------------------------------------------
>
>          Key: AXIS2-588
>          URL: http://issues.apache.org/jira/browse/AXIS2-588
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement

>   Components: om
>  Environment: All
>     Reporter: Deepak Bhole
>     Assignee: Deepak Bhole
>     Priority: Minor
>  Attachments: axiom-attachmentstreaming-new-files.tar.gz, axiom-attachmentstreaming-sample-service.tar.gz, axiom-attachmentstreaming.patch
>
> Like axis1, axis2 should allow users to access attachment streams directly, thus preventing the need to buffer attachments to disk/memory first. Since we are dealing with streams, access method should be mutually exclusive, a choice between Part based access, or direct stream access.

-- 
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