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, 25 Mar 2004 21:27:58 GMT
The following comment has been added to this issue:

     Author: Mike Perham
    Created: Thu, 25 Mar 2004 1:27 PM
Sorry but we're using now.  Any code or memory of the problem is
long gone...  Feel free to close this issue.
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, 25 Mar 2004 1:27 PM
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