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]

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 >

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

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):

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

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

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]