Doubt translation Spanish

I have a doubt about the translation in spanish language, for the translation in portguese exists in the Jira a master task, Translate examples into Portuguese [Main Task], follow the link https://issues.apache.org/jira/browse/TOMEE-2473. The new

Re: [TCK] Servlet - Server push

Merged! What an amazing end to the Jakarta EE 9 release day :) -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com > On Dec 8, 2020, at 5:18 PM, Thiago Henrique Hupner wrote: > > Sure! I'll do right away > > Em ter., 8 de dez. de 2020 às 22:17, David Blevins > escreveu:

[GitHub] [tomee-tck] dblevins merged pull request #14: Add the endorsed.lib from TCK to run the client

dblevins merged pull request #14: URL: https://github.com/apache/tomee-tck/pull/14 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

[GitHub] [tomee-tck] Thihup opened a new pull request #14: Add the endorsed.lib from TCK to run the client

Thihup opened a new pull request #14: URL: https://github.com/apache/tomee-tck/pull/14 The Servlet server push tests uses the flow.jar to make the HTTP/2 requests. However, as this jar add classes to java namespace, it has to be added to as endorsed lib

Re: [TCK] Servlet - Server push

Sure! I'll do right away Em ter., 8 de dez. de 2020 às 22:17, David Blevins escreveu: > > On Dec 8, 2020, at 5:07 PM, David Blevins > wrote: > > > > PR merged :) > > > > - https://github.com/apache/tomee-tck/pull/13 > > > > Thank you much, Thiago! So amazing to see this kind of activity. You

Re: [TCK] Servlet - Server push

PR merged :) - https://github.com/apache/tomee-tck/pull/13 Thank you much, Thiago! So amazing to see this kind of activity. You rock, Thiago! -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com > On Dec 8, 2020, at 4:36 PM, David Blevins wrote: > > Wow, I did not

[GitHub] [tomee-tck] dblevins commented on pull request #13: Add the endorsed.lib from TCK to run the client

dblevins commented on pull request #13: URL: https://github.com/apache/tomee-tck/pull/13#issuecomment-741365220 Perfect!! This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [tomee-tck] Thihup commented on pull request #13: Add the endorsed.lib from TCK to run the client

Thihup commented on pull request #13: URL: https://github.com/apache/tomee-tck/pull/13#issuecomment-741355011 With this change: ``` ./runtests --web tomee-plume com.sun.ts.tests.servlet.spec.serverpush 1/-0/?0 -

[GitHub] [tomee-tck] Thihup opened a new pull request #13: Add the endorsed.lib from TCK to run the client

Thihup opened a new pull request #13: URL: https://github.com/apache/tomee-tck/pull/13 The Servlet server push tests uses the flow.jar to make the HTTP/2 requests. However, as this jar add classes to java namespace, it has to be added to as endorsed lib

Re: [TCK] Servlet - Server push

Wow, I did not expect to get an email like this so fast :) It's awesome. We build the ts.jte file dynamically in Groovy here: - https://github.com/apache/tomee-tck/blob/master/src/test/script/openejb/tck/commands/SetupCommand.groovy#L37 That code is basically there to take this input file:

Re: Jakarta TCK

Thanks! :) Em ter., 8 de dez. de 2020 às 20:34, David Blevins escreveu: > > On Dec 8, 2020, at 2:12 PM, Thiago Henrique Hupner > wrote: > > > > Hey David! > > > > Good to be remembered ;) > > :) > > > Thanks for the link. > > > > I've been contributing to the Piranha server lately helping to

[TCK] Servlet - Server push

Hi all! I did some looking and most of the server push tests are failing because the TCK client is failing to startup correctly. https://tck.work/tomee/api/testlog/276/1607111275890 This is happening because in the command line to run the client is not specified the flow.jar library that is

Re: Jakarta TCK

> On Dec 8, 2020, at 2:12 PM, Thiago Henrique Hupner wrote: > > Hey David! > > Good to be remembered ;) :) > Thanks for the link. > > I've been contributing to the Piranha server lately helping to pass the > Servlet TCK, so I guess I've got some experience with the TCK. > I really would like

Re: Jakarta TCK

Hey David! Good to be remembered ;) Thanks for the link. I've been contributing to the Piranha server lately helping to pass the Servlet TCK, so I guess I've got some experience with the TCK. I really would like to help. Probably I'll need some help setting up the full TCK environment because I

Re: Jakarta TCK

Hey Thiago! Thought I saw your name on today's JakartaOne Livestream. Here's a site that has the latest TomEE TCK results: - https://tck.work/tomee/projects We're at the stage where we're down to the last few hundred failures. This is where things get really detailed and is actually a

Re: How can I help?

Hola, Jorge! We have a great variety of things that the project needs: - help organizing the documentation - examples translated to Spanish - new examples for various MicroProfile and Jakarta EE apis - help passing the Jakarta EE 8 and 9 TCKs - help helping people who ask how they can help

Re: [TCK] IvmContext: Naming context close

> On Dec 8, 2020, at 2:04 AM, Jean-Louis Monteiro > wrote: > > Hi all, > > Yesterday I worked on the EJB 3 failures related to naming context. > I realized we were failing on a couple of tests and I've been able to fix > them with configuration. > > But the last one was regarding the close

Re: Limitations in Arquillian Embedded and Application Composer

Hi Juan, Documentation these features would be a great contribution. If you're interested in helping there, let's talk through what issues you see and you can contribute some documentation. If there are issues that need to be fixed and are interested in code contribution opportunities too, I

Re: [TCK] JSTL x:transform failures

I fear slightly less the extra issues that reverting to xalan might bring to XSLT / XML Transform features than the impacts of searializer.jar reintroduction. Indeed, when xalan.jar was removed, we had to remove searializer.jar as well from our web apps otherwise our webapps failed to start. The

Re: [TCK] JSTL x:transform failures

I tried adding back Xalan and applying the patch mentioned. I double checked the version of Xalan by default in the JDK (shaded under com.sun.org.apache ...). It's a Xalan 2.7.2 so that's the one I used as a starting point. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro

Re: [TCK] JSTL x:transform failures

We're looking to pass the TCK for both EE8 and EE9. This change would be needed on both counts. Both TomEE 8 and 9 use the exact same codebase, and one is simply a translation of the other into the jakarta. namespace. I understand your view, and also the issue you experienced with the Japanese

Re: [TCK] JSTL x:transform failures

In that case, could xalan-reintroduction be limited to TomEE 9.x ? What's the urge with TomEE 8.x vs. impacts risks ? Le mar. 8 déc. 2020 à 14:39, Jonathan Gallimore a écrit : > > We fixed a specific issue by removing Xalan, but without realizing the > impact on JSTL. We'll need to fix this one

Re: Drop in TomEE WAR

That's awesome, thanks Rod. I'll keep an eye for the mail on the users list. Jon On Tue, Dec 8, 2020 at 1:28 PM Jenkins, Rodney J (Rod) < jenki...@nationwide.com> wrote: > Jon, > > Thank you for the response. I did not jump straight to bug. I figured I > missed something in the building of

Re: [TCK] JSTL x:transform failures

We fixed a specific issue by removing Xalan, but without realizing the impact on JSTL. We'll need to fix this one way or another. There's a couple of options: 1. Re-introduce Xalan and patch it (which seems to be the common approach across the app servers) 2. Implement what we need with JAXP. At

Re: Drop in TomEE WAR

Jon, Thank you for the response. I did not jump straight to bug. I figured I missed something in the building of our image. I have passed along the request for the exception and a reproducer. We cannot share the actual code base, but I did ask for something that will reproduce the error.

Re: [TCK] JSTL x:transform failures

ForEachTag's class comment says "Implementation of ; tag using low-level Xalan API." Isn't there a way to emulate that with simple JAXP instead of re-introducing the huge & unmaintained dependency on Xalan ? As far as I remember, not only xalan.jar, but also serializer.jar had to be removed (maybe

Re: [TCK] JSTL x:transform failures

Quick update on this one ... Tomcat Taglib has a direct dependency on XParthContext https://github.com/apache/tomcat-taglibs-standard/blob/master/impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/ForEachTag.java This is available in Xalan So at this point, we have an issue in TomEE

Re: [TCK] JSTL x:transform failures

Thanks. Alexandre also replied on the ticket so I'll revert and see if I can find a better solution. Thanks guys -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Dec 8, 2020 at 11:21 AM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > Yes -

[GitHub] [tomee] rzo1 commented on pull request #723: TOMEE-2933 - Updates to eclipselink 2.7.7

rzo1 commented on pull request #723: URL: https://github.com/apache/tomee/pull/723#issuecomment-740534565 Fixed with https://github.com/apache/tomee/commit/c38f60e78e7cef40fb7d1b61962d5cffc756de2e This is an automated

[GitHub] [tomee] rzo1 closed pull request #723: TOMEE-2933 - Updates to eclipselink 2.7.7

rzo1 closed pull request #723: URL: https://github.com/apache/tomee/pull/723 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

[GitHub] [tomee] rzo1 edited a comment on pull request #723: TOMEE-2933 - Updates to eclipselink 2.7.7

rzo1 edited a comment on pull request #723: URL: https://github.com/apache/tomee/pull/723#issuecomment-740529651 Hi @jeanouii I think, we did TOMEE-2933 twice :smile: Nevertheless, the changes related to `cxf-rt-rs-sse` here might be worth a check. Otherwise: Please close

[GitHub] [tomee] rzo1 commented on pull request #723: TOMEE-2933 - Updates to eclipselink 2.7.7

rzo1 commented on pull request #723: URL: https://github.com/apache/tomee/pull/723#issuecomment-740529651 Hi @jeanouii I think, we did TOMEE-2933 twice :+1: Nevertheless, the changes related to `cxf-rt-rs-sse` here might be worth a check. Otherwise: Please close this PR.

Re: [TCK] JSTL x:transform failures

Yes - there's a bug with parsing Japanese characters with Xalan. It also looks like its not maintained any more. I was under the impression that the Transformer functionality was part of the JDK, so I'm curious as to what is missing. I'll have a look at that failing test. Looks like we're missing

[TCK] IvmContext: Naming context close

Hi all, Yesterday I worked on the EJB 3 failures related to naming context. I realized we were failing on a couple of tests and I've been able to fix them with configuration. But the last one was regarding the close operation. Specification says 10.4.4. Container Provider Responsibility > > The

[TCK] JSTL x:transform failures

Hi, Been looking at the JSTL failures http://ec2-54-173-218-40.compute-1.amazonaws.com:17171/tests?path=com.sun.ts.tests.jstl=1607347669779=FAILED I realized that Xalan is missing from our distribution. Looks like it's been removed about a year ago.