Hi jvroom -
Thanks for your response. I've been trying everything from
sending message back through to the HibernateAssembler and also
just trying it through an RPC call. The same behavior is present. I
have, however, found a work around for it.....
The Organization java object had the locationSet as a
Set/HashSet declared for the set. I did this in order to use the
HIbernate set notation, instead of having to use an indexed List.
However, when I changed the Java object to a List, then it worked.
It appears as though, for some reason, serialization does not work
when declaring a Set. Not sure why since the Flex documentation
explicitly allows a Set/HashSet on the java side.
Any thoughts about that? Anyway, that was the solution that I
found. Hibernate does act a little strangely though given the way
the Hibernate Assembler compares the changes. For example, even
though I get the entire graph on the client, if I delete one of the
locations in the list, the server will only NULL out the foreign
key, instead of deleting the row. In my unit test on the server
going straight to Hibernate, it deletes the row. So, what I need to
do on the client is get the organizations and get the locations
seperately. When I delete from the location list, and then commit,
it works fine.
I'll do some more playing around with it, but I would assume
that if I delete a bean in a set that it would reflect the same
change through hibernate.
Thanks,
Tom