TCK status

Hello community, Quick update on Jakarta EE 9.1 status. 9.1 is going out soon, and we are trying to cross the finish line with TomEE being certified. We are running under Java 11 with TomEE 9.0-SNAPSHOT for the moment. And we are also grabbing a SNAPSHOT version (or building) of the TCK 9.1 Here

TCK status

Hi! We are down to 4 failures (sometimes only 3, one of the tests seems a bit random): Failed tests: RequestScopeEventRemoteTest>Arquillian.run:164->testRequestScopeActiveDuringRemoteCallToEjb:66 expected [true] but found [false] ApplicationInitializationLifecycleTest>Arquillian.run:164->

TomEE8 TCK status

Hi folks! I've come down to just 18 failing tests in tck/cdi-embedded.Most of them are EE related (missing privileges exceptions etc) There is one left with the CDI integration: support.This needs a change in the beans.xml schema.I've added the changes and moved to container/openejb-jee/src/mai

Re: TCK status

Awesome. Well done Mark and thank you for spending time on this. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Mar 9, 2015 at 8:31 AM, Mark Struberg wrote: > Hi! > > We are down to 4 failures (sometimes only 3, one of the tests seems a bit > random):

Re: TCK status

This is due to filters and flushing ordering. Should not be hard to fix. Next step is tomee. Le 9 mars 2015 17:05, "Jean-Louis Monteiro" a écrit : > Awesome. > > Well done Mark and thank you for spending time on this. > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www

Re: TomEE8 TCK status

Hi Mark, For simple updates like that I tend to update the sax parser manually (that's what we did for JSF since most of the model is not handled by tomee anyway). For CDI we are supposed to still use JAXB (since there can be a lot of beans.xml): https://github.com/apache/tomee/blob/master/contain

Re: TomEE8 TCK status

Yes I thought something similar when trashing 2 hours to try to get the JAXB generator running. Just to figure it might be broken beyond repair... Thanks that you at least confirm this view and spare me further investigation. There are 2 options on the table 1.) Do a quick hack and add the supp

Re: TomEE8 TCK status

2018-01-31 9:34 GMT+01:00 Mark Struberg : > Yes I thought something similar when trashing 2 hours to try to get the > JAXB generator running. > Just to figure it might be broken beyond repair... > Thanks that you at least confirm this view and spare me further > investigation. > > There are 2 opti

Re: TomEE8 TCK status

Then we should at least add a README? Or at least document that profile in the pom. LieGrue, strub > Am 31.01.2018 um 09:59 schrieb Romain Manni-Bucau : > > 2018-01-31 9:34 GMT+01:00 Mark Struberg : > >> Yes I thought something similar when trashing 2 hours to try to get the >> JAXB generato

Re: TomEE8 TCK status

yes yank the profile if not usable and if no one should use it to avoid mistakes -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, Jan 31, 2018 at 10:23 AM, Mark Struberg wrote: > > Then we should at least add a README? > Or at least document that profil

Re: TomEE8 TCK status

Txs JL! Btw, this is the current status: [ERROR] Failures: [ERROR] EnterpriseDefaultBeanDiscoveryModeTest>Arquillian.arquillianBeforeClass:109 » Deployment [ERROR] ResourceAdapterArchiveTest>Arquillian.run:164->testInjection:79 expected object to not be null [ERROR] ResourceAdapterArchi

Re: TomEE8 TCK status

>From memory, until you need jsf or advanced web stuff all should run in embedded mode. That said we can need to tune jaas to match the expectations of the tcks. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: TomEE8 TCK status

Fixed the new CDI-2.0 feature. Now down to 16 ^^ [ERROR] Failures: [ERROR] EnterpriseDefaultBeanDiscoveryModeTest>Arquillian.arquillianBeforeClass:109 » Deployment [ERROR] ResourceAdapterArchiveTest>Arquillian.run:164->testInjection:79 expected object to not be null [ERROR] ResourceAda

Re: TomEE8 TCK status

With a bit help from Romains we are now down to 10 failing tests: ERROR] Failures: [ERROR]   EnterpriseDefaultBeanDiscoveryModeTest>Arquillian.arquillianBeforeClass:109 » Deployment [ERROR]   ObserverMethodInvocationContextTest>Arquillian.run:164->testTransactionalObserverMethod:55 » EJB [E

Re: TomEE8 TCK status

exciting.  when it passes all the tests will there be a beta release ? On 01/02/2018 14:37, Mark Struberg wrote: With a bit help from Romains we are now down to 10 failing tests: ERROR] Failures: [ERROR]   EnterpriseDefaultBeanDiscoveryModeTest>Arquillian.arquillianBeforeClass:109 » Deploy

Re: TomEE8 TCK status

These are CDI TCK only. Java EE 8 TCK aren't available openly (Open sourced) so we can't certify the Apache version of TomEE -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, Feb 1, 2018 at 3:36 PM, Matthew Broadhead < matthew.broadh...@nbmlaw.co.uk> wrote:

Re: TomEE8 TCK status

a lot of libs should be updated before the release I think, like johnzon which is ready (literally like 2 poms to update). but yes we can do a release anytime technically. In terms of first bundle we can at least desire to have CDI 2 webprofile support, probably json-p/json-b and maybe jax-rs upgra

Re: TomEE8 TCK status

Hello, I will be able to use (and thus, to make feedbacks) on a TomEE+ 8 binary preview release if it includes JAX RS 2.1 : I have some fun stuff to do with SSE for feeding some reactive uis :) Best regards, Alex 2018-02-01 16:39 GMT+01:00 Romain Manni-Bucau : > a lot of libs should be updated b

Re: TomEE8 TCK status

And the last status: [ERROR] Failures: [ERROR] EnterpriseDefaultBeanDiscoveryModeTest>Arquillian.arquillianBeforeClass:109 » Deployment [ERROR] ContainerLifeCycleEventRuntimeInvocationTest>Arquillian.arquillianBeforeClass:109 » Deployment [ERROR] BuiltinMetadataEEBeanTest>Arquillian.run

Re: TomEE8 TCK status

[ERROR] Failures: [ERROR] EnterpriseDefaultBeanDiscoveryModeTest>Arquillian.arquillianBeforeClass:109 » Deployment [INFO] [ERROR] Tests run: 1567, Failures: 1, Errors: 0, Skipped: 5 Wohuuu, 1 to go! LieGrue, strub > Am 02.02.2018 um 21:54 schrieb Mark Struberg : > > And the last status: >

Re: TomEE8 TCK status

nearly there! On 07/02/2018 11:57, Mark Struberg wrote: [ERROR] Failures: [ERROR] EnterpriseDefaultBeanDiscoveryModeTest>Arquillian.arquillianBeforeClass:109 » Deployment [INFO] [ERROR] Tests run: 1567, Failures: 1, Errors: 0, Skipped: 5 Wohuuu, 1 to go! LieGrue, strub Am 02.02.2018 um

Re: TomEE8 TCK status

All the embedded tests are now green. I'm now working on cdi-tomes (webprofile TCK). So far we have 10 errors, but a few TCK tests are broken because they wrongly assume that a container stop also kills the Session. I've challenged those tests. Still have to review every red test... LieGrue, str

Re: TomEE8 TCK status

2018-02-08 11:28 GMT+01:00 Mark Struberg : > All the embedded tests are now green. > > I'm now working on cdi-tomes (webprofile TCK). > So far we have 10 errors, but a few TCK tests are broken because they > wrongly assume that a container stop also kills the Session. > We can make them passing.

Re: TomEE8 TCK status

Yea, it's mainly testing whether the @Observes @BeforeDestroyed(SessionScoped.class) and @Destroyed(SessionScoped.class) do work. The tests itself are fine, but instead of relying that the sessions get destroyed at server shutdown they could also have used Session.invalidate()... LieGrue, strub

Re: TomEE8 TCK status

Hmm, it is more vicious cause if the session is not destroyed you can still want to trigger this event. Guess it is another case where both cases are desirable (i want to clean up related state of the session...as well as I don't want to touch the session)... Since the appcontext destroy can be us

Re: TomEE8 TCK status

Well, this is why there are passivation listeners and stuff in the Servlet spec. We could easily also send a specific CDI event for it. But there is no such event in the CDI spec so far. The @Destryoed and @BeforeDestroyed are specifically for _destroyal_. LieGrue, strub > Am 08.02.2018 um 12:

Re: TomEE8 TCK status

We now pass all tests in tck/cdi-embedded And we have only 3 failing tests in tck/cdi-tomee. Those tests are all EAR related. Maybe they are only Arquillian adapter issues? LieGrue, strub > Am 08.02.2018 um 13:30 schrieb Mark Struberg : > > Well, this is why there are passivation listene

Re: TomEE8 TCK status

2018-02-14 23:28 GMT+01:00 Mark Struberg : > We now pass all tests in tck/cdi-embedded > And we have only 3 failing tests in tck/cdi-tomee. > > > > > > Those tests are all EAR related. > Maybe they are only Arquillian adapter issues? > Don't think so, ear deployment is not that hacky in arquil

Re: TomEE8 TCK status

At the risk of adding to my ever-growing task list and potentially becoming a bottleneck, I did some EAR / RAR related fixes in master. I'll port those forward and help look at these tests. Jon On Wed, Feb 14, 2018 at 10:28 PM, Mark Struberg wrote: > We now pass all tests in tck/cdi-embedded >

Re: TomEE8 TCK status

Really appreciated, thanks Jon! Due to the upgrade to Tomcat-9 we also might have to fix a few other tests along the line. I mainly focused on the CDI TCK for now as this is naturally the area where I can be of most use. I'll also gonna release OWB tonight or so. Just wanted to first fix the To

Re: TomEE8 TCK status

and now we should be passing both the tck/cdi-embedded and tck/cdi-tomee! So it's time to move forward to updating various dependencies, samples etc ;) LieGrue, strub > Am 15.02.2018 um 11:42 schrieb Mark Struberg : > > Really appreciated, thanks Jon! > > Due to the upgrade to Tomcat-9 we also

Re: TomEE8 TCK status

and probably switch the branch. master doesnt get much activity and in any case all the activity it gets can be done on the 8 branch Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: TomEE8 TCK status

probably a good idea. A tomee7 release should still be cut. But that could be done on a tomee7.x branch as well Will create a separate thread. LieGrue, strub > Am 15.02.2018 um 18:11 schrieb Romain Manni-Bucau : > > and probably switch the branch. master doesnt get much activity and in any

Re: TomEE8 TCK status

We definitely need a tomee-7 branch. I have done a merge of master to the tomee8_fb branch, and I'm making sure it builds and tests pass etc, before pushing. Jon On Thu, Feb 15, 2018 at 5:19 PM, Mark Struberg wrote: > probably a good idea. > > A tomee7 release should still be cut. But that coul

Re: TomEE8 TCK status

oki great, I've just upgraded to tomcat-9.0.5 and right now upgrading to xbean-asm6-shaded. Will ping you once done. LieGrue, strub > Am 15.02.2018 um 18:27 schrieb Jonathan Gallimore > : > > We definitely need a tomee-7 branch. I have done a merge of master to the > tomee8_fb branch, and I'm

Re: TomEE8 TCK status

PS: xbean-asm6 is needed for java9 support. Already using it in OWB and Meecrowave without any problems. So all should work fine. LieGrue, strub > Am 15.02.2018 um 19:20 schrieb Mark Struberg : > > oki great, I've just upgraded to tomcat-9.0.5 and right now upgrading to > xbean-asm6-shaded. >

Re: TomEE8 TCK status

Ok, locally (with the merge), I get test errors due to: java.lang.NoClassDefFoundError: javax/ws/rs/client/CompletionStageRxInvoker. Possibly a bad javaee dependency or something. I'll do a compare tomorrow and try and get that resolved, and get my changes pushed. Jon On Thu, Feb 15, 2018 at 6:41

Re: TomEE8 TCK status

Dont think our ee api has upgraded to https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-jaxrs_2.1_spec/ yet since we didnt have cxf 3.2. Le 16 févr. 2018 00:49, "Jonathan Gallimore" a écrit : > Ok, locally (with the merge), I get test errors due > to: java.lang.NoClassDefFoundError:

Re: TomEE8 TCK status

I think we did, but I probably did not deploy our javaee-api yet. Started the deploy jus tnow. LieGrue, strub > Am 16.02.2018 um 07:14 schrieb Romain Manni-Bucau : > > Dont think our ee api has upgraded to > https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-jaxrs_2.1_spec/ > yet si

Re: TomEE8 TCK status

Or just compile it yourself from source: https://svn.apache.org/repos/asf/tomee/javaee-api/trunk LieGrue, strub > Am 16.02.2018 um 07:41 schrieb Mark Struberg : > > I think we did, but I probably did not deploy our javaee-api yet. > > Started the deploy jus tnow. > > LieGrue, > strub > >>

Jakarta EE TCK status

Hey TomEE community, We just reach the 99% coverage of the Jakarta EE 8 TCK with TomEE 8 under JDK 8. We have few failures around EJB3, Javamail, Servlet, JSTL and JDBC. Any helps would be appreciated. I can provide everyone a way to run the failures only locally so you can help fix. Meanwhile,

[TCK] Status and plans

Hi community, Trying to give visibility as much as possible. Here is a more high level status on Jakarta EE 8 TCK (EE 9 is close so I'll focus on EE 8) I would say that most of the integration work has been done. We are mostly in a final stage where we need to check what a test is doing, and eith

Re: Jakarta EE TCK status

Woot! Almost there! Great job, Jean-Louis!! On Tue, Aug 6, 2019 at 3:07 AM Jean-Louis Monteiro wrote: > Hey TomEE community, > > We just reach the 99% coverage of the Jakarta EE 8 TCK with TomEE 8 under > JDK 8. > We have few failures around EJB3, Javamail, Servlet, JSTL and JDBC. > > Any helps

Re: Jakarta EE TCK status

Thanks for the update Jean-Louis, Base on your comment: > Any helps would be appreciated.I can provide everyone a way to run the > failures only locally so you can help fix. I think we can move Translation efforts into Code efforts to help Jakarta EE TCK 8 cross the finish line :) Let us know h

Re: Jakarta EE TCK status

Let's start filling subtasks in this ticket https://issues.apache.org/jira/browse/TOMEE-2603 I'll try to start adding subtasks with how to reproduce and what to look at. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Aug 6, 2019 at 5:13 PM Cesar Herna

Re: [TCK] Status and plans

Just a small heads up Here is the very last result of this week https://tck.work/tomee/build?id=1607726026267 We managed to fix about 100 tests, so we are at about 250 of the finish line. Small notes 1/ I have added some excludes for tests which were bad and that got fixed in Jakarta EE 9 - See

Re: [TCK] Status and plans

Hi all, Here is the last run https://tck.work/tomee/build?id=1608554936631 I just closed the vote on Apache Johnzon and released it. TomEE is up to date now and we should be 100% on JSONP. On JSTL, https://tck.work/tomee/tests?path=com.sun.ts.tests.jstl&build=1608554936631&status=FAILED Locally

Re: [TCK] Status and plans

https://tck.work/tomee/build?id=1608726402626 Boom, JSTL 1 failure and JSONP 0 failure. We are down to 209 failures -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, Dec 23, 2020 at 10:34 AM Jean-Louis Monteiro < jlmonte...@tomitribe.com> wrote: > Hi all,

Re: [TCK] Status and plans

Hi all, With the end of the year and some work constraints, I haven't been able to really work too much on the TCK. But I was back on it a bit last week and this week. Did some work on Jakarta EE 9 to see where we were at and I've been able to get down to 400+ failures which is not bad at all. ht

Jakarta EE 10 Web Profile TCK status

All, I’ve been fighting with the getting the latest TCK for a while now and from the looks of it there are significant changes not just to the standalone TCKs but to the Platform/WebProfile TCK as well. The initial results of the EE 10 TCK have us at about 44% passing. - https://tck.work/tom