Hi Short answer is no.
Reason is some "clarification" of EE 6 -> EE 7 made some changes making the run "red" whatever you do. This means the TCK result is "not EE 6 complaint" to be "EE 7 compliant". We sadly can't detail what is not and what is due to legal reasons around TCK themself. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-06-13 13:57 GMT+02:00 Kasun Gajasinghe <[email protected]>: > Hi devs, > > First of all, big kudos for getting the TomEE 7.0.0 release done. > > I'm interested in knowing $subject. I know that TomEE 7 is not certified > against JavaEE 7, but still have you tried to keep the compatibility with > JavaEE 6 WP as it is? > > I'm asking this because I've been checking other vendors and some have > maintained the compatibility with older JavaEE 6 specification. > > Thanks, > Kasun > > -- > ~~~*******'''''''''''''*******~~~ > *Kasun Gajasinghe* > Senior Software Engineer; WSO2 Inc.; http://wso2.com, > *Linked-in: *http://lk.linkedin.com/in/gajasinghe > *Blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org/> > > > *GitHub: **http://github.com/kasunbg* <http://github.com/kasunbg> >
