The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
thanks for your response. my requirement is not complex. I can go for simple JDBC / EJB calls. I thought of implementing the open source framework in my current project which gives good performance, in turn helps me to learn another technology.
Pls let me know your suggestions to chose the best persistence framework opensource.
Moving this to the Object Relational Mapping forum.
Well, I changed my mind since not all the frameworks you mentioned are all about persistence. Spring and EJB I wouldn't classify as persistence frameworks. Yes, EJB has Container and Bean Managed Entity beans, but that is a specification, not an actual framework, per say. The Spring is more of like an Application Container Framework, that is more involved than persistence. And with Spring and EJB, most people will still use a seperate persistence framework.
OK, so I will move it anyway.
Mark [ July 13, 2005: Message edited by: Mark Spritzler ]
Learning a new technology is not a great criteria for choosing a Java persistence strategy for an application (unless that's the purpose of the project). It's good that the initial responses have been about your technical requirements - that's certainly where you should start.
Your list of options includes a diverse range of items related to Java persistence. Can I suggest that you read "Choosing a Java Persistence Strategy" to get started:
Since this seems to just be a place to shill your product let me add my shilling to the mix.
Oracle TopLink is the most widely used commercial O/R mapping product on the market so if you have any serious requirements I recommend you download it and benchmark it against any other product that you are considering.
There are some white papers available there as well that you might want to put on your homework stack.
If you are just playing around then any old O/R mapper will do. Whatever you do, if you predict that your app will EVER grow to use more than just a handful of classes then please don't use JDBC. Use an O/R mapper, any one. I have seen too many companies get lured into rolling their own persistence for just a few objects, and it grows, and grows, until they end up with their own franken-mapping layer and wish they had done a little more planning up front.