[ 
https://issues.apache.org/jira/browse/AXIS2-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862092#action_12862092
 ] 

William Headrick edited comment on AXIS2-4615 at 4/29/10 12:43 AM:
-------------------------------------------------------------------

RE: Attached Files

Example POJO Service which should illustrate the problem.  "doTest1" should 
fail (byte array won't be returned).  "doTest2" should succeed (byte array WILL 
be returned).

When code is fixed, both should return the byte array.

      was (Author: headw01):
    Example POJO Service which should illustrate the problem.  "doTest1" should 
fail (byte array won't be returned).  "doTest2" should succeed (byte array WILL 
be returned).

When code is fixed, both should return the byte array.
  
> BeanUtil.deserialize byte array (still) blindly attempts to decode the first 
> element in the doc
> -----------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-4615
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4615
>             Project: Axis2
>          Issue Type: Sub-task
>          Components: adb, databinding, om
>    Affects Versions: 1.5.1
>            Reporter: William Headrick
>            Priority: Blocker
>         Attachments: TestMessage1.java, TestMessage2.java, TestService.java
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> This bug still exists in the 1.5.1 source code.
> If there is a byte array defined, the name of the element isn't used to look 
> up the element from the "beanElement".  The OMElementImpl#getFirstElement() 
> method is used.  There is a good chance that the byte array won't be first.
> These are the original issues that I can find:
> AXIS2-3538,AXIS2-3765
> Both 3538 and 3765 have proposed solutions.

-- 
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to