axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1034) WSDL2Java generates incorrect attachment handling for client stub
Date Thu, 01 Apr 2004 16:33:48 GMT
The following comment has been added to this issue:

     Author: Lisa Preston
    Created: Thu, 1 Apr 2004 8:31 AM
I believe I have seen a similar issue... It seems that when an operation that returns a SOAP
attachment is called, the attachment result is interpreted just fine.  The problem is on the
next call, because the Stub object is saving the attachments as a part of its object.  When
a subsequent call is made to the webservice, the attachments are attached to the request because
the stub did not remove the attachments after they were received and processed for the previous
call.  This causes the request to fail.

My temporary solution for this was to add clearAttachments() at the beginning of each generated
operation call in the Stub, but I'm sure there is a better solution.  I modified org/apache/axis/wsdl/toJava/
to accomplish this.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1034
    Summary: WSDL2Java generates incorrect attachment handling for client stub
       Type: Bug

     Status: Open

    Project: Axis
             WSDL processing
             current (nightly)

   Assignee: Axis Developers Mailing List
   Reporter: Mike Perham

    Created: Wed, 27 Aug 2003 5:14 PM
    Updated: Thu, 1 Apr 2004 8:31 AM
Environment: Operating System: Other
Platform: Other

I'm using a doc/lit service and I bind parts of a response message as
attachments in my WSDL.  They are sent back to the client correctly and do wind
up in the attachments vector in the client Stub (i.e. extractAttachments(_call)
works fine) but the generated binding stub code tries to pull the part data out
of the output instead, as this WSDL2Java generated code snippet shows:

    pic.value = (javax.activation.DataHandler) _output.get(new

In other words, I don't believe the WSDL2Java code generator is taking into
account whether a part is an attachment or not and creating the cooresponding
code - it is just assuming it is a part in the body.  Service WSDL is attached.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message