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 > <[email protected]> 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:[email protected]] > Sent: lundi 11 janvier 2016 09:02 > To: COURTAULT Francois > Cc: [email protected] > 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 <[email protected] >> : > >> 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:[email protected]] >> Sent: lundi 28 décembre 2015 13:50 >> To: [email protected] >> 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" <[email protected]> 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 < >>> [email protected]>: >>> >>>> 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.
