[ http://issues.apache.org/jira/browse/AXIS-1433?page=comments#action_12312801 ]
Davanum Srinivas commented on AXIS-1433: ---------------------------------------- Lisa, Is there a problem adding clearAttachments in your code? you do have access to the stub. thanks, dims > Problem about Stub adds the Attachment of response to the next request > ---------------------------------------------------------------------- > > Key: AXIS-1433 > URL: http://issues.apache.org/jira/browse/AXIS-1433 > Project: Axis > Type: Bug > Versions: 1.2 Beta, 1.0, 1.2 Alpha, 1.1RC1, 1.1rc2, 1.1, 1.1beta > Environment: OS:Win2k > JRE: J2SE1.4.2_03 > Axis 1.1, 1.2Beta > Reporter: Takaya Matsuishi > Priority: Critical > > Hi, all > Our software(Client for Web Service) calls Web Service which returns > MIME Attachment with Stub generated by WSDL2Java. > While the client had held DataHandler acquired from the response is > called, if the client calls web service using same Stub instance, client > CAN NOT access to the InputStream in DataHandler. > (InputStream throws IOException of "resouceDeleted.") > I investigated the source, and confirmed InputStream becomes invalid in the > following flow. > 1. > At this line of each Stub methods, > "extractAttachements(_call);" > (after "Object _resp = call.invoke(xx);"), > Stub holds attachments in response. > 2. > Stub adds to the request in next "setAttachments(_call);". > 3. > When HttpSender outputs the requests to the stream, Massage calls > "AttachmentsImpl#writeContentToStream()". > 4. > AttatchementImpl calls ManagedMemoryDataSource#delete(), then > InputStream becomes invalid. > I also saw these bug reports. > http://marc.theaimsgroup.com/?l=axis-dev&m=104154097030432&w=2 > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13769 > However, I cannot understand why Stub adds the Attachment of response to > the next request, and I have no idea how I should avoid. > Please advise me. > Thank you. > Best regards, > Takaya Matsuishi -- 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
