Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <6850248.1170618185729.JavaMail.jira@brutus>
Date: Sun, 4 Feb 2007 11:43:05 -0800 (PST)
From: "Rich Scheuerle (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Updated: (AXIS2-2092) Byte array attachments type
In-Reply-To: <25972905.1170456725503.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AXIS2-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rich Scheuerle updated AXIS2-2092:
----------------------------------

    Attachment: patch.txt

I am attaching a modified patch.

The modified patch contains the following:
   1) Added more debug information to both the JAXBAttachmentMarshaller and JAXBAttachmentUnmarshaller.
   2) Added code to implement JAXBAttachmentUnmarshaller.getAttachmentAsBytes() method.
   3) Changed the wsdl for the new test to load the local copy of xmlmime.xsd.  We had problems in 
       the past accessing this schema remotely.
   4) The new test webservices was swallowing exceptions.  I changed the code to throw WebServiceExceptions.
   5)  I added an additional test in the client suite to intentionally not send the message as MTOM optimized.  An MTOM unoptimized client and MTOM optimized server will force the code through some different paths.
   6) I added a second attachment to the ImageDepot.  The second attachement is a custom attachment using the Base64Binary mechanism.  Base64Binary allows the user to get the contentType and byte[] array directly.  I added this second kind of attachment to force some new flows.   It also allowed me to more easily check the resulting values.

I thought that (6) in combination with (5) would cause JAXB to use the unmarshaller code (2).  However it appears that the current version of JAXB 2.0 always invokes getAttachmentAsDataHandler.  Even so, I think the new addtions will help us out.  It would be nice to determine how/whether we can trigger JAXB to use (2).


> Byte array attachments type
> ---------------------------
>
>                 Key: AXIS2-2092
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2092
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: jaxws
>         Environment: Win XP
>            Reporter: Samuel Isokpunwu
>         Assigned To: Rich Scheuerle
>         Attachments: d417707patch.txt, patch.txt
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org