Well said. In addition, if you will need production support down the
road, the built-in JPA implementation is supported by Sun.
Sent from my iPhone
On Oct 24, 2008, at 5:52 AM, Ryan de Laplante <ryan_at_ijws.com> wrote:
> I think most GlassFish users choose to use the built in JPA
> implementation so that they can just use it without having to add
> dependencies and configuration to their project. I've only ever
> replaced the default implementation (TopLink Essentials) with
> Hibernate JPA implementation when needing features not offered by
> JPA spec or TopLink Essentials such as criteria API. That is
> coming in JPA 2.0.
>
> TopLink Essentials is a striped down version of Oracle's TopLink
> product. Recently Oracle has donated the full TopLink product to the
> Eclipse Foundation and renamed it to Eclipse Link. Eclipse Link is
> the reference implementation of JPA 2.0 and will be built into
> GlassFish V3. I'm pretty sure it can do everything Hibernate does,
> and the original Oracle TopLink was Gavin's source of inspiration
> when creating Hibernate.
>
>
> Ryan
>
>
>
> Ronaldo Rigoni ... wrote:
>> Hi all,
>> What is the JPA implementation that users has most used with
>> GlassFish?
>> Hibernate or TopLink?
>> What's the benefits to use Hibernate in alternative to the default
>> TopLink implementation?
>>
>> Regards,
>> Ronaldo Rigoni
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>