TOMEE-2926: Translate to Portuguese: examples/serverless-builder
Hello, I opened a ticket in Jira [1] and a PR [2], can anyone revise the translation? thank you [1] https://issues.apache.org/jira/browse/TOMEE-2926 [2] https://github.com/apache/tomee/pull/719 -- *Daniel Dias dos Santos* Java Developer SouJava & JCP Member GitHub: https://github.com/Daniel-Dos Linkedin: www.linkedin.com/in/danieldiasjava Twitter: http://twitter.com/danieldiasjava
[GitHub] [tomee] Daniel-Dos opened a new pull request #719: TOMEE-2926: Translate to Portuguese: examples/serverless-builder
Daniel-Dos opened a new pull request #719: URL: https://github.com/apache/tomee/pull/719 link to jira : https://issues.apache.org/jira/browse/TOMEE-2926 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: TCK work on Jakarta EE 8 and Jakarta EE 9
very good : ) -- *Daniel Dias dos Santos* Java Developer SouJava & JCP Member GitHub: https://github.com/Daniel-Dos Linkedin: www.linkedin.com/in/danieldiasjava Twitter: http://twitter.com/danieldiasjava Em seg., 16 de nov. de 2020 às 23:43, David Jencks escreveu: > Great work! > > It’s really nice we don’t have to hide it! > > David Jencks > > > On Nov 16, 2020, at 3:40 PM, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > > Hi community, > > > > Alongside with the Jakarta EE 9 work I've been doing, I tried to look at > > TomEE coverage for EE 8 and EE 9. They are quite close in terms of scope. > > The only difference is pretty much only the namespace change from javax > to > > jakarta. > > > > I looked into our EE 9 coverage with our TomEE 9 milestone and we are > quite > > far in terms of coverage. > > > > I pushed some setup changes in the dedicated > > https://github.com/apache/tomee-tck/tree/jakartaee9-tck branch to bring > the > > coverage near EE 8 coverage with TomEE (aka around 90+ %) > > > > The big gaps were as far as I can see around jaspic, securityapi and jta. > > > > 1/ JASPIC > > It's about authentication for containers. We don't have much but setup > > because we rely on Tomcat's implementation. > > We are having some issues with the setup because of the way TCK is built > > for jaspic. I've been able to workaround some, but I also got hit by TCK > > issues. > > See TomEE tickets > > > > https://issues.apache.org/jira/browse/TOMEE-2923 > > https://issues.apache.org/jira/browse/TOMEE-2924 > > https://issues.apache.org/jira/browse/TOMEE-2925 > > > > 2/ Security API > > This is about authorization and stores. > > This time implementation is all in TomEE (see tomee-security module). > I'll > > try to send another email with a walk through. It's been mostly > implemented > > in a quick and dirty mode but it needs tests and hardening before we can > > call it done. With that we can cover nearly 100% coverage of TCK. > > But, because there is a bug, we have random failures due to the way TCK > is > > built. I'll create a new ticket shortly to describe the issue. > > > > 3/ JTA > > We used to be covering 100% but we are down to 70% because of the > addition > > of @Transactional CDI tests. I again looked into our implementation and > the > > tests and found again issues with the TCK > > > > See ticket https://issues.apache.org/jira/browse/TOMEE-2921 > > > > I'll continue to dig into the other areas. > > Especially everything related to Tomcat should be closer to 100% than it > is > > today (JSTL, JSP, Servlet and WebSockets). > > > > If you want to help and look at them, that'd be great. > > Basically follow the steps to run the TCK locally as described here > > https://github.com/apache/tomee-tck > > > > and run > > > > com.sun.ts.tests.jstl > > com.sun.ts.tests.jsp > > com.sun.ts.tests.servlet > > com.sun.ts.tests.websocket > > > > Then go ahead and investigate. Feel free to create a ticket or at least > > shoot something in the mailing list so we don't duplicate the efforts. > > > > Hope it helps > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > >
Re: TCK work on Jakarta EE 8 and Jakarta EE 9
Great work! It’s really nice we don’t have to hide it! David Jencks > On Nov 16, 2020, at 3:40 PM, Jean-Louis Monteiro > wrote: > > Hi community, > > Alongside with the Jakarta EE 9 work I've been doing, I tried to look at > TomEE coverage for EE 8 and EE 9. They are quite close in terms of scope. > The only difference is pretty much only the namespace change from javax to > jakarta. > > I looked into our EE 9 coverage with our TomEE 9 milestone and we are quite > far in terms of coverage. > > I pushed some setup changes in the dedicated > https://github.com/apache/tomee-tck/tree/jakartaee9-tck branch to bring the > coverage near EE 8 coverage with TomEE (aka around 90+ %) > > The big gaps were as far as I can see around jaspic, securityapi and jta. > > 1/ JASPIC > It's about authentication for containers. We don't have much but setup > because we rely on Tomcat's implementation. > We are having some issues with the setup because of the way TCK is built > for jaspic. I've been able to workaround some, but I also got hit by TCK > issues. > See TomEE tickets > > https://issues.apache.org/jira/browse/TOMEE-2923 > https://issues.apache.org/jira/browse/TOMEE-2924 > https://issues.apache.org/jira/browse/TOMEE-2925 > > 2/ Security API > This is about authorization and stores. > This time implementation is all in TomEE (see tomee-security module). I'll > try to send another email with a walk through. It's been mostly implemented > in a quick and dirty mode but it needs tests and hardening before we can > call it done. With that we can cover nearly 100% coverage of TCK. > But, because there is a bug, we have random failures due to the way TCK is > built. I'll create a new ticket shortly to describe the issue. > > 3/ JTA > We used to be covering 100% but we are down to 70% because of the addition > of @Transactional CDI tests. I again looked into our implementation and the > tests and found again issues with the TCK > > See ticket https://issues.apache.org/jira/browse/TOMEE-2921 > > I'll continue to dig into the other areas. > Especially everything related to Tomcat should be closer to 100% than it is > today (JSTL, JSP, Servlet and WebSockets). > > If you want to help and look at them, that'd be great. > Basically follow the steps to run the TCK locally as described here > https://github.com/apache/tomee-tck > > and run > > com.sun.ts.tests.jstl > com.sun.ts.tests.jsp > com.sun.ts.tests.servlet > com.sun.ts.tests.websocket > > Then go ahead and investigate. Feel free to create a ticket or at least > shoot something in the mailing list so we don't duplicate the efforts. > > Hope it helps > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com
TCK work on Jakarta EE 8 and Jakarta EE 9
Hi community, Alongside with the Jakarta EE 9 work I've been doing, I tried to look at TomEE coverage for EE 8 and EE 9. They are quite close in terms of scope. The only difference is pretty much only the namespace change from javax to jakarta. I looked into our EE 9 coverage with our TomEE 9 milestone and we are quite far in terms of coverage. I pushed some setup changes in the dedicated https://github.com/apache/tomee-tck/tree/jakartaee9-tck branch to bring the coverage near EE 8 coverage with TomEE (aka around 90+ %) The big gaps were as far as I can see around jaspic, securityapi and jta. 1/ JASPIC It's about authentication for containers. We don't have much but setup because we rely on Tomcat's implementation. We are having some issues with the setup because of the way TCK is built for jaspic. I've been able to workaround some, but I also got hit by TCK issues. See TomEE tickets https://issues.apache.org/jira/browse/TOMEE-2923 https://issues.apache.org/jira/browse/TOMEE-2924 https://issues.apache.org/jira/browse/TOMEE-2925 2/ Security API This is about authorization and stores. This time implementation is all in TomEE (see tomee-security module). I'll try to send another email with a walk through. It's been mostly implemented in a quick and dirty mode but it needs tests and hardening before we can call it done. With that we can cover nearly 100% coverage of TCK. But, because there is a bug, we have random failures due to the way TCK is built. I'll create a new ticket shortly to describe the issue. 3/ JTA We used to be covering 100% but we are down to 70% because of the addition of @Transactional CDI tests. I again looked into our implementation and the tests and found again issues with the TCK See ticket https://issues.apache.org/jira/browse/TOMEE-2921 I'll continue to dig into the other areas. Especially everything related to Tomcat should be closer to 100% than it is today (JSTL, JSP, Servlet and WebSockets). If you want to help and look at them, that'd be great. Basically follow the steps to run the TCK locally as described here https://github.com/apache/tomee-tck and run com.sun.ts.tests.jstl com.sun.ts.tests.jsp com.sun.ts.tests.servlet com.sun.ts.tests.websocket Then go ahead and investigate. Feel free to create a ticket or at least shoot something in the mailing list so we don't duplicate the efforts. Hope it helps -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com
[GitHub] [tomee] tandraschko commented on pull request #717: MyFaces 2.3.7
tandraschko commented on pull request #717: URL: https://github.com/apache/tomee/pull/717#issuecomment-728258030 Could someone please merge it? 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
[GitHub] [tomee] rzo1 commented on pull request #713: TOMEE-2324 - Remove Corba ORB APIs from Codebase
rzo1 commented on pull request #713: URL: https://github.com/apache/tomee/pull/713#issuecomment-728116269 > @rzo1 Take a look at: [rzo1#1](https://github.com/rzo1/tomee/pull/1) Looks good to me. Thanks for the updates. 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
[GitHub] [tomee] jgallimore commented on pull request #713: TOMEE-2324 - Remove Corba ORB APIs from Codebase
jgallimore commented on pull request #713: URL: https://github.com/apache/tomee/pull/713#issuecomment-728115468 @rzo1 Take a look at: https://github.com/rzo1/tomee/pull/1 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
[GitHub] [tomee] jgallimore commented on pull request #713: TOMEE-2324 - Remove Corba ORB APIs from Codebase
jgallimore commented on pull request #713: URL: https://github.com/apache/tomee/pull/713#issuecomment-728041882 Added the dependency -- getting further. 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
[GitHub] [tomee] rzo1 commented on pull request #713: TOMEE-2324 - Remove Corba ORB APIs from Codebase
rzo1 commented on pull request #713: URL: https://github.com/apache/tomee/pull/713#issuecomment-728030626 > Building with JDK8 is fine, the failure above is with JDK11. Looks like a dependency update in the apache-tomee module will fix it. The `javax/xml/bind/JAXBException`classes were removed from the JDK; we might need to add the correct dependencies. 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
[GitHub] [tomee] jgallimore commented on pull request #713: TOMEE-2324 - Remove Corba ORB APIs from Codebase
jgallimore commented on pull request #713: URL: https://github.com/apache/tomee/pull/713#issuecomment-728026028 Building with JDK8 is fine, the failure above is with JDK11. Looks like a dependency update in the apache-tomee module will fix it. 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
[GitHub] [tomee] jgallimore commented on pull request #713: TOMEE-2324 - Remove Corba ORB APIs from Codebase
jgallimore commented on pull request #713: URL: https://github.com/apache/tomee/pull/713#issuecomment-728024025 Currently running into this issue: ``` [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 03:26 min [INFO] Finished at: 2020-11-16T13:32:24Z [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.20:integration-test (default) on project apache-tomee: Execution default of goal org.apache.maven.plugins:maven-failsafe-plugin:2.20:integration-test failed: A required class was missing while executing org.apache.maven.plugins:maven-failsafe-plugin:2.20:integration-test: javax/xml/bind/JAXBException [ERROR] - [ERROR] realm =plugin>org.apache.maven.plugins:maven-failsafe-plugin:2.20 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy [ERROR] urls[0] = file:/home/jgallimore/.m2/repository/org/apache/maven/plugins/maven-failsafe-plugin/2.20/maven-failsafe-plugin-2.20.jar [ERROR] urls[1] = file:/home/jgallimore/.m2/repository/org/apache/maven/surefire/maven-surefire-common/2.20/maven-surefire-common-2.20.jar [ERROR] urls[2] = file:/home/jgallimore/.m2/repository/org/apache/maven/surefire/surefire-booter/2.20/surefire-booter-2.20.jar [ERROR] urls[3] = file:/home/jgallimore/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar [ERROR] urls[4] = file:/home/jgallimore/.m2/repository/junit/junit/4.12/junit-4.12.jar [ERROR] urls[5] = file:/home/jgallimore/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar [ERROR] urls[6] = file:/home/jgallimore/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar [ERROR] urls[7] = file:/home/jgallimore/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar [ERROR] urls[8] = file:/home/jgallimore/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar [ERROR] urls[9] = file:/home/jgallimore/.m2/repository/org/slf4j/jcl-over-slf4j/1.5.6/jcl-over-slf4j-1.5.6.jar [ERROR] urls[10] = file:/home/jgallimore/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar [ERROR] urls[11] = file:/home/jgallimore/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar [ERROR] urls[12] = file:/home/jgallimore/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar [ERROR] urls[13] = file:/home/jgallimore/.m2/repository/org/apache/commons/commons-lang3/3.1/commons-lang3-3.1.jar [ERROR] urls[14] = file:/home/jgallimore/.m2/repository/org/apache/maven/surefire/surefire-api/2.20/surefire-api-2.20.jar [ERROR] urls[15] = file:/home/jgallimore/.m2/repository/org/apache/maven/surefire/surefire-logger-api/2.20/surefire-logger-api-2.20.jar [ERROR] urls[16] = file:/home/jgallimore/.m2/repository/org/apache/maven/plugin-tools/maven-plugin-annotations/3.3/maven-plugin-annotations-3.3.jar [ERROR] Number of foreign imports: 1 [ERROR] import: Entry[import from realm ClassRealm[project>org.apache.tomee:tomee-project:8.0.5-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]] [ERROR] [ERROR] - [ERROR] : javax.xml.bind.JAXBException [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :apache-tomee ``` 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
[GitHub] [tomee] rzo1 commented on pull request #713: TOMEE-2324 - Remove Corba ORB APIs from Codebase
rzo1 commented on pull request #713: URL: https://github.com/apache/tomee/pull/713#issuecomment-727906568 Thanks for the update, John. 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
[GitHub] [tomee] jgallimore commented on pull request #713: TOMEE-2324 - Remove Corba ORB APIs from Codebase
jgallimore commented on pull request #713: URL: https://github.com/apache/tomee/pull/713#issuecomment-727906109 I ran into some issues, which may have been down to some other stuff checked into the repository. Now that's sorted, let me run it again. 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
[GitHub] [tomee] rzo1 commented on pull request #713: TOMEE-2324 - Remove Corba ORB APIs from Codebase
rzo1 commented on pull request #713: URL: https://github.com/apache/tomee/pull/713#issuecomment-727899314 > Thanks for doing this. I'll give this a run-through this morning. Any updates on it? :) 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
