TomEE 7 and JPA 2.1

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

TomEE 7 and JPA 2.1

Ivan St. Ivanov
Hi folks,

We will be running a series of workshops in Bulgarian JUG to develop our
new website. We'll be using Java EE 7 and TomEE 7. I know it is still
milestone release and not fully EE 7 compatible. But we decided to take the
"risk".

In the app we are using the new schema generation annotations coming with
JPA 2.1, but they did not work. When I turned back to the old,
implementation specific ones, it worked.

Did I get it wrong that none of the WebProfile or PLUME distributions
supports the JPA 2.1 spec? In the former I find OpenJPA 2.4.0, while in the
latter I see EclipseLink 2.4.2.

Do you plan to provide JPA 2.1 support at least in the PLUME distro?

Thanks,
Ivan

P.S. Roberto sent me a couple of weeks ago instructions how to integrate
Hibernate JPA, but I would like to keep the configuration steps as few as
possible as there will be a lot of people that will have to do them during
the workshop
Reply | Threaded
Open this post in threaded view
|

Re: TomEE 7 and JPA 2.1

Mitia Alexandrov
OpenJpa 2.1 is not ready. Use EclipseLink for JPA 2.1, its shipped with
latest Plume :)

вт, 26 апр. 2016, 2:08 Ivan St. Ivanov <[hidden email]>:

> Hi folks,
>
> We will be running a series of workshops in Bulgarian JUG to develop our
> new website. We'll be using Java EE 7 and TomEE 7. I know it is still
> milestone release and not fully EE 7 compatible. But we decided to take the
> "risk".
>
> In the app we are using the new schema generation annotations coming with
> JPA 2.1, but they did not work. When I turned back to the old,
> implementation specific ones, it worked.
>
> Did I get it wrong that none of the WebProfile or PLUME distributions
> supports the JPA 2.1 spec? In the former I find OpenJPA 2.4.0, while in the
> latter I see EclipseLink 2.4.2.
>
> Do you plan to provide JPA 2.1 support at least in the PLUME distro?
>
> Thanks,
> Ivan
>
> P.S. Roberto sent me a couple of weeks ago instructions how to integrate
> Hibernate JPA, but I would like to keep the configuration steps as few as
> possible as there will be a lot of people that will have to do them during
> the workshop
>
Reply | Threaded
Open this post in threaded view
|

Re: TomEE 7 and JPA 2.1

asotobu
Hi Ivan what I would do will be droppng openjpa jars and add Hibernate
since it is the solution that IMHO most of the people use.

There is a doc in tomee website that explains it

Alex
El 26 abr. 2016 5:52 a. m., "Mitia Alexandrov" <[hidden email]>
escribió:

> OpenJpa 2.1 is not ready. Use EclipseLink for JPA 2.1, its shipped with
> latest Plume :)
>
> вт, 26 апр. 2016, 2:08 Ivan St. Ivanov <[hidden email]>:
>
> > Hi folks,
> >
> > We will be running a series of workshops in Bulgarian JUG to develop our
> > new website. We'll be using Java EE 7 and TomEE 7. I know it is still
> > milestone release and not fully EE 7 compatible. But we decided to take
> the
> > "risk".
> >
> > In the app we are using the new schema generation annotations coming with
> > JPA 2.1, but they did not work. When I turned back to the old,
> > implementation specific ones, it worked.
> >
> > Did I get it wrong that none of the WebProfile or PLUME distributions
> > supports the JPA 2.1 spec? In the former I find OpenJPA 2.4.0, while in
> the
> > latter I see EclipseLink 2.4.2.
> >
> > Do you plan to provide JPA 2.1 support at least in the PLUME distro?
> >
> > Thanks,
> > Ivan
> >
> > P.S. Roberto sent me a couple of weeks ago instructions how to integrate
> > Hibernate JPA, but I would like to keep the configuration steps as few as
> > possible as there will be a lot of people that will have to do them
> during
> > the workshop
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: TomEE 7 and JPA 2.1

Romain Manni-Bucau
Depending the dev workflow you will use, relying on maven plugins can be an
option which allows to customize plugins. They allow to add any jpa impl
pretty easily.
Le 26 avr. 2016 08:31, "Alex Soto" <[hidden email]> a écrit :

> Hi Ivan what I would do will be droppng openjpa jars and add Hibernate
> since it is the solution that IMHO most of the people use.
>
> There is a doc in tomee website that explains it
>
> Alex
> El 26 abr. 2016 5:52 a. m., "Mitia Alexandrov" <[hidden email]>
> escribió:
>
> > OpenJpa 2.1 is not ready. Use EclipseLink for JPA 2.1, its shipped with
> > latest Plume :)
> >
> > вт, 26 апр. 2016, 2:08 Ivan St. Ivanov <[hidden email]>:
> >
> > > Hi folks,
> > >
> > > We will be running a series of workshops in Bulgarian JUG to develop
> our
> > > new website. We'll be using Java EE 7 and TomEE 7. I know it is still
> > > milestone release and not fully EE 7 compatible. But we decided to take
> > the
> > > "risk".
> > >
> > > In the app we are using the new schema generation annotations coming
> with
> > > JPA 2.1, but they did not work. When I turned back to the old,
> > > implementation specific ones, it worked.
> > >
> > > Did I get it wrong that none of the WebProfile or PLUME distributions
> > > supports the JPA 2.1 spec? In the former I find OpenJPA 2.4.0, while in
> > the
> > > latter I see EclipseLink 2.4.2.
> > >
> > > Do you plan to provide JPA 2.1 support at least in the PLUME distro?
> > >
> > > Thanks,
> > > Ivan
> > >
> > > P.S. Roberto sent me a couple of weeks ago instructions how to
> integrate
> > > Hibernate JPA, but I would like to keep the configuration steps as few
> as
> > > possible as there will be a lot of people that will have to do them
> > during
> > > the workshop
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: TomEE 7 and JPA 2.1

Ivan St. Ivanov
Hi everybody,

Thanks for your answers!

*@Mitia:* as far as I saw, M3 contains EclipseLink 2.4.2 as well?

*@Alex:* I want to avoid that, as this is going to be a workshop and most
of the people will have to do that manually.

*@Romain:* I want to keep the pom as simple as possible.

Well, I guess we will go with the custom persistence.xml for now and once
you release TomEE 7 Final, we'll switch to the JPA 2.1 generic table
generation property. At the end, when we go productive, we won't need that
anyway.

Cheers,
Ivan

On Tue, Apr 26, 2016 at 9:33 AM, Romain Manni-Bucau <[hidden email]>
wrote:

> Depending the dev workflow you will use, relying on maven plugins can be an
> option which allows to customize plugins. They allow to add any jpa impl
> pretty easily.
> Le 26 avr. 2016 08:31, "Alex Soto" <[hidden email]> a écrit :
>
> > Hi Ivan what I would do will be droppng openjpa jars and add Hibernate
> > since it is the solution that IMHO most of the people use.
> >
> > There is a doc in tomee website that explains it
> >
> > Alex
> > El 26 abr. 2016 5:52 a. m., "Mitia Alexandrov" <
> [hidden email]>
> > escribió:
> >
> > > OpenJpa 2.1 is not ready. Use EclipseLink for JPA 2.1, its shipped with
> > > latest Plume :)
> > >
> > > вт, 26 апр. 2016, 2:08 Ivan St. Ivanov <[hidden email]>:
> > >
> > > > Hi folks,
> > > >
> > > > We will be running a series of workshops in Bulgarian JUG to develop
> > our
> > > > new website. We'll be using Java EE 7 and TomEE 7. I know it is still
> > > > milestone release and not fully EE 7 compatible. But we decided to
> take
> > > the
> > > > "risk".
> > > >
> > > > In the app we are using the new schema generation annotations coming
> > with
> > > > JPA 2.1, but they did not work. When I turned back to the old,
> > > > implementation specific ones, it worked.
> > > >
> > > > Did I get it wrong that none of the WebProfile or PLUME distributions
> > > > supports the JPA 2.1 spec? In the former I find OpenJPA 2.4.0, while
> in
> > > the
> > > > latter I see EclipseLink 2.4.2.
> > > >
> > > > Do you plan to provide JPA 2.1 support at least in the PLUME distro?
> > > >
> > > > Thanks,
> > > > Ivan
> > > >
> > > > P.S. Roberto sent me a couple of weeks ago instructions how to
> > integrate
> > > > Hibernate JPA, but I would like to keep the configuration steps as
> few
> > as
> > > > possible as there will be a lot of people that will have to do them
> > > during
> > > > the workshop
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

RE: TomEE 7 and JPA 2.1

Yann BLAZART
In reply to this post by asotobu
Hello.

Git clone the TomEE sources  then take a look how the TomEE distributions are built (plume by example).

You can do the same thing in your own project / pom, excluding all jpa artifacts then adding hibernate ones.

It's even simpler with TomEE embedded.

Regards.

-----Original Message-----
From: Alex Soto [mailto:[hidden email]]
Sent: mardi 26 avril 2016 08:31
To: [hidden email]
Subject: Re: TomEE 7 and JPA 2.1

Hi Ivan what I would do will be droppng openjpa jars and add Hibernate since it is the solution that IMHO most of the people use.

There is a doc in tomee website that explains it

Alex
El 26 abr. 2016 5:52 a. m., "Mitia Alexandrov" <[hidden email]>
escribió:

> OpenJpa 2.1 is not ready. Use EclipseLink for JPA 2.1, its shipped
> with latest Plume :)
>
> вт, 26 апр. 2016, 2:08 Ivan St. Ivanov <[hidden email]>:
>
> > Hi folks,
> >
> > We will be running a series of workshops in Bulgarian JUG to develop
> > our new website. We'll be using Java EE 7 and TomEE 7. I know it is
> > still milestone release and not fully EE 7 compatible. But we
> > decided to take
> the
> > "risk".
> >
> > In the app we are using the new schema generation annotations coming
> > with JPA 2.1, but they did not work. When I turned back to the old,
> > implementation specific ones, it worked.
> >
> > Did I get it wrong that none of the WebProfile or PLUME
> > distributions supports the JPA 2.1 spec? In the former I find
> > OpenJPA 2.4.0, while in
> the
> > latter I see EclipseLink 2.4.2.
> >
> > Do you plan to provide JPA 2.1 support at least in the PLUME distro?
> >
> > Thanks,
> > Ivan
> >
> > P.S. Roberto sent me a couple of weeks ago instructions how to
> > integrate Hibernate JPA, but I would like to keep the configuration
> > steps as few as possible as there will be a lot of people that will
> > have to do them
> during
> > the workshop
> >
>


This message and any attachments (the "message") is
intended solely for the intended addressees and is confidential.
If you receive this message in error,or are not the intended recipient(s),
please delete it and any copies from your systems and immediately notify
the sender. Any unauthorized view, use that does not comply with its purpose,
dissemination or disclosure, either whole or partial, is prohibited. Since the internet
cannot guarantee the integrity of this message which may not be reliable, BNP PARIBAS
(and its subsidiaries) shall not be liable for the message if modified, changed or falsified.
Do not print this message unless it is necessary,consider the environment.

----------------------------------------------------------------------------------------------------------------------------------

Ce message et toutes les pieces jointes (ci-apres le "message")
sont etablis a l'intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur ou s'il ne vous est pas destine,
merci de le detruire ainsi que toute copie de votre systeme et d'en avertir
immediatement l'expediteur. Toute lecture non autorisee, toute utilisation de
ce message qui n'est pas conforme a sa destination, toute diffusion ou toute
publication, totale ou partielle, est interdite. L'Internet ne permettant pas d'assurer
l'integrite de ce message electronique susceptible d'alteration, BNP Paribas
(et ses filiales) decline(nt) toute responsabilite au titre de ce message dans l'hypothese
ou il aurait ete modifie, deforme ou falsifie.
N'imprimez ce message que si necessaire, pensez a l'environnement.
Reply | Threaded
Open this post in threaded view
|

Re: TomEE 7 and JPA 2.1

Romain Manni-Bucau
We had (have but see warning at the end) a hibernate profile to build a
tomee-hibernate. Was not activated by default cause of hibernate license
but should still be working.

The small warning is we probably need to upgrade hibernate versions as we
did for eclipselink (right only on master ATM but we'll release soon once
next version is validated).

Finally I'd go with the tomee maven plugin solution which can be as easy as:

<plugin>
  ...
  <configuration>
   <libs>
     <lib>remove:openjpa</lib>
     <lib>unzip:com.jug.workshop:hibernate-bundle:1.0.0:zip</lib>
   </libs>
  </configuration>
</plugin>

if you prepare a zip of hibernate dependencies to add to tomee/lib. TomEE
also has the equivalent in programmatic mode if you want to replace all of
that by code in a dependency.



Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-04-26 9:36 GMT+02:00 Yann BLAZART <[hidden email]>
:

> Hello.
>
> Git clone the TomEE sources  then take a look how the TomEE distributions
> are built (plume by example).
>
> You can do the same thing in your own project / pom, excluding all jpa
> artifacts then adding hibernate ones.
>
> It's even simpler with TomEE embedded.
>
> Regards.
>
> -----Original Message-----
> From: Alex Soto [mailto:[hidden email]]
> Sent: mardi 26 avril 2016 08:31
> To: [hidden email]
> Subject: Re: TomEE 7 and JPA 2.1
>
> Hi Ivan what I would do will be droppng openjpa jars and add Hibernate
> since it is the solution that IMHO most of the people use.
>
> There is a doc in tomee website that explains it
>
> Alex
> El 26 abr. 2016 5:52 a. m., "Mitia Alexandrov" <[hidden email]>
> escribió:
>
> > OpenJpa 2.1 is not ready. Use EclipseLink for JPA 2.1, its shipped
> > with latest Plume :)
> >
> > вт, 26 апр. 2016, 2:08 Ivan St. Ivanov <[hidden email]>:
> >
> > > Hi folks,
> > >
> > > We will be running a series of workshops in Bulgarian JUG to develop
> > > our new website. We'll be using Java EE 7 and TomEE 7. I know it is
> > > still milestone release and not fully EE 7 compatible. But we
> > > decided to take
> > the
> > > "risk".
> > >
> > > In the app we are using the new schema generation annotations coming
> > > with JPA 2.1, but they did not work. When I turned back to the old,
> > > implementation specific ones, it worked.
> > >
> > > Did I get it wrong that none of the WebProfile or PLUME
> > > distributions supports the JPA 2.1 spec? In the former I find
> > > OpenJPA 2.4.0, while in
> > the
> > > latter I see EclipseLink 2.4.2.
> > >
> > > Do you plan to provide JPA 2.1 support at least in the PLUME distro?
> > >
> > > Thanks,
> > > Ivan
> > >
> > > P.S. Roberto sent me a couple of weeks ago instructions how to
> > > integrate Hibernate JPA, but I would like to keep the configuration
> > > steps as few as possible as there will be a lot of people that will
> > > have to do them
> > during
> > > the workshop
> > >
> >
>
>
> This message and any attachments (the "message") is
> intended solely for the intended addressees and is confidential.
> If you receive this message in error,or are not the intended recipient(s),
> please delete it and any copies from your systems and immediately notify
> the sender. Any unauthorized view, use that does not comply with its
> purpose,
> dissemination or disclosure, either whole or partial, is prohibited. Since
> the internet
> cannot guarantee the integrity of this message which may not be reliable,
> BNP PARIBAS
> (and its subsidiaries) shall not be liable for the message if modified,
> changed or falsified.
> Do not print this message unless it is necessary,consider the environment.
>
>
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Ce message et toutes les pieces jointes (ci-apres le "message")
> sont etablis a l'intention exclusive de ses destinataires et sont
> confidentiels.
> Si vous recevez ce message par erreur ou s'il ne vous est pas destine,
> merci de le detruire ainsi que toute copie de votre systeme et d'en avertir
> immediatement l'expediteur. Toute lecture non autorisee, toute utilisation
> de
> ce message qui n'est pas conforme a sa destination, toute diffusion ou
> toute
> publication, totale ou partielle, est interdite. L'Internet ne permettant
> pas d'assurer
> l'integrite de ce message electronique susceptible d'alteration, BNP
> Paribas
> (et ses filiales) decline(nt) toute responsabilite au titre de ce message
> dans l'hypothese
> ou il aurait ete modifie, deforme ou falsifie.
> N'imprimez ce message que si necessaire, pensez a l'environnement.
>