Thanks, Shailesh. Glad to hear about your successes.
Originally posted by peter coster:
Mike,
I used auto schema creation - this caused warnings for sequences that already existed, hibernate does it different.
Okay. I guess that's just a matter of taste and what you are used to. Some people like to be told if an object is being reused instead of being created and initialized.
the combination of OneToMany and a joinColumn was not allowed, I tought this was legal ? Haven't tried it with hibernate. This kind of uni-directional foreign key OneToMany is not legal in JPA 1.0, and we tried hard to discourage people from supporting such a thing. It is viewed as being a bad mapping strategy and contrary to good object-relational design. Unfortunately we will probably end up including support for it in JPA 2.0, though, but I don't like it.
[/QB]
This experience and comments from colleagues who had started projects with Toplink but switched to Hibernate because of problems (don't know what specifically), made me switch. More to have a quick result then for anything else really.[/QB]
I can't speak to third-hand general comments, but I would be surprised if there was any substance to it. In my experience (I have talked to a lot of people at a lot of conferences and user groups) and I find that all of the major providers have done a pretty good job on their JPA impls. The bug count does not vary much in quantity between them (I can actually list a couple of gotcha bugs from each vendor that regularly get people ;-). They are just different, and in the end it comes down to taste, and which features people feel more comfortable with. If someone feels more comfortable with one then they can switch, and if switching was fairly easy to do then we did our spec job well, I think.