...
[15:25:52 CDT(-0500)] <EricDalquist> like a PersistentList?
[15:27:59 CDT(-0500)] <athena> hm, i'll look
[15:28:26 CDT(-0500)] <athena> but i noticed that the fragment definiton has a different @blahblah in the name in the debugger
[15:37:01 CDT(-0500)] <EricDalquist> hrm
[15:37:08 CDT(-0500)] <EricDalquist> that should be the object's identity hash code
[15:37:10 CDT(-0500)] <EricDalquist> so if that changes
[15:37:13 CDT(-0500)] <EricDalquist> it is a different object
[15:42:54 CDT(-0500)] <athena> yeah
[15:43:08 CDT(-0500)] <athena> but maybe spring web flow is copying it when it saves it to the scope?
[15:43:26 CDT(-0500)] <EricDalquist> it would just grab a reference to it
[15:43:35 CDT(-0500)] <EricDalquist> the thing that scares me with those objects is they have behavior
[15:43:49 CDT(-0500)] <EricDalquist> is it the root evaluator where the id changes
[15:43:52 CDT(-0500)] <EricDalquist> or the list inside it
[15:44:03 CDT(-0500)] <athena> root
[15:44:16 CDT(-0500)] <EricDalquist> and both IDs are "new" on every request?
[15:44:21 CDT(-0500)] <athena> hmmm.
[15:44:29 CDT(-0500)] <athena> well, they're different between the dao response and what the JSP sees
[15:44:33 CDT(-0500)] <athena> haven't checked how they change over time
[15:44:43 CDT(-0500)] <athena> maybe really the best thing to do here is to have a helper that returns a custom object
[15:44:49 CDT(-0500)] <EricDalquist> just wondering if webflow has something in like session scope
[15:44:50 CDT(-0500)] <EricDalquist> yeah
[15:44:58 CDT(-0500)] <EricDalquist> that would probably be faster
[15:45:01 CDT(-0500)] <athena> that way we can protect any sensitive weirdness in that class too
[15:45:11 CDT(-0500)] <EricDalquist> yup
[15:45:18 CDT(-0500)] <athena> just expose some read-only data and let it be cleaner 
[16:54:46 CDT(-0500)] <EricDalquist> I really hate dates and times
[17:20:14 CDT(-0500)] <athena> no kidding.
[17:20:23 CDT(-0500)] <athena> amazing how painful that stuff can be
[17:20:33 CDT(-0500)] <EricDalquist> though this appears to be a bug in our jodatime -> hibernate binding library
[17:20:39 CDT(-0500)] <EricDalquist> the code is for storing local dates
[17:20:48 CDT(-0500)] <EricDalquist> and since SQL doesn't understand TZs
[17:21:05 CDT(-0500)] <EricDalquist> it does LocalDate -> Java Date in UTC
[17:21:11 CDT(-0500)] <EricDalquist> but on the way back out that TZ coversion breaks
[17:21:19 CDT(-0500)] <EricDalquist> so 2012-09-15 becomes 2012-09-14 when storing
[17:21:33 CDT(-0500)] <EricDalquist> but 2012-09-14 doesn't go back to 2012-09-15 when reading