On 5/25/05, Gentry, Michael (Contractor) <michael_gentr..anniemae.com> wrote:
> Well, I've been suspecting serialization. If I read the rows in and do
> an immediate commitChanges() in the same Tapestry request/response loop,
> nothing gets sent to the database (no changes). However, in the next
> request/response loop, it thinks they are modified (interestingly, only
> the objects hanging off a relationship, not the primary object).
>
If you convert all the relationships on the object back to fault
before the end of the request, does that help? If so, it might be
something funky in the way it deserializes the relationships.
This archive was generated by hypermail 2.0.0 : Wed May 25 2005 - 14:47:51 EDT