Charlouze, I worked on a world class backbone (meaning multi flavored request broker rmi/ejb/corba hostname:port ) for integrating supply chains bidders amidst a slew of Javascript apps...
In our applications... we performed transactions... responsibly. To say I am uncomfortable with tynamo's demarcation's usage of @CommitAfter... which appears to be everywhere and my current app is calling commit twice on one SAVE then rollback because hibernate does not support nested transactions would be an understatement. Its nice to see tapestry-security-0.6.1 released... (this says someone cares but the whole framework has been neglected for years) the build tree remains in shambles and the main core model wont work on checkout. Kuddos to the guy who can checkout one of those modules...roll the dice and use it commercially. I have yet to get it working and trying to fix my own checked out version permanently. Then I will introduce ANGULAR and piece by peace strip off obsolete unneeded pieces. Maybe I will be left with angular/rest/hibernate and that will be fine with me. To answer your question... a commercial solution is to implement a reference count. Decoupled to or within the @CommitAfter annotation. When the reference count == 0 then commit. Thats what we did for our world class backbone with which the 2002 honda accord was manufactured and built on... and its being used today its renamed eNovia...formerly eMatrix. I am not a happy software developer. And I got good reason to be. I come from the XWindows days when the MIT License was what governed the quality of open source code. And it looks like its made its way back finally. Best regards and thanks... KEN
