axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Husted (JIRA)" <>
Subject [jira] Commented: (AXIS-1872) Allow for streaming of DIME attachments
Date Wed, 13 Jul 2005 21:33:13 GMT
    [ ] 

Brian Husted commented on AXIS-1872:

Unfortunutely, I have run into some difficulties regarding streaming attachments using DIME
with the Axis patch. It works fine when submitting attachments from the Axis server to the
Axis client. However, when I attempt to submit an attachment from the Axis client to the Axis
server running the Web Services it has problems. I am using Axis version 1.2.1, running the
client in Java JDK 1.4.2_05 and server running Weblogic 7 on JDK 1.3.1. 

Below is the server side stack trace: End of physical stream detected when 11 more bytes expected. 
        at org.apache.axis.attachments.DimeDelimitedInputStream._read(



        at org.apache.axis.attachments.ManagedMemoryDataSource.<init>(

        at org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(

        at org.apache.axis.attachments.MultiPartDimeInputStream.readAll(

        at org.apache.axis.attachments.MultiPartDimeInputStream.getAttachments(

        at org.apache.axis.attachments.AttachmentsImpl.mergeinAttachments(

        at org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(

> Allow for streaming of DIME attachments
> ---------------------------------------
>          Key: AXIS-1872
>          URL:
>      Project: Apache Axis
>         Type: New Feature
>   Components: SAAJ
>     Versions: 1.2RC3
>     Reporter: Marc Dumontier
>  Attachments: DimeBodyPart.diff,, dime-patch.txt
> The current system does not allow for streaming DIME attachments because the size of
the data is requested from the DataHandler first (this usually means reading the entire stream,
then resetting it), and then a single DIME record is created.
> The DIME specification allows for the use of record chunking so that dynamic content
generators can stream back data with a small memory footprint.

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