I saw this issue when I first converted some code over to ValueObject. The problem was with value objects that are related bi-directionally. You baiscally have a circular reference. If you enable reentrant behavior, you won't get the exception, but you will blow your stack with an endless loop of method calls.
The way I got around it was to setup my value objects so that each one as two flavors: a full one and a 'relation' one. The relation versions did not include the CMR method. So, the full version calls the relation version (which doesn't in turn call back into the full version). Does that make any sense? Hopefully. :) Maybe somebody else has a better way, but that worked for me. Gary. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822917#3822917 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822917 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
