TomEE -Java EE 8 compatible or certified ?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

TomEE -Java EE 8 compatible or certified ?

Franos13
Hello everyone,

As Java EE 8 is out, could you tell us when a TomEE version will be at least compatible or certified released ?
Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle Java One ?)
Have to wait for TomEE 9 because of Servlet 4.0 ?

Best Regards.

________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

Mark Struberg-2
Hi Francois!

The community is already working on EE8.
It's in the tomee8 branch.

LieGrue,
strub


> Am 25.09.2017 um 17:15 schrieb COURTAULT Francois <[hidden email]>:
>
> Hello everyone,
>
> As Java EE 8 is out, could you tell us when a TomEE version will be at least compatible or certified released ?
> Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle Java One ?)
> Have to wait for TomEE 9 because of Servlet 4.0 ?
>
> Best Regards.
>
> ________________________________
> This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.


.
Reply | Threaded
Open this post in threaded view
|

RE: TomEE -Java EE 8 compatible or certified ?

Franos13
Hello,

No doubt about that. My question is more, when could we expect to have TomEE 8 released ?

Best Regards.

-----Original Message-----
From: Mark Struberg [mailto:[hidden email]]
Sent: lundi 25 septembre 2017 17:18
To: [hidden email]
Subject: Re: TomEE -Java EE 8 compatible or certified ?

Hi Francois!

The community is already working on EE8.
It's in the tomee8 branch.

LieGrue,
strub


> Am 25.09.2017 um 17:15 schrieb COURTAULT Francois <[hidden email]>:
>
> Hello everyone,
>
> As Java EE 8 is out, could you tell us when a TomEE version will be at least compatible or certified released ?
> Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle Java
> One ?) Have to wait for TomEE 9 because of Servlet 4.0 ?
>
> Best Regards.
>
> ________________________________
> This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.


.
________________________________
 This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

David Blevins-2
In reply to this post by Franos13
Hi Francois!

As Mark mentions the Java EE 8 work is going on now.  It will be compatible, but not certified -- at least not directly.

The story there is the Java EE TCK licensing agreement between Oracle and Apache expired and is not being renewed due to disagreement on the terms.  So Apache does not have a Java EE 8 TCK.  With my Apache hat on, I worked with Cameron Purdy, then SVP of Development at Oracle, for over 2 years trying to get a new agreement made.  When he departed Oracle, the progress stopped on the Oracle side.

I then switched hats and began pursing things from the Tomitribe.  After a year we have licensed and paid for a TCK.  We can't legally give it to Apache (Oracle's rules) nor can we legally release Apache TomEE (Apache's rules), but we can legally certify something that is 100% Apache TomEE, but with a different name.  I.e. we can take TomEE zip, rename it, run it through the TCK and put it up.  We intend to do that so that Apache TomEE releases are in spirit, certified.

There are some challenges ahead, such as only Tomitribe people can run the TCK or see the results.  Java EE itself is being open sourced, TCKs and all, so this will have a better solution long-term.  Short-term we'll have to power through together as a community and support each other the best we can.


--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com

> On Sep 25, 2017, at 8:15 AM, COURTAULT Francois <[hidden email]> wrote:
>
> Hello everyone,
>
> As Java EE 8 is out, could you tell us when a TomEE version will be at least compatible or certified released ?
> Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle Java One ?)
> Have to wait for TomEE 9 because of Servlet 4.0 ?
>
> Best Regards.
>
> ________________________________
> This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.

Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

Matheus Eduardo Bonifacio Morais

Em 25-09-2017 19:02, David Blevins escreveu:
> Hi Francois!
>
> As Mark mentions the Java EE 8 work is going on now.  It will be compatible, but not certified -- at least not directly.
>
> The story there is the Java EE TCK licensing agreement between Oracle and Apache expired and is not being renewed due to disagreement on the terms.  So Apache does not have a Java EE 8 TCK.  With my Apache hat on, I worked with Cameron Purdy, then SVP of Development at Oracle, for over 2 years trying to get a new agreement made.  When he departed Oracle, the progress stopped on the Oracle side.
>
> I then switched hats and began pursing things from the Tomitribe.  After a year we have licensed and paid for a TCK.  We can't legally give it to Apache (Oracle's rules) nor can we legally release Apache TomEE (Apache's rules), but we can legally certify something that is 100% Apache TomEE, but with a different name.  I.e. we can take TomEE zip, rename it, run it through the TCK and put it up.  We intend to do that so that Apache TomEE releases are in spirit, certified.
>
> There are some challenges ahead, such as only Tomitribe people can run the TCK or see the results.  Java EE itself is being open sourced, TCKs and all, so this will have a better solution long-term.  Short-term we'll have to power through together as a community and support each other the best we can.
Oracle destroy everything, it's their business model. Open source Java
it's nice, but it is too late for the platform IMHO.
>

--
Matheus Eduardo Bonifácio Morais
Analista de Infraestrutura de TI,
Plataforma e Aplicações
Confederação Sicredi

Centro Administrativo Sicredi – Porto Alegre
+55 51 3358 7143

sicredi.com.br
Esta mensagem é somente para uso do destinatário informado e pode conter informações privilegiadas, proprietárias ou privadas. Se você recebeu esta mensagem por engano, por favor, notifique o remetente imediatamente e apague a original. Qualquer outro uso deste e-mail é proibido.

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

Danilo Cominotti Marques
In reply to this post by David Blevins-2
Hello, David!

Thanks for all the details. However, there is another point that currently
worries me: is there any progress on the OpenJPA side of things? By looking
at the commits log on GitHub (which should mirror the Apache repository),
it doesn't seem like a 3.x release that targets JPA 2.1 will happen anytime
soon. Furthermore, the issues targeted at version 3.0.0 in OpenJPA's JIRA
seem not to have received any attention for over a year. Therefore, unless
I am mistaken about OpenJPA's current condition, I don't see TomEE
[non-Plume] implementing all of Java EE 7 soon either, never mind Java EE 8
with JPA 2.2.

On Mon, Sep 25, 2017 at 7:02 PM, David Blevins <[hidden email]>
wrote:

> Hi Francois!
>
> As Mark mentions the Java EE 8 work is going on now.  It will be
> compatible, but not certified -- at least not directly.
>
> The story there is the Java EE TCK licensing agreement between Oracle and
> Apache expired and is not being renewed due to disagreement on the terms.
> So Apache does not have a Java EE 8 TCK.  With my Apache hat on, I worked
> with Cameron Purdy, then SVP of Development at Oracle, for over 2 years
> trying to get a new agreement made.  When he departed Oracle, the progress
> stopped on the Oracle side.
>
> I then switched hats and began pursing things from the Tomitribe.  After a
> year we have licensed and paid for a TCK.  We can't legally give it to
> Apache (Oracle's rules) nor can we legally release Apache TomEE (Apache's
> rules), but we can legally certify something that is 100% Apache TomEE, but
> with a different name.  I.e. we can take TomEE zip, rename it, run it
> through the TCK and put it up.  We intend to do that so that Apache TomEE
> releases are in spirit, certified.
>
> There are some challenges ahead, such as only Tomitribe people can run the
> TCK or see the results.  Java EE itself is being open sourced, TCKs and
> all, so this will have a better solution long-term.  Short-term we'll have
> to power through together as a community and support each other the best we
> can.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> > On Sep 25, 2017, at 8:15 AM, COURTAULT Francois <
> [hidden email]> wrote:
> >
> > Hello everyone,
> >
> > As Java EE 8 is out, could you tell us when a TomEE version will be at
> least compatible or certified released ?
> > Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle Java One
> ?)
> > Have to wait for TomEE 9 because of Servlet 4.0 ?
> >
> > Best Regards.
> >
> > ________________________________
> > This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> > E-mails are susceptible to alteration. Our company shall not be liable
> for the message if altered, changed or falsified. If you are not the
> intended recipient of this message, please delete it and notify the sender.
> > Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>
>
Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

agumbrecht
Hi Danilo,

I'd personally only consider Hibernate or EclipseLink as production
contenders with TomEE. We can certify with either, but can only
distribute EclipseLink.

OpenJPA has lost it's momentum for sure, but that doesn't mean TomEE
will stand still at all. It's only about packaging, so quite trivial really.

That said, I'm sure that being OSS means that anyone willing can dive
into OpenJPA and make things happen. Even you might like to help?

Andy.


On 25/09/17 15:20, Danilo Cominotti Marques wrote:

> Hello, David!
>
> Thanks for all the details. However, there is another point that currently
> worries me: is there any progress on the OpenJPA side of things? By looking
> at the commits log on GitHub (which should mirror the Apache repository),
> it doesn't seem like a 3.x release that targets JPA 2.1 will happen anytime
> soon. Furthermore, the issues targeted at version 3.0.0 in OpenJPA's JIRA
> seem not to have received any attention for over a year. Therefore, unless
> I am mistaken about OpenJPA's current condition, I don't see TomEE
> [non-Plume] implementing all of Java EE 7 soon either, never mind Java EE 8
> with JPA 2.2.
>
> On Mon, Sep 25, 2017 at 7:02 PM, David Blevins <[hidden email]>
> wrote:
>
>> Hi Francois!
>>
>> As Mark mentions the Java EE 8 work is going on now.  It will be
>> compatible, but not certified -- at least not directly.
>>
>> The story there is the Java EE TCK licensing agreement between Oracle and
>> Apache expired and is not being renewed due to disagreement on the terms.
>> So Apache does not have a Java EE 8 TCK.  With my Apache hat on, I worked
>> with Cameron Purdy, then SVP of Development at Oracle, for over 2 years
>> trying to get a new agreement made.  When he departed Oracle, the progress
>> stopped on the Oracle side.
>>
>> I then switched hats and began pursing things from the Tomitribe.  After a
>> year we have licensed and paid for a TCK.  We can't legally give it to
>> Apache (Oracle's rules) nor can we legally release Apache TomEE (Apache's
>> rules), but we can legally certify something that is 100% Apache TomEE, but
>> with a different name.  I.e. we can take TomEE zip, rename it, run it
>> through the TCK and put it up.  We intend to do that so that Apache TomEE
>> releases are in spirit, certified.
>>
>> There are some challenges ahead, such as only Tomitribe people can run the
>> TCK or see the results.  Java EE itself is being open sourced, TCKs and
>> all, so this will have a better solution long-term.  Short-term we'll have
>> to power through together as a community and support each other the best we
>> can.
>>
>>
>> --
>> David Blevins
>> http://twitter.com/dblevins
>> http://www.tomitribe.com
>>
>>> On Sep 25, 2017, at 8:15 AM, COURTAULT Francois <
>> [hidden email]> wrote:
>>> Hello everyone,
>>>
>>> As Java EE 8 is out, could you tell us when a TomEE version will be at
>> least compatible or certified released ?
>>> Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle Java One
>> ?)
>>> Have to wait for TomEE 9 because of Servlet 4.0 ?
>>>
>>> Best Regards.
>>>
>>> ________________________________
>>> This message and any attachments are intended solely for the addressees
>> and may contain confidential information. Any unauthorized use or
>> disclosure, either whole or partial, is prohibited.
>>> E-mails are susceptible to alteration. Our company shall not be liable
>> for the message if altered, changed or falsified. If you are not the
>> intended recipient of this message, please delete it and notify the sender.
>>> Although all reasonable efforts have been made to keep this transmission
>> free from viruses, the sender will not be liable for damages caused by a
>> transmitted virus.
>>
>>

    --
    Andy Gumbrecht

    http://www.tomitribe.com
    agumbrecht@tomitribe.com
    https://twitter.com/AndyGeeDe

    TomEE treibt Tomitribe ! | http://tomee.apache.org
Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

chongma
i am using TomEE 7.0.3 Plus with OpenJPA in production and haven't had
any problems although i get your point that it is only JPA 2.0. Romain
Manni-Bucau and Mark Struberg have been great with support when I made
the transition from EclipseLink to OpenJPA.  I also thought I heard the
other day that Mark has been working towards a 3.x release

On 27/09/2017 07:01, Andy Gumbrecht wrote:

> Hi Danilo,
>
> I'd personally only consider Hibernate or EclipseLink as production
> contenders with TomEE. We can certify with either, but can only
> distribute EclipseLink.
>
> OpenJPA has lost it's momentum for sure, but that doesn't mean TomEE
> will stand still at all. It's only about packaging, so quite trivial
> really.
>
> That said, I'm sure that being OSS means that anyone willing can dive
> into OpenJPA and make things happen. Even you might like to help?
>
> Andy.
>
>
> On 25/09/17 15:20, Danilo Cominotti Marques wrote:
>> Hello, David!
>>
>> Thanks for all the details. However, there is another point that
>> currently
>> worries me: is there any progress on the OpenJPA side of things? By
>> looking
>> at the commits log on GitHub (which should mirror the Apache
>> repository),
>> it doesn't seem like a 3.x release that targets JPA 2.1 will happen
>> anytime
>> soon. Furthermore, the issues targeted at version 3.0.0 in OpenJPA's
>> JIRA
>> seem not to have received any attention for over a year. Therefore,
>> unless
>> I am mistaken about OpenJPA's current condition, I don't see TomEE
>> [non-Plume] implementing all of Java EE 7 soon either, never mind
>> Java EE 8
>> with JPA 2.2.
>>
>> On Mon, Sep 25, 2017 at 7:02 PM, David Blevins <[hidden email]>
>> wrote:
>>
>>> Hi Francois!
>>>
>>> As Mark mentions the Java EE 8 work is going on now.  It will be
>>> compatible, but not certified -- at least not directly.
>>>
>>> The story there is the Java EE TCK licensing agreement between
>>> Oracle and
>>> Apache expired and is not being renewed due to disagreement on the
>>> terms.
>>> So Apache does not have a Java EE 8 TCK.  With my Apache hat on, I
>>> worked
>>> with Cameron Purdy, then SVP of Development at Oracle, for over 2 years
>>> trying to get a new agreement made.  When he departed Oracle, the
>>> progress
>>> stopped on the Oracle side.
>>>
>>> I then switched hats and began pursing things from the Tomitribe. 
>>> After a
>>> year we have licensed and paid for a TCK.  We can't legally give it to
>>> Apache (Oracle's rules) nor can we legally release Apache TomEE
>>> (Apache's
>>> rules), but we can legally certify something that is 100% Apache
>>> TomEE, but
>>> with a different name.  I.e. we can take TomEE zip, rename it, run it
>>> through the TCK and put it up.  We intend to do that so that Apache
>>> TomEE
>>> releases are in spirit, certified.
>>>
>>> There are some challenges ahead, such as only Tomitribe people can
>>> run the
>>> TCK or see the results.  Java EE itself is being open sourced, TCKs and
>>> all, so this will have a better solution long-term. Short-term we'll
>>> have
>>> to power through together as a community and support each other the
>>> best we
>>> can.
>>>
>>>
>>> --
>>> David Blevins
>>> http://twitter.com/dblevins
>>> http://www.tomitribe.com
>>>
>>>> On Sep 25, 2017, at 8:15 AM, COURTAULT Francois <
>>> [hidden email]> wrote:
>>>> Hello everyone,
>>>>
>>>> As Java EE 8 is out, could you tell us when a TomEE version will be at
>>> least compatible or certified released ?
>>>> Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle
>>>> Java One
>>> ?)
>>>> Have to wait for TomEE 9 because of Servlet 4.0 ?
>>>>
>>>> Best Regards.
>>>>
>>>> ________________________________
>>>> This message and any attachments are intended solely for the
>>>> addressees
>>> and may contain confidential information. Any unauthorized use or
>>> disclosure, either whole or partial, is prohibited.
>>>> E-mails are susceptible to alteration. Our company shall not be liable
>>> for the message if altered, changed or falsified. If you are not the
>>> intended recipient of this message, please delete it and notify the
>>> sender.
>>>> Although all reasonable efforts have been made to keep this
>>>> transmission
>>> free from viruses, the sender will not be liable for damages caused
>>> by a
>>> transmitted virus.
>>>
>>>
>

Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

Maxim Solodovnik
Hello Matthew,

sorry for off-topic ... why have you migrated from EclipseLink?

On Wed, Sep 27, 2017 at 4:22 PM, Matthew Broadhead <
[hidden email]> wrote:

> i am using TomEE 7.0.3 Plus with OpenJPA in production and haven't had any
> problems although i get your point that it is only JPA 2.0. Romain
> Manni-Bucau and Mark Struberg have been great with support when I made the
> transition from EclipseLink to OpenJPA.  I also thought I heard the other
> day that Mark has been working towards a 3.x release
>
>
> On 27/09/2017 07:01, Andy Gumbrecht wrote:
>
>> Hi Danilo,
>>
>> I'd personally only consider Hibernate or EclipseLink as production
>> contenders with TomEE. We can certify with either, but can only distribute
>> EclipseLink.
>>
>> OpenJPA has lost it's momentum for sure, but that doesn't mean TomEE will
>> stand still at all. It's only about packaging, so quite trivial really.
>>
>> That said, I'm sure that being OSS means that anyone willing can dive
>> into OpenJPA and make things happen. Even you might like to help?
>>
>> Andy.
>>
>>
>> On 25/09/17 15:20, Danilo Cominotti Marques wrote:
>>
>>> Hello, David!
>>>
>>> Thanks for all the details. However, there is another point that
>>> currently
>>> worries me: is there any progress on the OpenJPA side of things? By
>>> looking
>>> at the commits log on GitHub (which should mirror the Apache repository),
>>> it doesn't seem like a 3.x release that targets JPA 2.1 will happen
>>> anytime
>>> soon. Furthermore, the issues targeted at version 3.0.0 in OpenJPA's JIRA
>>> seem not to have received any attention for over a year. Therefore,
>>> unless
>>> I am mistaken about OpenJPA's current condition, I don't see TomEE
>>> [non-Plume] implementing all of Java EE 7 soon either, never mind Java
>>> EE 8
>>> with JPA 2.2.
>>>
>>> On Mon, Sep 25, 2017 at 7:02 PM, David Blevins <[hidden email]>
>>> wrote:
>>>
>>> Hi Francois!
>>>>
>>>> As Mark mentions the Java EE 8 work is going on now.  It will be
>>>> compatible, but not certified -- at least not directly.
>>>>
>>>> The story there is the Java EE TCK licensing agreement between Oracle
>>>> and
>>>> Apache expired and is not being renewed due to disagreement on the
>>>> terms.
>>>> So Apache does not have a Java EE 8 TCK.  With my Apache hat on, I
>>>> worked
>>>> with Cameron Purdy, then SVP of Development at Oracle, for over 2 years
>>>> trying to get a new agreement made.  When he departed Oracle, the
>>>> progress
>>>> stopped on the Oracle side.
>>>>
>>>> I then switched hats and began pursing things from the Tomitribe.
>>>> After a
>>>> year we have licensed and paid for a TCK.  We can't legally give it to
>>>> Apache (Oracle's rules) nor can we legally release Apache TomEE
>>>> (Apache's
>>>> rules), but we can legally certify something that is 100% Apache TomEE,
>>>> but
>>>> with a different name.  I.e. we can take TomEE zip, rename it, run it
>>>> through the TCK and put it up.  We intend to do that so that Apache
>>>> TomEE
>>>> releases are in spirit, certified.
>>>>
>>>> There are some challenges ahead, such as only Tomitribe people can run
>>>> the
>>>> TCK or see the results.  Java EE itself is being open sourced, TCKs and
>>>> all, so this will have a better solution long-term. Short-term we'll
>>>> have
>>>> to power through together as a community and support each other the
>>>> best we
>>>> can.
>>>>
>>>>
>>>> --
>>>> David Blevins
>>>> http://twitter.com/dblevins
>>>> http://www.tomitribe.com
>>>>
>>>> On Sep 25, 2017, at 8:15 AM, COURTAULT Francois <
>>>>>
>>>> [hidden email]> wrote:
>>>>
>>>>> Hello everyone,
>>>>>
>>>>> As Java EE 8 is out, could you tell us when a TomEE version will be at
>>>>>
>>>> least compatible or certified released ?
>>>>
>>>>> Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle Java
>>>>> One
>>>>>
>>>> ?)
>>>>
>>>>> Have to wait for TomEE 9 because of Servlet 4.0 ?
>>>>>
>>>>> Best Regards.
>>>>>
>>>>> ________________________________
>>>>> This message and any attachments are intended solely for the addressees
>>>>>
>>>> and may contain confidential information. Any unauthorized use or
>>>> disclosure, either whole or partial, is prohibited.
>>>>
>>>>> E-mails are susceptible to alteration. Our company shall not be liable
>>>>>
>>>> for the message if altered, changed or falsified. If you are not the
>>>> intended recipient of this message, please delete it and notify the
>>>> sender.
>>>>
>>>>> Although all reasonable efforts have been made to keep this
>>>>> transmission
>>>>>
>>>> free from viruses, the sender will not be liable for damages caused by a
>>>> transmitted virus.
>>>>
>>>>
>>>>
>>
>


--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

chongma
hi Maxim
i wanted to use full stack TomEE (minimise external dependencies) and it
seemed the in house JPA option gave me better support from the TomEE
team.  also once i had overcome the differences between EclipseLink and
OpenJPA OpenJPA seems to work more logically IMHO (less peculiarities). 
everyone will have their own preference but in my case working with JSF,
CDI, CXF etc i now feel comfortable with OpenJPA.

On 27/09/2017 11:23, Maxim Solodovnik wrote:

> Hello Matthew,
>
> sorry for off-topic ... why have you migrated from EclipseLink?
>
> On Wed, Sep 27, 2017 at 4:22 PM, Matthew Broadhead <
> [hidden email]> wrote:
>
>> i am using TomEE 7.0.3 Plus with OpenJPA in production and haven't had any
>> problems although i get your point that it is only JPA 2.0. Romain
>> Manni-Bucau and Mark Struberg have been great with support when I made the
>> transition from EclipseLink to OpenJPA.  I also thought I heard the other
>> day that Mark has been working towards a 3.x release
>>
>>
>> On 27/09/2017 07:01, Andy Gumbrecht wrote:
>>
>>> Hi Danilo,
>>>
>>> I'd personally only consider Hibernate or EclipseLink as production
>>> contenders with TomEE. We can certify with either, but can only distribute
>>> EclipseLink.
>>>
>>> OpenJPA has lost it's momentum for sure, but that doesn't mean TomEE will
>>> stand still at all. It's only about packaging, so quite trivial really.
>>>
>>> That said, I'm sure that being OSS means that anyone willing can dive
>>> into OpenJPA and make things happen. Even you might like to help?
>>>
>>> Andy.
>>>
>>>
>>> On 25/09/17 15:20, Danilo Cominotti Marques wrote:
>>>
>>>> Hello, David!
>>>>
>>>> Thanks for all the details. However, there is another point that
>>>> currently
>>>> worries me: is there any progress on the OpenJPA side of things? By
>>>> looking
>>>> at the commits log on GitHub (which should mirror the Apache repository),
>>>> it doesn't seem like a 3.x release that targets JPA 2.1 will happen
>>>> anytime
>>>> soon. Furthermore, the issues targeted at version 3.0.0 in OpenJPA's JIRA
>>>> seem not to have received any attention for over a year. Therefore,
>>>> unless
>>>> I am mistaken about OpenJPA's current condition, I don't see TomEE
>>>> [non-Plume] implementing all of Java EE 7 soon either, never mind Java
>>>> EE 8
>>>> with JPA 2.2.
>>>>
>>>> On Mon, Sep 25, 2017 at 7:02 PM, David Blevins <[hidden email]>
>>>> wrote:
>>>>
>>>> Hi Francois!
>>>>> As Mark mentions the Java EE 8 work is going on now.  It will be
>>>>> compatible, but not certified -- at least not directly.
>>>>>
>>>>> The story there is the Java EE TCK licensing agreement between Oracle
>>>>> and
>>>>> Apache expired and is not being renewed due to disagreement on the
>>>>> terms.
>>>>> So Apache does not have a Java EE 8 TCK.  With my Apache hat on, I
>>>>> worked
>>>>> with Cameron Purdy, then SVP of Development at Oracle, for over 2 years
>>>>> trying to get a new agreement made.  When he departed Oracle, the
>>>>> progress
>>>>> stopped on the Oracle side.
>>>>>
>>>>> I then switched hats and began pursing things from the Tomitribe.
>>>>> After a
>>>>> year we have licensed and paid for a TCK.  We can't legally give it to
>>>>> Apache (Oracle's rules) nor can we legally release Apache TomEE
>>>>> (Apache's
>>>>> rules), but we can legally certify something that is 100% Apache TomEE,
>>>>> but
>>>>> with a different name.  I.e. we can take TomEE zip, rename it, run it
>>>>> through the TCK and put it up.  We intend to do that so that Apache
>>>>> TomEE
>>>>> releases are in spirit, certified.
>>>>>
>>>>> There are some challenges ahead, such as only Tomitribe people can run
>>>>> the
>>>>> TCK or see the results.  Java EE itself is being open sourced, TCKs and
>>>>> all, so this will have a better solution long-term. Short-term we'll
>>>>> have
>>>>> to power through together as a community and support each other the
>>>>> best we
>>>>> can.
>>>>>
>>>>>
>>>>> --
>>>>> David Blevins
>>>>> http://twitter.com/dblevins
>>>>> http://www.tomitribe.com
>>>>>
>>>>> On Sep 25, 2017, at 8:15 AM, COURTAULT Francois <
>>>>> [hidden email]> wrote:
>>>>>
>>>>>> Hello everyone,
>>>>>>
>>>>>> As Java EE 8 is out, could you tell us when a TomEE version will be at
>>>>>>
>>>>> least compatible or certified released ?
>>>>>
>>>>>> Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle Java
>>>>>> One
>>>>>>
>>>>> ?)
>>>>>
>>>>>> Have to wait for TomEE 9 because of Servlet 4.0 ?
>>>>>>
>>>>>> Best Regards.
>>>>>>
>>>>>> ________________________________
>>>>>> This message and any attachments are intended solely for the addressees
>>>>>>
>>>>> and may contain confidential information. Any unauthorized use or
>>>>> disclosure, either whole or partial, is prohibited.
>>>>>
>>>>>> E-mails are susceptible to alteration. Our company shall not be liable
>>>>>>
>>>>> for the message if altered, changed or falsified. If you are not the
>>>>> intended recipient of this message, please delete it and notify the
>>>>> sender.
>>>>>
>>>>>> Although all reasonable efforts have been made to keep this
>>>>>> transmission
>>>>>>
>>>>> free from viruses, the sender will not be liable for damages caused by a
>>>>> transmitted virus.
>>>>>
>>>>>
>>>>>
>

Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

Maxim Solodovnik
Thanks :)

We are currently using OpenJPA, and I'm a little bit worried regarding my
next steps if I have to change it to something else.
Hibernate is not an option due to licensing limitations ...

On Wed, Sep 27, 2017 at 4:30 PM, Matthew Broadhead <
[hidden email]> wrote:

> hi Maxim
> i wanted to use full stack TomEE (minimise external dependencies) and it
> seemed the in house JPA option gave me better support from the TomEE team.
> also once i had overcome the differences between EclipseLink and OpenJPA
> OpenJPA seems to work more logically IMHO (less peculiarities).  everyone
> will have their own preference but in my case working with JSF, CDI, CXF
> etc i now feel comfortable with OpenJPA.
>
>
> On 27/09/2017 11:23, Maxim Solodovnik wrote:
>
>> Hello Matthew,
>>
>> sorry for off-topic ... why have you migrated from EclipseLink?
>>
>> On Wed, Sep 27, 2017 at 4:22 PM, Matthew Broadhead <
>> [hidden email]> wrote:
>>
>> i am using TomEE 7.0.3 Plus with OpenJPA in production and haven't had any
>>> problems although i get your point that it is only JPA 2.0. Romain
>>> Manni-Bucau and Mark Struberg have been great with support when I made
>>> the
>>> transition from EclipseLink to OpenJPA.  I also thought I heard the other
>>> day that Mark has been working towards a 3.x release
>>>
>>>
>>> On 27/09/2017 07:01, Andy Gumbrecht wrote:
>>>
>>> Hi Danilo,
>>>>
>>>> I'd personally only consider Hibernate or EclipseLink as production
>>>> contenders with TomEE. We can certify with either, but can only
>>>> distribute
>>>> EclipseLink.
>>>>
>>>> OpenJPA has lost it's momentum for sure, but that doesn't mean TomEE
>>>> will
>>>> stand still at all. It's only about packaging, so quite trivial really.
>>>>
>>>> That said, I'm sure that being OSS means that anyone willing can dive
>>>> into OpenJPA and make things happen. Even you might like to help?
>>>>
>>>> Andy.
>>>>
>>>>
>>>> On 25/09/17 15:20, Danilo Cominotti Marques wrote:
>>>>
>>>> Hello, David!
>>>>>
>>>>> Thanks for all the details. However, there is another point that
>>>>> currently
>>>>> worries me: is there any progress on the OpenJPA side of things? By
>>>>> looking
>>>>> at the commits log on GitHub (which should mirror the Apache
>>>>> repository),
>>>>> it doesn't seem like a 3.x release that targets JPA 2.1 will happen
>>>>> anytime
>>>>> soon. Furthermore, the issues targeted at version 3.0.0 in OpenJPA's
>>>>> JIRA
>>>>> seem not to have received any attention for over a year. Therefore,
>>>>> unless
>>>>> I am mistaken about OpenJPA's current condition, I don't see TomEE
>>>>> [non-Plume] implementing all of Java EE 7 soon either, never mind Java
>>>>> EE 8
>>>>> with JPA 2.2.
>>>>>
>>>>> On Mon, Sep 25, 2017 at 7:02 PM, David Blevins <
>>>>> [hidden email]>
>>>>> wrote:
>>>>>
>>>>> Hi Francois!
>>>>>
>>>>>> As Mark mentions the Java EE 8 work is going on now.  It will be
>>>>>> compatible, but not certified -- at least not directly.
>>>>>>
>>>>>> The story there is the Java EE TCK licensing agreement between Oracle
>>>>>> and
>>>>>> Apache expired and is not being renewed due to disagreement on the
>>>>>> terms.
>>>>>> So Apache does not have a Java EE 8 TCK.  With my Apache hat on, I
>>>>>> worked
>>>>>> with Cameron Purdy, then SVP of Development at Oracle, for over 2
>>>>>> years
>>>>>> trying to get a new agreement made.  When he departed Oracle, the
>>>>>> progress
>>>>>> stopped on the Oracle side.
>>>>>>
>>>>>> I then switched hats and began pursing things from the Tomitribe.
>>>>>> After a
>>>>>> year we have licensed and paid for a TCK.  We can't legally give it to
>>>>>> Apache (Oracle's rules) nor can we legally release Apache TomEE
>>>>>> (Apache's
>>>>>> rules), but we can legally certify something that is 100% Apache
>>>>>> TomEE,
>>>>>> but
>>>>>> with a different name.  I.e. we can take TomEE zip, rename it, run it
>>>>>> through the TCK and put it up.  We intend to do that so that Apache
>>>>>> TomEE
>>>>>> releases are in spirit, certified.
>>>>>>
>>>>>> There are some challenges ahead, such as only Tomitribe people can run
>>>>>> the
>>>>>> TCK or see the results.  Java EE itself is being open sourced, TCKs
>>>>>> and
>>>>>> all, so this will have a better solution long-term. Short-term we'll
>>>>>> have
>>>>>> to power through together as a community and support each other the
>>>>>> best we
>>>>>> can.
>>>>>>
>>>>>>
>>>>>> --
>>>>>> David Blevins
>>>>>> http://twitter.com/dblevins
>>>>>> http://www.tomitribe.com
>>>>>>
>>>>>> On Sep 25, 2017, at 8:15 AM, COURTAULT Francois <
>>>>>> [hidden email]> wrote:
>>>>>>
>>>>>> Hello everyone,
>>>>>>>
>>>>>>> As Java EE 8 is out, could you tell us when a TomEE version will be
>>>>>>> at
>>>>>>>
>>>>>>> least compatible or certified released ?
>>>>>>
>>>>>> Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle Java
>>>>>>> One
>>>>>>>
>>>>>>> ?)
>>>>>>
>>>>>> Have to wait for TomEE 9 because of Servlet 4.0 ?
>>>>>>>
>>>>>>> Best Regards.
>>>>>>>
>>>>>>> ________________________________
>>>>>>> This message and any attachments are intended solely for the
>>>>>>> addressees
>>>>>>>
>>>>>>> and may contain confidential information. Any unauthorized use or
>>>>>> disclosure, either whole or partial, is prohibited.
>>>>>>
>>>>>> E-mails are susceptible to alteration. Our company shall not be liable
>>>>>>>
>>>>>>> for the message if altered, changed or falsified. If you are not the
>>>>>> intended recipient of this message, please delete it and notify the
>>>>>> sender.
>>>>>>
>>>>>> Although all reasonable efforts have been made to keep this
>>>>>>> transmission
>>>>>>>
>>>>>>> free from viruses, the sender will not be liable for damages caused
>>>>>> by a
>>>>>> transmitted virus.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>
>


--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

Romain Manni-Bucau
presonally I got a lot of surprises with eclipselink (like good perf out of
the both...cause cache is on by default which doesnt enjoy clustering the
apps, like getting connections used outside transactions where the entity
should be a dead DTO etc...) which made applications uncontrolled so
OpenJPA being closer to the spec is very appreciated even if it requires
some setup to have the bytecode enhancement done right.


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

2017-09-27 11:54 GMT+02:00 Maxim Solodovnik <[hidden email]>:

> Thanks :)
>
> We are currently using OpenJPA, and I'm a little bit worried regarding my
> next steps if I have to change it to something else.
> Hibernate is not an option due to licensing limitations ...
>
> On Wed, Sep 27, 2017 at 4:30 PM, Matthew Broadhead <
> [hidden email]> wrote:
>
> > hi Maxim
> > i wanted to use full stack TomEE (minimise external dependencies) and it
> > seemed the in house JPA option gave me better support from the TomEE
> team.
> > also once i had overcome the differences between EclipseLink and OpenJPA
> > OpenJPA seems to work more logically IMHO (less peculiarities).  everyone
> > will have their own preference but in my case working with JSF, CDI, CXF
> > etc i now feel comfortable with OpenJPA.
> >
> >
> > On 27/09/2017 11:23, Maxim Solodovnik wrote:
> >
> >> Hello Matthew,
> >>
> >> sorry for off-topic ... why have you migrated from EclipseLink?
> >>
> >> On Wed, Sep 27, 2017 at 4:22 PM, Matthew Broadhead <
> >> [hidden email]> wrote:
> >>
> >> i am using TomEE 7.0.3 Plus with OpenJPA in production and haven't had
> any
> >>> problems although i get your point that it is only JPA 2.0. Romain
> >>> Manni-Bucau and Mark Struberg have been great with support when I made
> >>> the
> >>> transition from EclipseLink to OpenJPA.  I also thought I heard the
> other
> >>> day that Mark has been working towards a 3.x release
> >>>
> >>>
> >>> On 27/09/2017 07:01, Andy Gumbrecht wrote:
> >>>
> >>> Hi Danilo,
> >>>>
> >>>> I'd personally only consider Hibernate or EclipseLink as production
> >>>> contenders with TomEE. We can certify with either, but can only
> >>>> distribute
> >>>> EclipseLink.
> >>>>
> >>>> OpenJPA has lost it's momentum for sure, but that doesn't mean TomEE
> >>>> will
> >>>> stand still at all. It's only about packaging, so quite trivial
> really.
> >>>>
> >>>> That said, I'm sure that being OSS means that anyone willing can dive
> >>>> into OpenJPA and make things happen. Even you might like to help?
> >>>>
> >>>> Andy.
> >>>>
> >>>>
> >>>> On 25/09/17 15:20, Danilo Cominotti Marques wrote:
> >>>>
> >>>> Hello, David!
> >>>>>
> >>>>> Thanks for all the details. However, there is another point that
> >>>>> currently
> >>>>> worries me: is there any progress on the OpenJPA side of things? By
> >>>>> looking
> >>>>> at the commits log on GitHub (which should mirror the Apache
> >>>>> repository),
> >>>>> it doesn't seem like a 3.x release that targets JPA 2.1 will happen
> >>>>> anytime
> >>>>> soon. Furthermore, the issues targeted at version 3.0.0 in OpenJPA's
> >>>>> JIRA
> >>>>> seem not to have received any attention for over a year. Therefore,
> >>>>> unless
> >>>>> I am mistaken about OpenJPA's current condition, I don't see TomEE
> >>>>> [non-Plume] implementing all of Java EE 7 soon either, never mind
> Java
> >>>>> EE 8
> >>>>> with JPA 2.2.
> >>>>>
> >>>>> On Mon, Sep 25, 2017 at 7:02 PM, David Blevins <
> >>>>> [hidden email]>
> >>>>> wrote:
> >>>>>
> >>>>> Hi Francois!
> >>>>>
> >>>>>> As Mark mentions the Java EE 8 work is going on now.  It will be
> >>>>>> compatible, but not certified -- at least not directly.
> >>>>>>
> >>>>>> The story there is the Java EE TCK licensing agreement between
> Oracle
> >>>>>> and
> >>>>>> Apache expired and is not being renewed due to disagreement on the
> >>>>>> terms.
> >>>>>> So Apache does not have a Java EE 8 TCK.  With my Apache hat on, I
> >>>>>> worked
> >>>>>> with Cameron Purdy, then SVP of Development at Oracle, for over 2
> >>>>>> years
> >>>>>> trying to get a new agreement made.  When he departed Oracle, the
> >>>>>> progress
> >>>>>> stopped on the Oracle side.
> >>>>>>
> >>>>>> I then switched hats and began pursing things from the Tomitribe.
> >>>>>> After a
> >>>>>> year we have licensed and paid for a TCK.  We can't legally give it
> to
> >>>>>> Apache (Oracle's rules) nor can we legally release Apache TomEE
> >>>>>> (Apache's
> >>>>>> rules), but we can legally certify something that is 100% Apache
> >>>>>> TomEE,
> >>>>>> but
> >>>>>> with a different name.  I.e. we can take TomEE zip, rename it, run
> it
> >>>>>> through the TCK and put it up.  We intend to do that so that Apache
> >>>>>> TomEE
> >>>>>> releases are in spirit, certified.
> >>>>>>
> >>>>>> There are some challenges ahead, such as only Tomitribe people can
> run
> >>>>>> the
> >>>>>> TCK or see the results.  Java EE itself is being open sourced, TCKs
> >>>>>> and
> >>>>>> all, so this will have a better solution long-term. Short-term we'll
> >>>>>> have
> >>>>>> to power through together as a community and support each other the
> >>>>>> best we
> >>>>>> can.
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> David Blevins
> >>>>>> http://twitter.com/dblevins
> >>>>>> http://www.tomitribe.com
> >>>>>>
> >>>>>> On Sep 25, 2017, at 8:15 AM, COURTAULT Francois <
> >>>>>> [hidden email]> wrote:
> >>>>>>
> >>>>>> Hello everyone,
> >>>>>>>
> >>>>>>> As Java EE 8 is out, could you tell us when a TomEE version will be
> >>>>>>> at
> >>>>>>>
> >>>>>>> least compatible or certified released ?
> >>>>>>
> >>>>>> Any pointer to TomEE roadmap ? (Maybe an announcement at Oracle Java
> >>>>>>> One
> >>>>>>>
> >>>>>>> ?)
> >>>>>>
> >>>>>> Have to wait for TomEE 9 because of Servlet 4.0 ?
> >>>>>>>
> >>>>>>> Best Regards.
> >>>>>>>
> >>>>>>> ________________________________
> >>>>>>> This message and any attachments are intended solely for the
> >>>>>>> addressees
> >>>>>>>
> >>>>>>> and may contain confidential information. Any unauthorized use or
> >>>>>> disclosure, either whole or partial, is prohibited.
> >>>>>>
> >>>>>> E-mails are susceptible to alteration. Our company shall not be
> liable
> >>>>>>>
> >>>>>>> for the message if altered, changed or falsified. If you are not
> the
> >>>>>> intended recipient of this message, please delete it and notify the
> >>>>>> sender.
> >>>>>>
> >>>>>> Although all reasonable efforts have been made to keep this
> >>>>>>> transmission
> >>>>>>>
> >>>>>>> free from viruses, the sender will not be liable for damages caused
> >>>>>> by a
> >>>>>> transmitted virus.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>
> >
>
>
> --
> WBR
> Maxim aka solomax
>
Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

cocorossello
In reply to this post by Maxim Solodovnik
Hi,

One question about future TomEE 8. Would it be compatible with java 9? (I
mean project compiled to java 9, I can run tomee 7 with java 9 runtime but I
have to compile to java 8).



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

David Blevins-2

> On Sep 27, 2017, at 3:00 AM, cocorossello <[hidden email]> wrote:
>
> Hi,
>
> One question about future TomEE 8. Would it be compatible with java 9? (I
> mean project compiled to java 9, I can run tomee 7 with java 9 runtime but I
> have to compile to java 8).

Effectively that comes down to are we going to drop support for Java 8 in TomEE 8.  So far that has not been discussed.

Is there something specific you're looking for from Java 9 to be leveraged in TomEE 8?


-David

Reply | Threaded
Open this post in threaded view
|

Re: TomEE -Java EE 8 compatible or certified ?

Mark Struberg-2
Hmm, EE8 requires Java8. Just from the API alone.
And anything compiled with Java8 will also run on Java9, right?

So I'd say the minimum requirement in TomEE8 is Java8.

Btw, we still can use Java9 for the TomEE8 development!
The new Java9 Maven build chain supports to generate real Java8 code by making use of the new Java9 javac --release feature.

Imo we should be perfectly fine supporting Java8++ in TomEE8

LieGrue,
strub


> Am 28.09.2017 um 19:15 schrieb David Blevins <[hidden email]>:
>
>
>> On Sep 27, 2017, at 3:00 AM, cocorossello <[hidden email]> wrote:
>>
>> Hi,
>>
>> One question about future TomEE 8. Would it be compatible with java 9? (I
>> mean project compiled to java 9, I can run tomee 7 with java 9 runtime but I
>> have to compile to java 8).
>
> Effectively that comes down to are we going to drop support for Java 8 in TomEE 8.  So far that has not been discussed.
>
> Is there something specific you're looking for from Java 9 to be leveraged in TomEE 8?
>
>
> -David
>