tag:blogger.com,1999:blog-2808112929591985886.post442150369486280505..comments2023-07-28T04:34:25.848-05:00Comments on On TopLink: Using TopLink projects through JPAShaun Smithhttp://www.blogger.com/profile/03444889032778621661noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2808112929591985886.post-31626610536147100252007-04-18T17:19:00.000-05:002007-04-18T17:19:00.000-05:00OK, that helps me a lot with my planning. Thanks a...OK, that helps me a lot with my planning. Thanks again for saving us from what would have been a lot of fruitless prototyping!Bruno Felacohttps://www.blogger.com/profile/15688366084271243524noreply@blogger.comtag:blogger.com,1999:blog-2808112929591985886.post-22834130655838514212007-04-18T14:45:00.000-05:002007-04-18T14:45:00.000-05:00Hi Bruno, The code in TLE is a fork of the Oracle ...Hi Bruno, <BR/><BR/>The code in TLE is a fork of the Oracle TopLink code base tuned to implement the JPA spec so the classes in oracle.toplink.essentials.** are substantially--I didn't say 'essentially' ;-)-- the same as the corresponding classes in oracle.toplink.**. Changes were only made for the sake of the spec.<BR/><BR/>That being said--you're right, TopLink Essentials is missing a few advanced features available in Oracle TopLink, like cache coordination, so what I suggested is really only a good idea if you're doing pretty vanilla Oracle TopLink.<BR/><BR/>I think what you really should do is wait until the Oracle TopLink 11 preview is available around JavaOne (2nd week of May '07) to start migrating your TopLink app to JPA. This will allow you to use all the features in Oracle TopLink and make use of the Java Persistence programmer API.<BR/><BR/>--ShaunShaun Smithhttps://www.blogger.com/profile/03444889032778621661noreply@blogger.comtag:blogger.com,1999:blog-2808112929591985886.post-51289832711873513252007-04-18T14:15:00.000-05:002007-04-18T14:15:00.000-05:00Hi Shaun,Thanks so much for responing, and for pos...Hi Shaun,<BR/><BR/>Thanks so much for responing, and for posting this as a toplevel entry to get the word out to others. I was under the false impression that TopLink 10.1.3.1 was the JPA spec compliant release of TopLink and that it would be possible to use the JPA interfaces with TopLink.<BR/><BR/>I would consider switching to TopLink essentials and refactoring my code, but what guarantees do I have about the behavior? Are the classes in oracle.toplink.essentials.** exactly the same as those in oracle.toplink.**? Please don't say that they are "essentially" the same. :-) We make use of an awful lot of TopLink features including:<BR/>- clustering (still using the legacy CacheSynchronizationManager classes)<BR/>- very specific event handlers<BR/>- extensions to the Expression API<BR/>- extensions to a Platform class<BR/>- custom sequence generator<BR/>Are all these features supported in TopLink Essentials? My understanding was - NO. <BR/><BR/>Thanks<BR/>- BrunoBruno Felacohttps://www.blogger.com/profile/15688366084271243524noreply@blogger.com