You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by James Green <ja...@gmail.com> on 2014/06/02 13:04:32 UTC
Re: Roadmap (CXF 3)
So are Apache paying Oracle to get certified?
On 29 May 2014 17:12, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Actually that's a bit worse. TomEE is certified by Oracle as JavaEE
> compliant. We can't be JavaEE 7 certified yet but if we upgrade any spec
> we'll not be JavaEE 6 certified anymore cause API signatures are checked in
> the certification process.
>
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-05-29 15:31 GMT+02:00 Thiago Veronezi <th...@veronezi.org>:
>
> > Hi,
> >
> > They can be used. TomEE needs to be compiled on with JDK 6 tough. Usually
> > Java EE 7 features rely on the JDK 7 features. These things don't work on
> > JDK 6. In order to be certified Java EE 6, we need to support JDK 6. That
> > means that the TomEE source code uses no Java 7 (or Java 8) goodness yet.
> >
> > []s,
> > Thiago.
> >
> >
> >
> > On Thu, May 29, 2014 at 9:10 AM, James Green <james.mk.green@gmail.com
> > >wrote:
> >
> > > Why is it that something EE 7 compliant cannot be used in something EE
> 6
> > > compliant then?
> > >
> > >
> > > On 28 May 2014 12:32, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
> > >
> > > > Hi
> > > >
> > > > when we'll target JavaEE 7 so end of summer surely
> > > >
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > Twitter: @rmannibucau
> > > > Blog: http://rmannibucau.wordpress.com/
> > > > LinkedIn: http://fr.linkedin.com/in/rmannibucau
> > > > Github: https://github.com/rmannibucau
> > > >
> > > >
> > > > 2014-05-28 12:59 GMT+02:00 James Green <ja...@gmail.com>:
> > > >
> > > > > The JIRA Roadmap page appears inaccurate at best so I have to ask
> > here
> > > -
> > > > > what plans do you have to ship a TomEE with CXF 3.0 included?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > James
> > > > >
> > > >
> > >
> >
>
Re: Roadmap (CXF 3)
Posted by agumbrecht <ag...@tomitribe.com>.
OK, not to upset people and count chickens before they hatch - Apache TomEE
2.0.0 will be JEE7 compatible.
Andy.
-----
--
Andy Gumbrecht
http://www.tomitribe.com
agumbrecht@tomitribe.com
https://twitter.com/AndyGeeDe
TomEE treibt Tomitribe ! | http://tomee.apache.org
--
View this message in context: http://openejb.979440.n4.nabble.com/Roadmap-CXF-3-tp4669702p4669806.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Roadmap (CXF 3)
Posted by Niki Dokovski <ni...@gmail.com>.
—
Sent from Mailbox
On Tue, Jun 3, 2014 at 01:39 PM, Andy Gumbrecht<ag...@tomitribe.com>, wrote:
Hi James,
Oracle communities define the profile with a reference implementation,
which is then tested using a Technology Compatibility Kit (TCK). This
TCK is then offered under license and governed by regulations defined here:
http://www.oracle.com/technetwork/java/index-137188.html
The license includes non-disclosure policies, but you can be assured
when something claims to be officially certified under the TCK it has
met all of the defined requirements.
This will also be the case for JEE 7. We are really close to last JEE 6
release of Apache TomEE 1.7.0, after which we will concentrate on
defining the JEE 7 roadmap in as much detail as possible for Apache
TomEE 2.0.0.
As most of the work is done by volunteers or companies dedicating their
own time to the project I guess that it us paying Apache 'in kind' to
get a certified open source version.
Apache TomEE 2.0.0 will be JEE 7 certified and include as many up to
date technologies as possible on that path - That will include the most
recent CXF version at the time.
Awesome !
Please post the roadmap of TomEE 2.x. when available.
Andy.
On 02/06/2014 13:04, James Green wrote:
> So are Apache paying Oracle to get certified?
>
>
> On 29 May 2014 17:12, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
>> Actually that's a bit worse. TomEE is certified by Oracle as JavaEE
>> compliant. We can't be JavaEE 7 certified yet but if we upgrade any spec
>> we'll not be JavaEE 6 certified anymore cause API signatures are checked in
>> the certification process.
>>
>>
>>
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>> 2014-05-29 15:31 GMT+02:00 Thiago Veronezi <th...@veronezi.org>:
>>
>>> Hi,
>>>
>>> They can be used. TomEE needs to be compiled on with JDK 6 tough. Usually
>>> Java EE 7 features rely on the JDK 7 features. These things don't work on
>>> JDK 6. In order to be certified Java EE 6, we need to support JDK 6. That
>>> means that the TomEE source code uses no Java 7 (or Java 8) goodness yet.
>>>
>>> []s,
>>> Thiago.
>>>
>>>
>>>
>>> On Thu, May 29, 2014 at 9:10 AM, James Green <james.mk.green@gmail.com
>>>> wrote:
>>>> Why is it that something EE 7 compliant cannot be used in something EE
>> 6
>>>> compliant then?
>>>>
>>>>
>>>> On 28 May 2014 12:32, Romain Manni-Bucau <rm...@gmail.com>
>> wrote:
>>>>> Hi
>>>>>
>>>>> when we'll target JavaEE 7 so end of summer surely
>>>>>
>>>>>
>>>>>
>>>>> Romain Manni-Bucau
>>>>> Twitter: @rmannibucau
>>>>> Blog: http://rmannibucau.wordpress.com/
>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>> Github: https://github.com/rmannibucau
>>>>>
>>>>>
>>>>> 2014-05-28 12:59 GMT+02:00 James Green <ja...@gmail.com>:
>>>>>
>>>>>> The JIRA Roadmap page appears inaccurate at best so I have to ask
>>> here
>>>> -
>>>>>> what plans do you have to ship a TomEE with CXF 3.0 included?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> James
>>>>>>
--
Andy Gumbrecht
http://www.tomitribe.com
agumbrecht@tomitribe.com
https://twitter.com/AndyGeeDe
TomEE treibt Tomitribe! | http://tomee.apache.org
Re: Roadmap (CXF 3)
Posted by Romain Manni-Bucau <rm...@gmail.com>.
No you can only be EE 6 or EE 7 at a time. But tomee+ can be anything
;). That said upgrades will come very soon. We should just take care
to not upgrade everything at the same time ;)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-04 16:09 GMT+02:00 James Green <ja...@gmail.com>:
> I was reading Romain's email about the situation being worse as
> re-certification would be required as the interfaces will have changed. I
> read that as meaning that each time the interfaces changed a costly
> re-certification process would be required.
>
> Can something not be JEE-6 and JEE-7 compliant at the same time then? I was
> hoping by upgrading TomEE to CXF 3 it would retain EE-6 compliance and gain
> an EE-7 component. Re-certification with an open TCK ought be free..?
>
>
> On 3 June 2014 11:39, Andy Gumbrecht <ag...@tomitribe.com> wrote:
>
>> Hi James,
>>
>> Oracle communities define the profile with a reference implementation,
>> which is then tested using a Technology Compatibility Kit (TCK). This TCK
>> is then offered under license and governed by regulations defined here:
>>
>> http://www.oracle.com/technetwork/java/index-137188.html
>>
>> The license includes non-disclosure policies, but you can be assured when
>> something claims to be officially certified under the TCK it has met all of
>> the defined requirements.
>>
>> This will also be the case for JEE 7. We are really close to last JEE 6
>> release of Apache TomEE 1.7.0, after which we will concentrate on defining
>> the JEE 7 roadmap in as much detail as possible for Apache TomEE 2.0.0.
>>
>> As most of the work is done by volunteers or companies dedicating their
>> own time to the project I guess that it us paying Apache 'in kind' to get a
>> certified open source version.
>>
>> Apache TomEE 2.0.0 will be JEE 7 certified and include as many up to date
>> technologies as possible on that path - That will include the most recent
>> CXF version at the time.
>>
>> Andy.
>>
>>
>>
>> On 02/06/2014 13:04, James Green wrote:
>>
>>> So are Apache paying Oracle to get certified?
>>>
>>>
>>> On 29 May 2014 17:12, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>>
>>> Actually that's a bit worse. TomEE is certified by Oracle as JavaEE
>>>> compliant. We can't be JavaEE 7 certified yet but if we upgrade any spec
>>>> we'll not be JavaEE 6 certified anymore cause API signatures are checked
>>>> in
>>>> the certification process.
>>>>
>>>>
>>>>
>>>> Romain Manni-Bucau
>>>> Twitter: @rmannibucau
>>>> Blog: http://rmannibucau.wordpress.com/
>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>> Github: https://github.com/rmannibucau
>>>>
>>>>
>>>> 2014-05-29 15:31 GMT+02:00 Thiago Veronezi <th...@veronezi.org>:
>>>>
>>>> Hi,
>>>>>
>>>>> They can be used. TomEE needs to be compiled on with JDK 6 tough.
>>>>> Usually
>>>>> Java EE 7 features rely on the JDK 7 features. These things don't work
>>>>> on
>>>>> JDK 6. In order to be certified Java EE 6, we need to support JDK 6.
>>>>> That
>>>>> means that the TomEE source code uses no Java 7 (or Java 8) goodness
>>>>> yet.
>>>>>
>>>>> []s,
>>>>> Thiago.
>>>>>
>>>>>
>>>>>
>>>>> On Thu, May 29, 2014 at 9:10 AM, James Green <james.mk.green@gmail.com
>>>>>
>>>>>> wrote:
>>>>>> Why is it that something EE 7 compliant cannot be used in something EE
>>>>>>
>>>>> 6
>>>>
>>>>> compliant then?
>>>>>>
>>>>>>
>>>>>> On 28 May 2014 12:32, Romain Manni-Bucau <rm...@gmail.com>
>>>>>>
>>>>> wrote:
>>>>
>>>>> Hi
>>>>>>>
>>>>>>> when we'll target JavaEE 7 so end of summer surely
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Romain Manni-Bucau
>>>>>>> Twitter: @rmannibucau
>>>>>>> Blog: http://rmannibucau.wordpress.com/
>>>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>>>> Github: https://github.com/rmannibucau
>>>>>>>
>>>>>>>
>>>>>>> 2014-05-28 12:59 GMT+02:00 James Green <ja...@gmail.com>:
>>>>>>>
>>>>>>> The JIRA Roadmap page appears inaccurate at best so I have to ask
>>>>>>>>
>>>>>>> here
>>>>>
>>>>>> -
>>>>>>
>>>>>>> what plans do you have to ship a TomEE with CXF 3.0 included?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> James
>>>>>>>>
>>>>>>>>
>> --
>> Andy Gumbrecht
>>
>> http://www.tomitribe.com
>> agumbrecht@tomitribe.com
>> https://twitter.com/AndyGeeDe
>>
>> TomEE treibt Tomitribe! | http://tomee.apache.org
>>
>>
Re: Roadmap (CXF 3)
Posted by James Green <ja...@gmail.com>.
I was reading Romain's email about the situation being worse as
re-certification would be required as the interfaces will have changed. I
read that as meaning that each time the interfaces changed a costly
re-certification process would be required.
Can something not be JEE-6 and JEE-7 compliant at the same time then? I was
hoping by upgrading TomEE to CXF 3 it would retain EE-6 compliance and gain
an EE-7 component. Re-certification with an open TCK ought be free..?
On 3 June 2014 11:39, Andy Gumbrecht <ag...@tomitribe.com> wrote:
> Hi James,
>
> Oracle communities define the profile with a reference implementation,
> which is then tested using a Technology Compatibility Kit (TCK). This TCK
> is then offered under license and governed by regulations defined here:
>
> http://www.oracle.com/technetwork/java/index-137188.html
>
> The license includes non-disclosure policies, but you can be assured when
> something claims to be officially certified under the TCK it has met all of
> the defined requirements.
>
> This will also be the case for JEE 7. We are really close to last JEE 6
> release of Apache TomEE 1.7.0, after which we will concentrate on defining
> the JEE 7 roadmap in as much detail as possible for Apache TomEE 2.0.0.
>
> As most of the work is done by volunteers or companies dedicating their
> own time to the project I guess that it us paying Apache 'in kind' to get a
> certified open source version.
>
> Apache TomEE 2.0.0 will be JEE 7 certified and include as many up to date
> technologies as possible on that path - That will include the most recent
> CXF version at the time.
>
> Andy.
>
>
>
> On 02/06/2014 13:04, James Green wrote:
>
>> So are Apache paying Oracle to get certified?
>>
>>
>> On 29 May 2014 17:12, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>
>> Actually that's a bit worse. TomEE is certified by Oracle as JavaEE
>>> compliant. We can't be JavaEE 7 certified yet but if we upgrade any spec
>>> we'll not be JavaEE 6 certified anymore cause API signatures are checked
>>> in
>>> the certification process.
>>>
>>>
>>>
>>> Romain Manni-Bucau
>>> Twitter: @rmannibucau
>>> Blog: http://rmannibucau.wordpress.com/
>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>> Github: https://github.com/rmannibucau
>>>
>>>
>>> 2014-05-29 15:31 GMT+02:00 Thiago Veronezi <th...@veronezi.org>:
>>>
>>> Hi,
>>>>
>>>> They can be used. TomEE needs to be compiled on with JDK 6 tough.
>>>> Usually
>>>> Java EE 7 features rely on the JDK 7 features. These things don't work
>>>> on
>>>> JDK 6. In order to be certified Java EE 6, we need to support JDK 6.
>>>> That
>>>> means that the TomEE source code uses no Java 7 (or Java 8) goodness
>>>> yet.
>>>>
>>>> []s,
>>>> Thiago.
>>>>
>>>>
>>>>
>>>> On Thu, May 29, 2014 at 9:10 AM, James Green <james.mk.green@gmail.com
>>>>
>>>>> wrote:
>>>>> Why is it that something EE 7 compliant cannot be used in something EE
>>>>>
>>>> 6
>>>
>>>> compliant then?
>>>>>
>>>>>
>>>>> On 28 May 2014 12:32, Romain Manni-Bucau <rm...@gmail.com>
>>>>>
>>>> wrote:
>>>
>>>> Hi
>>>>>>
>>>>>> when we'll target JavaEE 7 so end of summer surely
>>>>>>
>>>>>>
>>>>>>
>>>>>> Romain Manni-Bucau
>>>>>> Twitter: @rmannibucau
>>>>>> Blog: http://rmannibucau.wordpress.com/
>>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>>> Github: https://github.com/rmannibucau
>>>>>>
>>>>>>
>>>>>> 2014-05-28 12:59 GMT+02:00 James Green <ja...@gmail.com>:
>>>>>>
>>>>>> The JIRA Roadmap page appears inaccurate at best so I have to ask
>>>>>>>
>>>>>> here
>>>>
>>>>> -
>>>>>
>>>>>> what plans do you have to ship a TomEE with CXF 3.0 included?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> James
>>>>>>>
>>>>>>>
> --
> Andy Gumbrecht
>
> http://www.tomitribe.com
> agumbrecht@tomitribe.com
> https://twitter.com/AndyGeeDe
>
> TomEE treibt Tomitribe! | http://tomee.apache.org
>
>
Re: Roadmap (CXF 3)
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
Hi James,
Oracle communities define the profile with a reference implementation,
which is then tested using a Technology Compatibility Kit (TCK). This
TCK is then offered under license and governed by regulations defined here:
http://www.oracle.com/technetwork/java/index-137188.html
The license includes non-disclosure policies, but you can be assured
when something claims to be officially certified under the TCK it has
met all of the defined requirements.
This will also be the case for JEE 7. We are really close to last JEE 6
release of Apache TomEE 1.7.0, after which we will concentrate on
defining the JEE 7 roadmap in as much detail as possible for Apache
TomEE 2.0.0.
As most of the work is done by volunteers or companies dedicating their
own time to the project I guess that it us paying Apache 'in kind' to
get a certified open source version.
Apache TomEE 2.0.0 will be JEE 7 certified and include as many up to
date technologies as possible on that path - That will include the most
recent CXF version at the time.
Andy.
On 02/06/2014 13:04, James Green wrote:
> So are Apache paying Oracle to get certified?
>
>
> On 29 May 2014 17:12, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
>> Actually that's a bit worse. TomEE is certified by Oracle as JavaEE
>> compliant. We can't be JavaEE 7 certified yet but if we upgrade any spec
>> we'll not be JavaEE 6 certified anymore cause API signatures are checked in
>> the certification process.
>>
>>
>>
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>> 2014-05-29 15:31 GMT+02:00 Thiago Veronezi <th...@veronezi.org>:
>>
>>> Hi,
>>>
>>> They can be used. TomEE needs to be compiled on with JDK 6 tough. Usually
>>> Java EE 7 features rely on the JDK 7 features. These things don't work on
>>> JDK 6. In order to be certified Java EE 6, we need to support JDK 6. That
>>> means that the TomEE source code uses no Java 7 (or Java 8) goodness yet.
>>>
>>> []s,
>>> Thiago.
>>>
>>>
>>>
>>> On Thu, May 29, 2014 at 9:10 AM, James Green <james.mk.green@gmail.com
>>>> wrote:
>>>> Why is it that something EE 7 compliant cannot be used in something EE
>> 6
>>>> compliant then?
>>>>
>>>>
>>>> On 28 May 2014 12:32, Romain Manni-Bucau <rm...@gmail.com>
>> wrote:
>>>>> Hi
>>>>>
>>>>> when we'll target JavaEE 7 so end of summer surely
>>>>>
>>>>>
>>>>>
>>>>> Romain Manni-Bucau
>>>>> Twitter: @rmannibucau
>>>>> Blog: http://rmannibucau.wordpress.com/
>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>> Github: https://github.com/rmannibucau
>>>>>
>>>>>
>>>>> 2014-05-28 12:59 GMT+02:00 James Green <ja...@gmail.com>:
>>>>>
>>>>>> The JIRA Roadmap page appears inaccurate at best so I have to ask
>>> here
>>>> -
>>>>>> what plans do you have to ship a TomEE with CXF 3.0 included?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> James
>>>>>>
--
Andy Gumbrecht
http://www.tomitribe.com
agumbrecht@tomitribe.com
https://twitter.com/AndyGeeDe
TomEE treibt Tomitribe! | http://tomee.apache.org