I am not certain to be honest but they have to tie it to a RI aka Glashfish release to
make sure the RI passes it.
On 2 déc. 2011, at 18:45, Matt Benson <mbenson(a)apache.org> wrote:
Emmanuel: Thanks for running this down. Is their process of
upgrading
"nestedTCKs" somewhat informal, then?
Matt
On Fri, Dec 2, 2011 at 11:10 AM, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
> I have been discussing with people at Oracle and they did tell me that the EE TCK
uses BV's 1.0.6 since August this year and you should not have any problem.
>
> On 1 déc. 2011, at 17:29, Matt Benson wrote:
>
>> Hi all,
>> As far as I know, the version of the JSR303 TCK still in use with
>> Java EE is 1.0.3.GA; i.e. that's what Geronimo and OpenEJB are both
>> constrained to use here on the Apache side of the fence. As you may
>> recall, there is a huge compatibility gap between 1.0.4.GA and
>> 1.0.5.GA of the TCK due to
>>
https://hibernate.onjira.com/browse/BVTCK-12 --as far as I know it's
>> impossible for an implementation of JSR303 to pass < 1.0.5.GA and >=
>> 1.0.5.GA simultaneously. What is the procedure for upgrading the Bean
>> Validation TCK Oracle will use for Java EE, so that EE implementations
>> can use the latest JSR303 implementations?
>>
>> Thanks,
>> Matt
>> _______________________________________________
>> beanvalidation-dev mailing list
>> beanvalidation-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
>
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev