| JPA2.1 [message #662069] |
Tue, 29 March 2011 07:08 |
 Tom Eugelink
Messages: 817
Registered: July 2009 |
Senior Member |
|
|
Dear Oracle people,
Just read the specs for JPA2.1 and found one thing that I really miss in JPA absent: events in which changes to the BM are formally allowed. In the last few years I've posted myself and have seen many posts by other in this mailinglist on the fact that the before-persist, before-merge, etc events are only partial usable. The main issue is that if you modify entities in these events the changes may or may not be included in the database. In order to write good encapsulated business models these types of events are a necessity; at the moment I have pieces of such code in my UI (and have to repeat them in my web UI and SOAP interface). I believe the pass that generates the events and the pass that does the actual persisting should be separated. And because of changes being made during the event-pass, multiple event-passes may be required.
Do you know if I can just bring this concern to Linda DeMichiel's attention by emailing her? Or is there a more formal way to address the JPA 2.1 committee?
Tom
|
|
|
Powered by
FUDForum. Page generated in 0.02775 seconds
] 
Search
Help
Register
Login
Home
