commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Halsey (JIRA)" <j...@apache.org>
Subject [jira] Updated: (BETWIXT-61) String Array in bean causes String element after to not be set
Date Fri, 16 Nov 2007 20:17:42 GMT

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

Stephen Halsey updated BETWIXT-61:
----------------------------------

    Summary: String Array in bean causes String element after to not be set  (was: Array in
bean causes element after to not be set)

> String Array in bean causes String element after to not be set
> --------------------------------------------------------------
>
>                 Key: BETWIXT-61
>                 URL: https://issues.apache.org/jira/browse/BETWIXT-61
>             Project: Commons Betwixt
>          Issue Type: Bug
>         Environment: Windows XP, Suns Java 1.5.0_07, Betwixt Version 0.8 Source.
>            Reporter: Stephen Halsey
>         Attachments: TestBetwixtArrayBugUnit.java, WithBugBean.java, WithoutBugBean.java
>
>
> Hi,
> I am having a problem with a class that has arrays in it and writing and reading them
using betwixt.  I have tracked down the problem and created a simple unit test with the 3
classes attached that demonstate this.  If you create a new org.apache.commons.betwixt.arraybug
package in your src/test folder of you betwixt source code and put these classes in you should
be able to run the tests.
> I have put an explanation of what the test does at the top of the TestBetwixtArrayBugUnit
class.
> I'm sorry if I've just used the wrong settings or something, but I based it on the code
from the examples page at http://commons.apache.org/betwixt/guide/examples.html for doing
a round trip on a simple bean.
> I'm not sure, but there is a chance this could be related to the error someone reported
at:-
> http://markmail.org/message/ofm3yp7gf7auhfcp
> because I may have seen the EmptyStackException under certain circumstances too whilst
developing this test, but in this test you will see no exception is generated, the value just
comes out null for the xxx parameter because it is alphabetically after the array parameter,
which is actually more worrying as its a lot harder to spot.
> If you would like me to I can do a bit more work and get sample debug output to try and
work out why it is doing what it is doing?
> thanks
> Steve

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


Mime
View raw message