You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by COURTAULT Francois <Fr...@gemalto.com> on 2015/12/28 12:30:59 UTC
Question about Java EE certification TomEE and Plume
Hello everyone,
TomEE is quite nice but one thing which annoys me is about certification using EclipseLink.
Let me explain my concern:
Some application servers like Weblogic and even Liberty, quite recently, uses EclipseLink as the JPA layer.
But If I look at the TomEE docs, only the Plume delivery contains EclipseLink as the JPA layer, but this one is not Java EE 6 certified.
Just want to know, if there are future plans in order to have JAX-RS delivery be Java EE 6 or Java EE 7 web profile certified but using EclipselInk (alternative to OpenJPA) as the JPA layer ?
I ask this question because it will most probably ease our migration from some commercial app vendors to TomEE.
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.
Re: Question about Java EE certification TomEE and Plume
Posted by Romain Manni-Bucau <rm...@gmail.com>.
To be complete JAXRS was certified only cause EE7 web profile is our (old
since tomee 7 is out ;)) JAXRS distribution so we got the certification for
our jaxrs distribution as well.
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>
2016-01-11 9:13 GMT+01:00 Jean-Louis Monteiro <jl...@tomitribe.com>:
> Correct.
>
> Even if we pass the WebProfile TCK for Plus and Plume we can't claim to be
> certified.
>
> There is no equivalent profile for TomEE Plus or Plume.
> Also correct for JAX-RS.
>
> Jean-Louis
>
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Mon, Jan 11, 2016 at 9:07 AM, COURTAULT Francois <
> Francois.Courtault@gemalto.com> wrote:
>
>> Hello Romain,
>>
>> To be sure to have understood you well: Plume is Java EE6 Web profile
>> certified (pass the TCK tests) and not Java EE6 Full profile: right ?
>> According to an answer I have received, it seems that the Plume JAX-RS
>> part is also certified, right ?
>>
>> Best Regards.
>>
>> -----Original Message-----
>> From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>> Sent: lundi 11 janvier 2016 09:02
>> To: COURTAULT Francois
>> Cc: users@tomee.apache.org
>> Subject: Re: Question about Java EE certification TomEE and Plume
>>
>> Ok, I was not very clear - let's blame the phone for this one ;): we cant
>> certify tomee+ cause we dont pass (= dont run) TCKs for > webprofile (JMS
>> for instance). Plume being plus based it has the same constraint but we
>> pass TCKs for the webprofile part - hope it is clearer.
>>
>>
>> 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>
>>
>> 2016-01-11 8:58 GMT+01:00 COURTAULT Francois <
>> Francois.Courtault@gemalto.com
>> >:
>>
>> > Hello Romain,
>> >
>> > If you go to http://tomee.apache.org/ you will see, in that page,
>> > that, for Plume, it is written NOT Java EE6 Certified.
>> > So mistake in the tomee main page ?
>> >
>> > Best Regards.
>> >
>> > -----Original Message-----
>> > From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>> > Sent: lundi 28 décembre 2015 13:50
>> > To: users@tomee.apache.org
>> > Subject: Re: Question about Java EE certification TomEE and Plume
>> >
>> > Plume has been certified for ee6.
>> >
>> > Now as default provider i hope to stick to openjpa as much as possible
>> > to not break hundreds of applications.
>> > Le 28 déc. 2015 13:00, "Yann Blazart" <ya...@bycode.fr> a écrit
>> :
>> >
>> > > Hello, from my point of view, there's no problem.
>> > >
>> > > You can change the JPA implementation following your needs, put
>> > > Hibernate for example.
>> > >
>> > > I can garanty you that all my products running on webspehere and
>> > > weblogic was able to run in tomee. Sometimes some "proprietary"
>> > > config files to write or change, but this is part of Java EE specs.
>> > >
>> > > You can test TomEE 7.0.0-M1, it's nearly readed to be released, and
>> > > it's a fantastic EE 7 server !
>> > >
>> > > 2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
>> > > Francois.Courtault@gemalto.com>:
>> > >
>> > > > Hello everyone,
>> > > >
>> > > > TomEE is quite nice but one thing which annoys me is about
>> > > > certification using EclipseLink.
>> > > >
>> > > > Let me explain my concern:
>> > > > Some application servers like Weblogic and even Liberty, quite
>> > > > recently, uses EclipseLink as the JPA layer.
>> > > > But If I look at the TomEE docs, only the Plume delivery contains
>> > > > EclipseLink as the JPA layer, but this one is not Java EE 6
>> certified.
>> > > >
>> > > > Just want to know, if there are future plans in order to have
>> > > > JAX-RS delivery be Java EE 6 or Java EE 7 web profile certified
>> > > > but using EclipselInk (alternative to OpenJPA) as the JPA layer ?
>> > > > I ask this question because it will most probably ease our
>> > > > migration
>> > > from
>> > > > some commercial app vendors to TomEE.
>> > > >
>> > > > 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.
>> >
>> ________________________________
>> 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.
>>
>
>
Re: Question about Java EE certification TomEE and Plume
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Correct.
Even if we pass the WebProfile TCK for Plus and Plume we can't claim to be
certified.
There is no equivalent profile for TomEE Plus or Plume.
Also correct for JAX-RS.
Jean-Louis
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Mon, Jan 11, 2016 at 9:07 AM, COURTAULT Francois <
Francois.Courtault@gemalto.com> wrote:
> Hello Romain,
>
> To be sure to have understood you well: Plume is Java EE6 Web profile
> certified (pass the TCK tests) and not Java EE6 Full profile: right ?
> According to an answer I have received, it seems that the Plume JAX-RS
> part is also certified, right ?
>
> Best Regards.
>
> -----Original Message-----
> From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Sent: lundi 11 janvier 2016 09:02
> To: COURTAULT Francois
> Cc: users@tomee.apache.org
> Subject: Re: Question about Java EE certification TomEE and Plume
>
> Ok, I was not very clear - let's blame the phone for this one ;): we cant
> certify tomee+ cause we dont pass (= dont run) TCKs for > webprofile (JMS
> for instance). Plume being plus based it has the same constraint but we
> pass TCKs for the webprofile part - hope it is clearer.
>
>
> 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>
>
> 2016-01-11 8:58 GMT+01:00 COURTAULT Francois <
> Francois.Courtault@gemalto.com
> >:
>
> > Hello Romain,
> >
> > If you go to http://tomee.apache.org/ you will see, in that page,
> > that, for Plume, it is written NOT Java EE6 Certified.
> > So mistake in the tomee main page ?
> >
> > Best Regards.
> >
> > -----Original Message-----
> > From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> > Sent: lundi 28 décembre 2015 13:50
> > To: users@tomee.apache.org
> > Subject: Re: Question about Java EE certification TomEE and Plume
> >
> > Plume has been certified for ee6.
> >
> > Now as default provider i hope to stick to openjpa as much as possible
> > to not break hundreds of applications.
> > Le 28 déc. 2015 13:00, "Yann Blazart" <ya...@bycode.fr> a écrit :
> >
> > > Hello, from my point of view, there's no problem.
> > >
> > > You can change the JPA implementation following your needs, put
> > > Hibernate for example.
> > >
> > > I can garanty you that all my products running on webspehere and
> > > weblogic was able to run in tomee. Sometimes some "proprietary"
> > > config files to write or change, but this is part of Java EE specs.
> > >
> > > You can test TomEE 7.0.0-M1, it's nearly readed to be released, and
> > > it's a fantastic EE 7 server !
> > >
> > > 2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
> > > Francois.Courtault@gemalto.com>:
> > >
> > > > Hello everyone,
> > > >
> > > > TomEE is quite nice but one thing which annoys me is about
> > > > certification using EclipseLink.
> > > >
> > > > Let me explain my concern:
> > > > Some application servers like Weblogic and even Liberty, quite
> > > > recently, uses EclipseLink as the JPA layer.
> > > > But If I look at the TomEE docs, only the Plume delivery contains
> > > > EclipseLink as the JPA layer, but this one is not Java EE 6
> certified.
> > > >
> > > > Just want to know, if there are future plans in order to have
> > > > JAX-RS delivery be Java EE 6 or Java EE 7 web profile certified
> > > > but using EclipselInk (alternative to OpenJPA) as the JPA layer ?
> > > > I ask this question because it will most probably ease our
> > > > migration
> > > from
> > > > some commercial app vendors to TomEE.
> > > >
> > > > 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.
> >
> ________________________________
> 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.
>
Re: Question about Java EE certification TomEE and Plume
Posted by Romain Manni-Bucau <rm...@gmail.com>.
@Andy: we cant certified plume cause it brings more than web profile as
stated in this thread, that's why it is not and plus is not as well.
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>
2016-01-15 13:30 GMT+01:00 Andy Gumbrecht <ag...@tomitribe.com>:
> The ASF does have access to the EE6 TCK, and TomEE is always tested before
> a release.
>
> So when ASF TomEE states that a TomEE distribution is Webprofile certified
> then you can be sure that it is.
>
> @Devs If we run PLUME through the TCK then surely that distribution would
> at least be a 'both' Webprofile certified & other JSR compatible solution?
>
> Andy.
>
> On 14 January 2016 at 20:17, Gurkan Erdogdu <ge...@managecat.com>
> wrote:
>
> > To my knowledge, no, it is not the same. Actually without accessing TCK
> > suite ( and required to become a licensee of Oracle) , you can not use
> any
> > test and say that blabla server is compatible. Currently ASF is not
> > licensee of Oracle so no project in ASF can have access to TCK suite.
> >
> > Best
> > Gurkan
> >
> > Sent from my iPhone
> >
> > > On 14 Oca 2016, at 20:45, Mark Struberg <st...@yahoo.de> wrote:
> > >
> > > With other words, most of the other vendor packages are strictly seen
> > also not ‚certified‘ but only ‚compliant‘.
> > > Which makes them not bad - it’s just that the terms often get mixed up
> > by marketing (knowingly or not? I don’t know) and confuse users.
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > >> Am 11.01.2016 um 23:04 schrieb David Blevins <david.blevins@gmail.com
> >:
> > >>
> > >> Correct and to be clear, there are two distinct words
> > >>
> > >> - Certified = formal acknowledgement from Oracle for passing the Web
> > Profile or Full Profile TCK. Oracle offers no other form of
> certification.
> > >> - Compliant = passes the respective tests or conforms to the related
> > spec.
> > >>
> > >> In the majority of the thread the word “certified” is being used where
> > really “compliant” is more appropriate.
> > >>
> > >> Per certification rules, there are just the two profiles (Web and
> > Full). To be Web Profile certified by Oracle you have to implement and
> > pass the Web Profile technologies and ONLY the Web Profile technologies.
> > If you go one inch further and add JAX-WS, JMS or anything else, you
> cannot
> > call it “certified” even if you pass the respective tests.
> > >>
> > >> If we wanted to have a Java EE 6 Web Profile certified version of
> TomEE
> > 1.x that includes EclipseLink and Mojarra, we could do that, but we’d
> have
> > to remove JAX-RS, JAX-WS, and JMS from the box as none of those are in
> the
> > Web Profile.
> > >>
> > >>
> > >> --
> > >> David Blevins
> >
>
>
>
> --
> Andy Gumbrecht
> https://twitter.com/AndyGeeDe
> http://www.tomitribe.com
>
Re: Question about Java EE certification TomEE and Plume
Posted by Mark Struberg <st...@yahoo.de>.
ok, agree with that.
LieGrue,
strub
> Am 15.01.2016 um 13:45 schrieb Gurkan Erdogdu <ge...@managecat.com>:
>
> I mean EE 7 and above TCK
>
> Sent from my iPhone
>
>> On 15 Oca 2016, at 14:30, Andy Gumbrecht <ag...@tomitribe.com> wrote:
>>
>> The ASF does have access to the EE6 TCK, and TomEE is always tested before
>> a release.
>>
>> So when ASF TomEE states that a TomEE distribution is Webprofile certified
>> then you can be sure that it is.
>>
>> @Devs If we run PLUME through the TCK then surely that distribution would
>> at least be a 'both' Webprofile certified & other JSR compatible solution?
>>
>> Andy.
>>
>>> On 14 January 2016 at 20:17, Gurkan Erdogdu <ge...@managecat.com> wrote:
>>>
>>> To my knowledge, no, it is not the same. Actually without accessing TCK
>>> suite ( and required to become a licensee of Oracle) , you can not use any
>>> test and say that blabla server is compatible. Currently ASF is not
>>> licensee of Oracle so no project in ASF can have access to TCK suite.
>>>
>>> Best
>>> Gurkan
>>>
>>> Sent from my iPhone
>>>
>>>> On 14 Oca 2016, at 20:45, Mark Struberg <st...@yahoo.de> wrote:
>>>>
>>>> With other words, most of the other vendor packages are strictly seen
>>> also not ‚certified‘ but only ‚compliant‘.
>>>> Which makes them not bad - it’s just that the terms often get mixed up
>>> by marketing (knowingly or not? I don’t know) and confuse users.
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>> Am 11.01.2016 um 23:04 schrieb David Blevins <da...@gmail.com>:
>>>>>
>>>>> Correct and to be clear, there are two distinct words
>>>>>
>>>>> - Certified = formal acknowledgement from Oracle for passing the Web
>>> Profile or Full Profile TCK. Oracle offers no other form of certification.
>>>>> - Compliant = passes the respective tests or conforms to the related
>>> spec.
>>>>>
>>>>> In the majority of the thread the word “certified” is being used where
>>> really “compliant” is more appropriate.
>>>>>
>>>>> Per certification rules, there are just the two profiles (Web and
>>> Full). To be Web Profile certified by Oracle you have to implement and
>>> pass the Web Profile technologies and ONLY the Web Profile technologies.
>>> If you go one inch further and add JAX-WS, JMS or anything else, you cannot
>>> call it “certified” even if you pass the respective tests.
>>>>>
>>>>> If we wanted to have a Java EE 6 Web Profile certified version of TomEE
>>> 1.x that includes EclipseLink and Mojarra, we could do that, but we’d have
>>> to remove JAX-RS, JAX-WS, and JMS from the box as none of those are in the
>>> Web Profile.
>>>>>
>>>>>
>>>>> --
>>>>> David Blevins
>>
>>
>>
>> --
>> Andy Gumbrecht
>> https://twitter.com/AndyGeeDe
>> http://www.tomitribe.com
Re: Question about Java EE certification TomEE and Plume
Posted by Gurkan Erdogdu <ge...@managecat.com>.
I mean EE 7 and above TCK
Sent from my iPhone
> On 15 Oca 2016, at 14:30, Andy Gumbrecht <ag...@tomitribe.com> wrote:
>
> The ASF does have access to the EE6 TCK, and TomEE is always tested before
> a release.
>
> So when ASF TomEE states that a TomEE distribution is Webprofile certified
> then you can be sure that it is.
>
> @Devs If we run PLUME through the TCK then surely that distribution would
> at least be a 'both' Webprofile certified & other JSR compatible solution?
>
> Andy.
>
>> On 14 January 2016 at 20:17, Gurkan Erdogdu <ge...@managecat.com> wrote:
>>
>> To my knowledge, no, it is not the same. Actually without accessing TCK
>> suite ( and required to become a licensee of Oracle) , you can not use any
>> test and say that blabla server is compatible. Currently ASF is not
>> licensee of Oracle so no project in ASF can have access to TCK suite.
>>
>> Best
>> Gurkan
>>
>> Sent from my iPhone
>>
>>> On 14 Oca 2016, at 20:45, Mark Struberg <st...@yahoo.de> wrote:
>>>
>>> With other words, most of the other vendor packages are strictly seen
>> also not ‚certified‘ but only ‚compliant‘.
>>> Which makes them not bad - it’s just that the terms often get mixed up
>> by marketing (knowingly or not? I don’t know) and confuse users.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>> Am 11.01.2016 um 23:04 schrieb David Blevins <da...@gmail.com>:
>>>>
>>>> Correct and to be clear, there are two distinct words
>>>>
>>>> - Certified = formal acknowledgement from Oracle for passing the Web
>> Profile or Full Profile TCK. Oracle offers no other form of certification.
>>>> - Compliant = passes the respective tests or conforms to the related
>> spec.
>>>>
>>>> In the majority of the thread the word “certified” is being used where
>> really “compliant” is more appropriate.
>>>>
>>>> Per certification rules, there are just the two profiles (Web and
>> Full). To be Web Profile certified by Oracle you have to implement and
>> pass the Web Profile technologies and ONLY the Web Profile technologies.
>> If you go one inch further and add JAX-WS, JMS or anything else, you cannot
>> call it “certified” even if you pass the respective tests.
>>>>
>>>> If we wanted to have a Java EE 6 Web Profile certified version of TomEE
>> 1.x that includes EclipseLink and Mojarra, we could do that, but we’d have
>> to remove JAX-RS, JAX-WS, and JMS from the box as none of those are in the
>> Web Profile.
>>>>
>>>>
>>>> --
>>>> David Blevins
>
>
>
> --
> Andy Gumbrecht
> https://twitter.com/AndyGeeDe
> http://www.tomitribe.com
Re: Question about Java EE certification TomEE and Plume
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
The ASF does have access to the EE6 TCK, and TomEE is always tested before
a release.
So when ASF TomEE states that a TomEE distribution is Webprofile certified
then you can be sure that it is.
@Devs If we run PLUME through the TCK then surely that distribution would
at least be a 'both' Webprofile certified & other JSR compatible solution?
Andy.
On 14 January 2016 at 20:17, Gurkan Erdogdu <ge...@managecat.com> wrote:
> To my knowledge, no, it is not the same. Actually without accessing TCK
> suite ( and required to become a licensee of Oracle) , you can not use any
> test and say that blabla server is compatible. Currently ASF is not
> licensee of Oracle so no project in ASF can have access to TCK suite.
>
> Best
> Gurkan
>
> Sent from my iPhone
>
> > On 14 Oca 2016, at 20:45, Mark Struberg <st...@yahoo.de> wrote:
> >
> > With other words, most of the other vendor packages are strictly seen
> also not ‚certified‘ but only ‚compliant‘.
> > Which makes them not bad - it’s just that the terms often get mixed up
> by marketing (knowingly or not? I don’t know) and confuse users.
> >
> > LieGrue,
> > strub
> >
> >
> >> Am 11.01.2016 um 23:04 schrieb David Blevins <da...@gmail.com>:
> >>
> >> Correct and to be clear, there are two distinct words
> >>
> >> - Certified = formal acknowledgement from Oracle for passing the Web
> Profile or Full Profile TCK. Oracle offers no other form of certification.
> >> - Compliant = passes the respective tests or conforms to the related
> spec.
> >>
> >> In the majority of the thread the word “certified” is being used where
> really “compliant” is more appropriate.
> >>
> >> Per certification rules, there are just the two profiles (Web and
> Full). To be Web Profile certified by Oracle you have to implement and
> pass the Web Profile technologies and ONLY the Web Profile technologies.
> If you go one inch further and add JAX-WS, JMS or anything else, you cannot
> call it “certified” even if you pass the respective tests.
> >>
> >> If we wanted to have a Java EE 6 Web Profile certified version of TomEE
> 1.x that includes EclipseLink and Mojarra, we could do that, but we’d have
> to remove JAX-RS, JAX-WS, and JMS from the box as none of those are in the
> Web Profile.
> >>
> >>
> >> --
> >> David Blevins
>
--
Andy Gumbrecht
https://twitter.com/AndyGeeDe
http://www.tomitribe.com
Re: Question about Java EE certification TomEE and Plume
Posted by Mark Struberg <st...@yahoo.de>.
> Currently ASF is not licensee of Oracle so no project in ASF can have access to TCK suite.
That’s simply FUD and not true. ASF has not licensed the EE7 tck because Oracle did breach the contract.
But the ASF has a EE6 TCK license.
LieGrue,
strub
> Am 14.01.2016 um 20:17 schrieb Gurkan Erdogdu <ge...@managecat.com>:
>
> To my knowledge, no, it is not the same. Actually without accessing TCK suite ( and required to become a licensee of Oracle) , you can not use any test and say that blabla server is compatible. Currently ASF is not licensee of Oracle so no project in ASF can have access to TCK suite.
>
> Best
> Gurkan
>
> Sent from my iPhone
>
>> On 14 Oca 2016, at 20:45, Mark Struberg <st...@yahoo.de> wrote:
>>
>> With other words, most of the other vendor packages are strictly seen also not ‚certified‘ but only ‚compliant‘.
>> Which makes them not bad - it’s just that the terms often get mixed up by marketing (knowingly or not? I don’t know) and confuse users.
>>
>> LieGrue,
>> strub
>>
>>
>>> Am 11.01.2016 um 23:04 schrieb David Blevins <da...@gmail.com>:
>>>
>>> Correct and to be clear, there are two distinct words
>>>
>>> - Certified = formal acknowledgement from Oracle for passing the Web Profile or Full Profile TCK. Oracle offers no other form of certification.
>>> - Compliant = passes the respective tests or conforms to the related spec.
>>>
>>> In the majority of the thread the word “certified” is being used where really “compliant” is more appropriate.
>>>
>>> Per certification rules, there are just the two profiles (Web and Full). To be Web Profile certified by Oracle you have to implement and pass the Web Profile technologies and ONLY the Web Profile technologies. If you go one inch further and add JAX-WS, JMS or anything else, you cannot call it “certified” even if you pass the respective tests.
>>>
>>> If we wanted to have a Java EE 6 Web Profile certified version of TomEE 1.x that includes EclipseLink and Mojarra, we could do that, but we’d have to remove JAX-RS, JAX-WS, and JMS from the box as none of those are in the Web Profile.
>>>
>>>
>>> --
>>> David Blevins
Re: Question about Java EE certification TomEE and Plume
Posted by Gurkan Erdogdu <ge...@managecat.com>.
To my knowledge, no, it is not the same. Actually without accessing TCK suite ( and required to become a licensee of Oracle) , you can not use any test and say that blabla server is compatible. Currently ASF is not licensee of Oracle so no project in ASF can have access to TCK suite.
Best
Gurkan
Sent from my iPhone
> On 14 Oca 2016, at 20:45, Mark Struberg <st...@yahoo.de> wrote:
>
> With other words, most of the other vendor packages are strictly seen also not ‚certified‘ but only ‚compliant‘.
> Which makes them not bad - it’s just that the terms often get mixed up by marketing (knowingly or not? I don’t know) and confuse users.
>
> LieGrue,
> strub
>
>
>> Am 11.01.2016 um 23:04 schrieb David Blevins <da...@gmail.com>:
>>
>> Correct and to be clear, there are two distinct words
>>
>> - Certified = formal acknowledgement from Oracle for passing the Web Profile or Full Profile TCK. Oracle offers no other form of certification.
>> - Compliant = passes the respective tests or conforms to the related spec.
>>
>> In the majority of the thread the word “certified” is being used where really “compliant” is more appropriate.
>>
>> Per certification rules, there are just the two profiles (Web and Full). To be Web Profile certified by Oracle you have to implement and pass the Web Profile technologies and ONLY the Web Profile technologies. If you go one inch further and add JAX-WS, JMS or anything else, you cannot call it “certified” even if you pass the respective tests.
>>
>> If we wanted to have a Java EE 6 Web Profile certified version of TomEE 1.x that includes EclipseLink and Mojarra, we could do that, but we’d have to remove JAX-RS, JAX-WS, and JMS from the box as none of those are in the Web Profile.
>>
>>
>> --
>> David Blevins
Re: Question about Java EE certification TomEE and Plume
Posted by Mark Struberg <st...@yahoo.de>.
With other words, most of the other vendor packages are strictly seen also not ‚certified‘ but only ‚compliant‘.
Which makes them not bad - it’s just that the terms often get mixed up by marketing (knowingly or not? I don’t know) and confuse users.
LieGrue,
strub
> Am 11.01.2016 um 23:04 schrieb David Blevins <da...@gmail.com>:
>
> Correct and to be clear, there are two distinct words
>
> - Certified = formal acknowledgement from Oracle for passing the Web Profile or Full Profile TCK. Oracle offers no other form of certification.
> - Compliant = passes the respective tests or conforms to the related spec.
>
> In the majority of the thread the word “certified” is being used where really “compliant” is more appropriate.
>
> Per certification rules, there are just the two profiles (Web and Full). To be Web Profile certified by Oracle you have to implement and pass the Web Profile technologies and ONLY the Web Profile technologies. If you go one inch further and add JAX-WS, JMS or anything else, you cannot call it “certified” even if you pass the respective tests.
>
> If we wanted to have a Java EE 6 Web Profile certified version of TomEE 1.x that includes EclipseLink and Mojarra, we could do that, but we’d have to remove JAX-RS, JAX-WS, and JMS from the box as none of those are in the Web Profile.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>> On Jan 11, 2016, at 12:07 AM, COURTAULT Francois <Fr...@gemalto.com> wrote:
>>
>> Hello Romain,
>>
>> To be sure to have understood you well: Plume is Java EE6 Web profile certified (pass the TCK tests) and not Java EE6 Full profile: right ?
>> According to an answer I have received, it seems that the Plume JAX-RS part is also certified, right ?
>>
>> Best Regards.
>>
>> -----Original Message-----
>> From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>> Sent: lundi 11 janvier 2016 09:02
>> To: COURTAULT Francois
>> Cc: users@tomee.apache.org
>> Subject: Re: Question about Java EE certification TomEE and Plume
>>
>> Ok, I was not very clear - let's blame the phone for this one ;): we cant certify tomee+ cause we dont pass (= dont run) TCKs for > webprofile (JMS for instance). Plume being plus based it has the same constraint but we pass TCKs for the webprofile part - hope it is clearer.
>>
>>
>> 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>
>>
>> 2016-01-11 8:58 GMT+01:00 COURTAULT Francois <Francois.Courtault@gemalto.com
>>> :
>>
>>> Hello Romain,
>>>
>>> If you go to http://tomee.apache.org/ you will see, in that page,
>>> that, for Plume, it is written NOT Java EE6 Certified.
>>> So mistake in the tomee main page ?
>>>
>>> Best Regards.
>>>
>>> -----Original Message-----
>>> From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>>> Sent: lundi 28 décembre 2015 13:50
>>> To: users@tomee.apache.org
>>> Subject: Re: Question about Java EE certification TomEE and Plume
>>>
>>> Plume has been certified for ee6.
>>>
>>> Now as default provider i hope to stick to openjpa as much as possible
>>> to not break hundreds of applications.
>>> Le 28 déc. 2015 13:00, "Yann Blazart" <ya...@bycode.fr> a écrit :
>>>
>>>> Hello, from my point of view, there's no problem.
>>>>
>>>> You can change the JPA implementation following your needs, put
>>>> Hibernate for example.
>>>>
>>>> I can garanty you that all my products running on webspehere and
>>>> weblogic was able to run in tomee. Sometimes some "proprietary"
>>>> config files to write or change, but this is part of Java EE specs.
>>>>
>>>> You can test TomEE 7.0.0-M1, it's nearly readed to be released, and
>>>> it's a fantastic EE 7 server !
>>>>
>>>> 2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
>>>> Francois.Courtault@gemalto.com>:
>>>>
>>>>> Hello everyone,
>>>>>
>>>>> TomEE is quite nice but one thing which annoys me is about
>>>>> certification using EclipseLink.
>>>>>
>>>>> Let me explain my concern:
>>>>> Some application servers like Weblogic and even Liberty, quite
>>>>> recently, uses EclipseLink as the JPA layer.
>>>>> But If I look at the TomEE docs, only the Plume delivery contains
>>>>> EclipseLink as the JPA layer, but this one is not Java EE 6 certified.
>>>>>
>>>>> Just want to know, if there are future plans in order to have
>>>>> JAX-RS delivery be Java EE 6 or Java EE 7 web profile certified
>>>>> but using EclipselInk (alternative to OpenJPA) as the JPA layer ?
>>>>> I ask this question because it will most probably ease our
>>>>> migration
>>>> from
>>>>> some commercial app vendors to TomEE.
>>>>>
>>>>> 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.
>>>
>> ________________________________
>> 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.
>
Re: Question about Java EE certification TomEE and Plume
Posted by David Blevins <da...@gmail.com>.
Correct and to be clear, there are two distinct words
- Certified = formal acknowledgement from Oracle for passing the Web Profile or Full Profile TCK. Oracle offers no other form of certification.
- Compliant = passes the respective tests or conforms to the related spec.
In the majority of the thread the word “certified” is being used where really “compliant” is more appropriate.
Per certification rules, there are just the two profiles (Web and Full). To be Web Profile certified by Oracle you have to implement and pass the Web Profile technologies and ONLY the Web Profile technologies. If you go one inch further and add JAX-WS, JMS or anything else, you cannot call it “certified” even if you pass the respective tests.
If we wanted to have a Java EE 6 Web Profile certified version of TomEE 1.x that includes EclipseLink and Mojarra, we could do that, but we’d have to remove JAX-RS, JAX-WS, and JMS from the box as none of those are in the Web Profile.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
> On Jan 11, 2016, at 12:07 AM, COURTAULT Francois <Fr...@gemalto.com> wrote:
>
> Hello Romain,
>
> To be sure to have understood you well: Plume is Java EE6 Web profile certified (pass the TCK tests) and not Java EE6 Full profile: right ?
> According to an answer I have received, it seems that the Plume JAX-RS part is also certified, right ?
>
> Best Regards.
>
> -----Original Message-----
> From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Sent: lundi 11 janvier 2016 09:02
> To: COURTAULT Francois
> Cc: users@tomee.apache.org
> Subject: Re: Question about Java EE certification TomEE and Plume
>
> Ok, I was not very clear - let's blame the phone for this one ;): we cant certify tomee+ cause we dont pass (= dont run) TCKs for > webprofile (JMS for instance). Plume being plus based it has the same constraint but we pass TCKs for the webprofile part - hope it is clearer.
>
>
> 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>
>
> 2016-01-11 8:58 GMT+01:00 COURTAULT Francois <Francois.Courtault@gemalto.com
>> :
>
>> Hello Romain,
>>
>> If you go to http://tomee.apache.org/ you will see, in that page,
>> that, for Plume, it is written NOT Java EE6 Certified.
>> So mistake in the tomee main page ?
>>
>> Best Regards.
>>
>> -----Original Message-----
>> From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
>> Sent: lundi 28 décembre 2015 13:50
>> To: users@tomee.apache.org
>> Subject: Re: Question about Java EE certification TomEE and Plume
>>
>> Plume has been certified for ee6.
>>
>> Now as default provider i hope to stick to openjpa as much as possible
>> to not break hundreds of applications.
>> Le 28 déc. 2015 13:00, "Yann Blazart" <ya...@bycode.fr> a écrit :
>>
>>> Hello, from my point of view, there's no problem.
>>>
>>> You can change the JPA implementation following your needs, put
>>> Hibernate for example.
>>>
>>> I can garanty you that all my products running on webspehere and
>>> weblogic was able to run in tomee. Sometimes some "proprietary"
>>> config files to write or change, but this is part of Java EE specs.
>>>
>>> You can test TomEE 7.0.0-M1, it's nearly readed to be released, and
>>> it's a fantastic EE 7 server !
>>>
>>> 2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
>>> Francois.Courtault@gemalto.com>:
>>>
>>>> Hello everyone,
>>>>
>>>> TomEE is quite nice but one thing which annoys me is about
>>>> certification using EclipseLink.
>>>>
>>>> Let me explain my concern:
>>>> Some application servers like Weblogic and even Liberty, quite
>>>> recently, uses EclipseLink as the JPA layer.
>>>> But If I look at the TomEE docs, only the Plume delivery contains
>>>> EclipseLink as the JPA layer, but this one is not Java EE 6 certified.
>>>>
>>>> Just want to know, if there are future plans in order to have
>>>> JAX-RS delivery be Java EE 6 or Java EE 7 web profile certified
>>>> but using EclipselInk (alternative to OpenJPA) as the JPA layer ?
>>>> I ask this question because it will most probably ease our
>>>> migration
>>> from
>>>> some commercial app vendors to TomEE.
>>>>
>>>> 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.
>>
> ________________________________
> 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.
RE: Question about Java EE certification TomEE and Plume
Posted by COURTAULT Francois <Fr...@gemalto.com>.
Hello Romain,
To be sure to have understood you well: Plume is Java EE6 Web profile certified (pass the TCK tests) and not Java EE6 Full profile: right ?
According to an answer I have received, it seems that the Plume JAX-RS part is also certified, right ?
Best Regards.
-----Original Message-----
From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
Sent: lundi 11 janvier 2016 09:02
To: COURTAULT Francois
Cc: users@tomee.apache.org
Subject: Re: Question about Java EE certification TomEE and Plume
Ok, I was not very clear - let's blame the phone for this one ;): we cant certify tomee+ cause we dont pass (= dont run) TCKs for > webprofile (JMS for instance). Plume being plus based it has the same constraint but we pass TCKs for the webprofile part - hope it is clearer.
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>
2016-01-11 8:58 GMT+01:00 COURTAULT Francois <Francois.Courtault@gemalto.com
>:
> Hello Romain,
>
> If you go to http://tomee.apache.org/ you will see, in that page,
> that, for Plume, it is written NOT Java EE6 Certified.
> So mistake in the tomee main page ?
>
> Best Regards.
>
> -----Original Message-----
> From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Sent: lundi 28 décembre 2015 13:50
> To: users@tomee.apache.org
> Subject: Re: Question about Java EE certification TomEE and Plume
>
> Plume has been certified for ee6.
>
> Now as default provider i hope to stick to openjpa as much as possible
> to not break hundreds of applications.
> Le 28 déc. 2015 13:00, "Yann Blazart" <ya...@bycode.fr> a écrit :
>
> > Hello, from my point of view, there's no problem.
> >
> > You can change the JPA implementation following your needs, put
> > Hibernate for example.
> >
> > I can garanty you that all my products running on webspehere and
> > weblogic was able to run in tomee. Sometimes some "proprietary"
> > config files to write or change, but this is part of Java EE specs.
> >
> > You can test TomEE 7.0.0-M1, it's nearly readed to be released, and
> > it's a fantastic EE 7 server !
> >
> > 2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
> > Francois.Courtault@gemalto.com>:
> >
> > > Hello everyone,
> > >
> > > TomEE is quite nice but one thing which annoys me is about
> > > certification using EclipseLink.
> > >
> > > Let me explain my concern:
> > > Some application servers like Weblogic and even Liberty, quite
> > > recently, uses EclipseLink as the JPA layer.
> > > But If I look at the TomEE docs, only the Plume delivery contains
> > > EclipseLink as the JPA layer, but this one is not Java EE 6 certified.
> > >
> > > Just want to know, if there are future plans in order to have
> > > JAX-RS delivery be Java EE 6 or Java EE 7 web profile certified
> > > but using EclipselInk (alternative to OpenJPA) as the JPA layer ?
> > > I ask this question because it will most probably ease our
> > > migration
> > from
> > > some commercial app vendors to TomEE.
> > >
> > > 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.
>
________________________________
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.
Re: Question about Java EE certification TomEE and Plume
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Ok, I was not very clear - let's blame the phone for this one ;): we cant
certify tomee+ cause we dont pass (= dont run) TCKs for > webprofile (JMS
for instance). Plume being plus based it has the same constraint but we
pass TCKs for the webprofile part - hope it is clearer.
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>
2016-01-11 8:58 GMT+01:00 COURTAULT Francois <Francois.Courtault@gemalto.com
>:
> Hello Romain,
>
> If you go to http://tomee.apache.org/ you will see, in that page, that,
> for Plume, it is written NOT Java EE6 Certified.
> So mistake in the tomee main page ?
>
> Best Regards.
>
> -----Original Message-----
> From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Sent: lundi 28 décembre 2015 13:50
> To: users@tomee.apache.org
> Subject: Re: Question about Java EE certification TomEE and Plume
>
> Plume has been certified for ee6.
>
> Now as default provider i hope to stick to openjpa as much as possible to
> not break hundreds of applications.
> Le 28 déc. 2015 13:00, "Yann Blazart" <ya...@bycode.fr> a écrit :
>
> > Hello, from my point of view, there's no problem.
> >
> > You can change the JPA implementation following your needs, put
> > Hibernate for example.
> >
> > I can garanty you that all my products running on webspehere and
> > weblogic was able to run in tomee. Sometimes some "proprietary" config
> > files to write or change, but this is part of Java EE specs.
> >
> > You can test TomEE 7.0.0-M1, it's nearly readed to be released, and
> > it's a fantastic EE 7 server !
> >
> > 2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
> > Francois.Courtault@gemalto.com>:
> >
> > > Hello everyone,
> > >
> > > TomEE is quite nice but one thing which annoys me is about
> > > certification using EclipseLink.
> > >
> > > Let me explain my concern:
> > > Some application servers like Weblogic and even Liberty, quite
> > > recently, uses EclipseLink as the JPA layer.
> > > But If I look at the TomEE docs, only the Plume delivery contains
> > > EclipseLink as the JPA layer, but this one is not Java EE 6 certified.
> > >
> > > Just want to know, if there are future plans in order to have JAX-RS
> > > delivery be Java EE 6 or Java EE 7 web profile certified but using
> > > EclipselInk (alternative to OpenJPA) as the JPA layer ?
> > > I ask this question because it will most probably ease our
> > > migration
> > from
> > > some commercial app vendors to TomEE.
> > >
> > > 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.
>
Re: Question about Java EE certification TomEE and Plume
Posted by Gurkan Erdogdu <ge...@managecat.com>.
Hi Francois
Only Java EE 6 web profile had been certified in TomEE which includes WebProfile + JAX-RS.
Regards.
Gurkan Erdogdu
Founder, ManageCat
p. +1 (909) - 366 – 9337
a. 340 S Lemon Ave #7996 Walnut, CA 91789
w. http://managecat.com
e gerdogdu@managecat.com
> On 11 Jan 2016, at 09:58, COURTAULT Francois <Fr...@gemalto.com> wrote:
>
> Hello Romain,
>
> If you go to http://tomee.apache.org/ you will see, in that page, that, for Plume, it is written NOT Java EE6 Certified.
> So mistake in the tomee main page ?
>
> Best Regards.
>
> -----Original Message-----
> From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
> Sent: lundi 28 décembre 2015 13:50
> To: users@tomee.apache.org
> Subject: Re: Question about Java EE certification TomEE and Plume
>
> Plume has been certified for ee6.
>
> Now as default provider i hope to stick to openjpa as much as possible to not break hundreds of applications.
> Le 28 déc. 2015 13:00, "Yann Blazart" <ya...@bycode.fr> a écrit :
>
>> Hello, from my point of view, there's no problem.
>>
>> You can change the JPA implementation following your needs, put
>> Hibernate for example.
>>
>> I can garanty you that all my products running on webspehere and
>> weblogic was able to run in tomee. Sometimes some "proprietary" config
>> files to write or change, but this is part of Java EE specs.
>>
>> You can test TomEE 7.0.0-M1, it's nearly readed to be released, and
>> it's a fantastic EE 7 server !
>>
>> 2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
>> Francois.Courtault@gemalto.com>:
>>
>>> Hello everyone,
>>>
>>> TomEE is quite nice but one thing which annoys me is about
>>> certification using EclipseLink.
>>>
>>> Let me explain my concern:
>>> Some application servers like Weblogic and even Liberty, quite
>>> recently, uses EclipseLink as the JPA layer.
>>> But If I look at the TomEE docs, only the Plume delivery contains
>>> EclipseLink as the JPA layer, but this one is not Java EE 6 certified.
>>>
>>> Just want to know, if there are future plans in order to have JAX-RS
>>> delivery be Java EE 6 or Java EE 7 web profile certified but using
>>> EclipselInk (alternative to OpenJPA) as the JPA layer ?
>>> I ask this question because it will most probably ease our
>>> migration
>> from
>>> some commercial app vendors to TomEE.
>>>
>>> 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.
RE: Question about Java EE certification TomEE and Plume
Posted by COURTAULT Francois <Fr...@gemalto.com>.
Hello Romain,
If you go to http://tomee.apache.org/ you will see, in that page, that, for Plume, it is written NOT Java EE6 Certified.
So mistake in the tomee main page ?
Best Regards.
-----Original Message-----
From: Romain Manni-Bucau [mailto:rmannibucau@gmail.com]
Sent: lundi 28 décembre 2015 13:50
To: users@tomee.apache.org
Subject: Re: Question about Java EE certification TomEE and Plume
Plume has been certified for ee6.
Now as default provider i hope to stick to openjpa as much as possible to not break hundreds of applications.
Le 28 déc. 2015 13:00, "Yann Blazart" <ya...@bycode.fr> a écrit :
> Hello, from my point of view, there's no problem.
>
> You can change the JPA implementation following your needs, put
> Hibernate for example.
>
> I can garanty you that all my products running on webspehere and
> weblogic was able to run in tomee. Sometimes some "proprietary" config
> files to write or change, but this is part of Java EE specs.
>
> You can test TomEE 7.0.0-M1, it's nearly readed to be released, and
> it's a fantastic EE 7 server !
>
> 2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
> Francois.Courtault@gemalto.com>:
>
> > Hello everyone,
> >
> > TomEE is quite nice but one thing which annoys me is about
> > certification using EclipseLink.
> >
> > Let me explain my concern:
> > Some application servers like Weblogic and even Liberty, quite
> > recently, uses EclipseLink as the JPA layer.
> > But If I look at the TomEE docs, only the Plume delivery contains
> > EclipseLink as the JPA layer, but this one is not Java EE 6 certified.
> >
> > Just want to know, if there are future plans in order to have JAX-RS
> > delivery be Java EE 6 or Java EE 7 web profile certified but using
> > EclipselInk (alternative to OpenJPA) as the JPA layer ?
> > I ask this question because it will most probably ease our
> > migration
> from
> > some commercial app vendors to TomEE.
> >
> > 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.
Re: Question about Java EE certification TomEE and Plume
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Plume has been certified for ee6.
Now as default provider i hope to stick to openjpa as much as possible to
not break hundreds of applications.
Le 28 déc. 2015 13:00, "Yann Blazart" <ya...@bycode.fr> a écrit :
> Hello, from my point of view, there's no problem.
>
> You can change the JPA implementation following your needs, put Hibernate
> for example.
>
> I can garanty you that all my products running on webspehere and weblogic
> was able to run in tomee. Sometimes some "proprietary" config files to
> write or change, but this is part of Java EE specs.
>
> You can test TomEE 7.0.0-M1, it's nearly readed to be released, and it's a
> fantastic EE 7 server !
>
> 2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
> Francois.Courtault@gemalto.com>:
>
> > Hello everyone,
> >
> > TomEE is quite nice but one thing which annoys me is about certification
> > using EclipseLink.
> >
> > Let me explain my concern:
> > Some application servers like Weblogic and even Liberty, quite recently,
> > uses EclipseLink as the JPA layer.
> > But If I look at the TomEE docs, only the Plume delivery contains
> > EclipseLink as the JPA layer, but this one is not Java EE 6 certified.
> >
> > Just want to know, if there are future plans in order to have JAX-RS
> > delivery be Java EE 6 or Java EE 7 web profile certified but using
> > EclipselInk (alternative to OpenJPA) as the JPA layer ?
> > I ask this question because it will most probably ease our migration
> from
> > some commercial app vendors to TomEE.
> >
> > 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.
> >
>
Re: Question about Java EE certification TomEE and Plume
Posted by Yann Blazart <ya...@bycode.fr>.
Hello, from my point of view, there's no problem.
You can change the JPA implementation following your needs, put Hibernate
for example.
I can garanty you that all my products running on webspehere and weblogic
was able to run in tomee. Sometimes some "proprietary" config files to
write or change, but this is part of Java EE specs.
You can test TomEE 7.0.0-M1, it's nearly readed to be released, and it's a
fantastic EE 7 server !
2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
Francois.Courtault@gemalto.com>:
> Hello everyone,
>
> TomEE is quite nice but one thing which annoys me is about certification
> using EclipseLink.
>
> Let me explain my concern:
> Some application servers like Weblogic and even Liberty, quite recently,
> uses EclipseLink as the JPA layer.
> But If I look at the TomEE docs, only the Plume delivery contains
> EclipseLink as the JPA layer, but this one is not Java EE 6 certified.
>
> Just want to know, if there are future plans in order to have JAX-RS
> delivery be Java EE 6 or Java EE 7 web profile certified but using
> EclipselInk (alternative to OpenJPA) as the JPA layer ?
> I ask this question because it will most probably ease our migration from
> some commercial app vendors to TomEE.
>
> 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.
>