I guess you are setting the object references null in a managed instance
in a transactional method? Can you detach the instance before modifying
it? In the mean while, let me think if if there is an alternative way to
handle this.
Thanks,
Sahoo
glassfish_at_javadesktop.org wrote:
> I am also getting the same error - A cycle is detected in the object graph. This will cause infinitely deep XML whenever there is a circular reference.
>
> I followed Sahoo's advice by making object reference to null. Now I am getting an exception - Cannot update the record.
>
> Looks like when i am making the object reference null it is synchronizing the inmemory object with database and hence it is updating the database and kicks out with exception - cannot update - value cannot be null.
>
> How can i prevent it from updating the database or rather stop synchronizing the inmemory object with datasbe for this.
> [Message sent by forum member 'ad1900' (ad1900)]
>
> http://forums.java.net/jive/thread.jspa?messageID=240546
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>