users@glassfish.java.net

Re: JPA cacade remove operation: Spec vs. TLE implementation

From: <glassfish_at_javadesktop.org>
Date: Mon, 13 Aug 2007 20:41:24 PDT

>The fix will also be available in the nightly and promoted builds of both GlassFish<br/>
I always use promoted builds so it's ok to have fix this way.<br/>
Thank you very much for keeping us posted.<br/>
I think that would be very useful for many developers to have project that can demonstrate how to implement all kind of tricks related to persistence provider.<br/>
Let me describe how I see that in details:<br/>
1) netbeans 6 based<br/>
2) directly available from glassfish site <br/>
3) demonstrate how to use and when to use all functionality that provide "toplink essential"<br/>
4) the toplink team constantly review the project and make necessary improvements that probably in many cases will be triggered by improvements in persistence provider itself.<br/>
5) project should be semantic oriented. To reach this goal it necessary to have xml based file that will be able to describe all semantic relations that exist between entities.<br/> Keep in mind that entity mapping descriptor (aka orm.xml) doesn't provide all information that need to know to implement application.<br/>
Having this file will provide the possibility to generate whole database oriented application.<br/> As additional benefit we don't need to have much documentation that describe entities and relationships between them.<br/> I called this file semantic because it will use semantic concepts like parent, child, owner and etc.<br/>
<br/>
If the team interesting in this kind of project I'm ready to start preparing some material in this direction.<br/>
<br/>
Sincerely,<br/>
Vladimir<br/>
[Message sent by forum member 'vladperl' (vladperl)]

http://forums.java.net/jive/thread.jspa?messageID=230744