Re: TOMEE-2967 - Translate to Spanish: examples/xa-datasource/
I have assigned it to you. Thank you! Gruss Richard Am Donnerstag, den 28.01.2021, 23:13 -0300 schrieb Evaldo Junior: > I created the issue on the JIRA [1] to translate to spanish of the > document > examples/xa-datasource/. > Can some of the JIRA admins please assign the ticket to my > username:evaldoapjunior > > [1]https://issues.apache.org/jira/browse/TOMEE-2967 > > > Best Regards, > > > Evaldo Junior smime.p7s Description: S/MIME cryptographic signature
TOMEE-2967 - Translate to Spanish: examples/xa-datasource/
I created the issue on the JIRA [1] to translate to spanish of the document examples/xa-datasource/. Can some of the JIRA admins please assign the ticket to my username:evaldoapjunior [1]https://issues.apache.org/jira/browse/TOMEE-2967 Best Regards, Evaldo Junior
[GitHub] [tomee] exabrial commented on pull request #759: TOMEE-2966: Provide a pure JUnit5 OpenEJB Extension
exabrial commented on pull request #759: URL: https://github.com/apache/tomee/pull/759#issuecomment-769222943 Love this! We converted to JUnit5 awhile back This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: TomEE 9 with Jakarta EE 9
Hi, I like the idea of move to master 9.x. On Thu, Jan 28, 2021, 10:12 Daniel Cunha wrote: > Hi!! > > personally, I like the idea to create a maintenance branch for TomEE 8.x > and move master to 9.x. > > > Em qui., 28 de jan. de 2021 às 08:50, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> escreveu: > > > Hi, > > > > We started the work on Jakarta EE 9 a few months ago. So far we are in > good > > shape by only applying the transformer in our code. But it looks like we > > are facing some limitations. > > > > 1/ libraries we are using Tomcat, Mojorra, EclipseLink to name a few > > already have Jakarta EE 9 compliant versions, which are more complete > than > > what we could do with the transformer. > > > > 2/ only creating zip files is restrictive. People can't use the > > EJBContainer to unit test their code because we don't publish Maven > > artifacts. TomEE embedded and other flavors of TomEE are not available > > anymore. > > > > I'm wondering if at this moment, it would not be better to create a > > maintenant branch for TomEE 8.x and move master to 9.x > > > > We could just do the dependency upgrades in there and any API changes due > > to dependency upgrades. > > > > We would only keep working on TomEE 8 and cherry pick or backport > > everything into TomEE 9.x so we have minimal changes between the 2 and we > > don't spread our effort on multiple source trees. > > > > What do you think? > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > -- > Daniel "soro" Cunha > https://twitter.com/dvlc_ >
Re: TomEE 9 with Jakarta EE 9
Hi!! personally, I like the idea to create a maintenance branch for TomEE 8.x and move master to 9.x. Em qui., 28 de jan. de 2021 às 08:50, Jean-Louis Monteiro < jlmonte...@tomitribe.com> escreveu: > Hi, > > We started the work on Jakarta EE 9 a few months ago. So far we are in good > shape by only applying the transformer in our code. But it looks like we > are facing some limitations. > > 1/ libraries we are using Tomcat, Mojorra, EclipseLink to name a few > already have Jakarta EE 9 compliant versions, which are more complete than > what we could do with the transformer. > > 2/ only creating zip files is restrictive. People can't use the > EJBContainer to unit test their code because we don't publish Maven > artifacts. TomEE embedded and other flavors of TomEE are not available > anymore. > > I'm wondering if at this moment, it would not be better to create a > maintenant branch for TomEE 8.x and move master to 9.x > > We could just do the dependency upgrades in there and any API changes due > to dependency upgrades. > > We would only keep working on TomEE 8 and cherry pick or backport > everything into TomEE 9.x so we have minimal changes between the 2 and we > don't spread our effort on multiple source trees. > > What do you think? > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > -- Daniel "soro" Cunha https://twitter.com/dvlc_
[TCK] EJB 30 Interceptor test in embedded mode
Hi all, We have currently 3 tests failing on this section where I would get any help or ideas. - com.sun.ts.tests.ejb30.lite.interceptor.singleton.lifecycle.annotated.Client - Works in Servlet, JSF and others but fails in Standalone. Looks like when we deploy a jar file, CDI is not activated and is not picking up the @AroundConstruct methods. - I created a test to mimic what the TCK does. There are no asserts in there so build does not fail because of it. But if someone can have a look and give some thoughts, that would be great as I'm a bit stuck on this one - https://github.com/apache/tomee/commit/e03a4ed5eda1d0d04d3de057788446f4762f4e4f - - com.sun.ts.tests.ejb30.lite.packaging.war.datasource.global.Client - Fails with database not found. Works locally so something to do with other tests maybe. - - com.sun.ts.tests.ejb30.lite.packaging.war.datasource.singleton.Client - Same as previous After that, we should also be 100% compliant. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com
TomEE 9 with Jakarta EE 9
Hi, We started the work on Jakarta EE 9 a few months ago. So far we are in good shape by only applying the transformer in our code. But it looks like we are facing some limitations. 1/ libraries we are using Tomcat, Mojorra, EclipseLink to name a few already have Jakarta EE 9 compliant versions, which are more complete than what we could do with the transformer. 2/ only creating zip files is restrictive. People can't use the EJBContainer to unit test their code because we don't publish Maven artifacts. TomEE embedded and other flavors of TomEE are not available anymore. I'm wondering if at this moment, it would not be better to create a maintenant branch for TomEE 8.x and move master to 9.x We could just do the dependency upgrades in there and any API changes due to dependency upgrades. We would only keep working on TomEE 8 and cherry pick or backport everything into TomEE 9.x so we have minimal changes between the 2 and we don't spread our effort on multiple source trees. What do you think? -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com
