Re: TomEE & Java 17
The easy fix is to replace the illegal access to - - add-opens and - - add-exports. The exception message includes which one is required. Em seg., 20 de set. de 2021 07:34, Zowalla, Richard < richard.zowa...@hs-heilbronn.de> escreveu: > I think that's the approach taken by the guys at deltaspike in Thomas' > link [1] (and the related PR in [2]). > > [1] https://issues.apache.org/jira/browse/DELTASPIKE-1432 > [2] https://github.com/apache/deltaspike/pull/119 > > Am Montag, dem 20.09.2021 um 11:09 +0100 schrieb Jonathan Gallimore: > > I had a very quick look - I wonder if we simply need to move to > > MethodHandles.Lookup.defineClass(): > > > https://docs.oracle.com/javase/9/docs/api/java/lang/invoke/MethodHandles.Lookup.html#defineClass-byte:A- > > in the LocalBeanProxyFactory. There's likely a couple of other > > libraries > > that TomEE uses that do similar things, such as OWB and OpenJPA, so > > we'll > > need to check that they do the right thing in Java 17 as well. > > > > Jon > > > > On Mon, Sep 20, 2021 at 9:08 AM Zowalla, Richard < > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > Hi ladies, > > > > > > I wanted to start a discussion about TomEE and its Java 17 > > > compatibility. > > > > > > I did some tests in one of our demo projects It looks like that " > > > --illegal-access=permit" was removed in Java 17, which leads to > > > some InaccessibleObjectException [1]. > > > > > > Does anybody know, if there are solutions / workarounds for it in > > > Java > > > 17 or do we need to fix it? If so: how? ;) > > > > > > I bet, that many other frameworks / containers will run in this > > > issue, > > > so maybe someone already thought about a possible solution? > > > Discussion > > > seems to be "hot" [2]. > > > > > > Gruss > > > Richard > > > > > > > > > [1] https://gist.github.com/rzo1/5c1d0724a700e262a2e2824ded9f32ab > > > [2] https://twitter.com/delabassee/status/1438446396865224705 > > > > > > > > > >
Why the indivial components didn't get certified yet?
Hello! I was taking a look at the progress of compliance of the Apache components, and I wonder why don't Myfaces, for instance, is certified for Jakarta EE 9 yet? The plan is only to certify all the individual components after TomEE gets certified? Thanks!
Re: [TCK] Servlet status
Hi all!
So, I couldn't take a look at the TomEE for a while.
>From what I recall I couldn't get any further because the annotation
scanning
wasn't looking for security annotations in Servlets, only EJBs.
If someone could continue the work would be great. I've spent some time on
it,
but as I couldn't progress, I guess I can learn from the solution.
Em seg., 4 de jan. de 2021 às 09:55, Jean-Louis Monteiro <
jlmonte...@tomitribe.com> escreveu:
> Hey Thiago,
>
> Happy new year.
> Wanted to check if you got any change to move something forward, or if you
> need something from us?
>
> Thanks
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Dec 16, 2020 at 6:51 PM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
> > In a meeting and about to get the kids for diner. I'll answer later.
> >
> > In regards to the debug, the deployment class does not run on the server.
> > Check out the runtest script. At the beginning, there are a couple of
> > flags you can use to debug the server, the javatest, the harness (ds, dj,
> > dh ...).
> > it gives the ports you can connect to.
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Dec 16, 2020 at 6:04 PM Thiago Henrique Hupner >
> > wrote:
> >
> >> Well, the AnnotationDeployer does in fact run on servlet classes,
> however
> >> it doesn't process the security
> >> annotations in the deploy method:
> >>
> >>
> https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/config/AnnotationDeployer.java#L1084
> >>
> >> I'll keep looking around.
> >>
> >> Thanks
> >>
> >> Em qua., 16 de dez. de 2020 às 13:48, Thiago Henrique Hupner <
> >> thi...@gmail.com> escreveu:
> >>
> >> > Hi.
> >> >
> >> > I tried to debug the DeploymentImpl however I wasn't able. Do you know
> >> if
> >> > this class is only used by the
> >> > full TCK run or if it used by single run?
> >> >
> >> > I'm running the TCK with:
> >> > ./runtests -sql skip -ds --web tomee-plume
> >> > com.sun.ts.tests.servlet.ee.spec.security.runAs
> >> > And attaching the debugger to port 5005.
> >> >
> >> > I also find something weird: looks like the AnnotationDeployer class
> is
> >> > not run on Servlet classes.
> >> > From what I can tell, only the EJBs are been scanned. The
> >> > com.sun.ts.tests.servlet.ee.spec.security.runAs.ServletTwo doesn't
> >> reach
> >> > there and the applications
> >> > doesn't know about the RunAs("Manager").
> >> >
> >> > About the DeploymentImpl probably I'll need to get more information to
> >> > understand how it works.
> >> > For now, I've applied a patch to the DeployerEjb:
> >> >
> >> > if (slash > 0) {
> >> >String moduleId = name.substring(0, slash);
> >> >// To remove ".war" from the module name
> >> >moduleId = moduleId.substring(0, moduleId.length() - 4);
> >> >name = name.substring(slash + 1);
> >> >module = modules.get(moduleId);
> >> > }
> >> >
> >> > Probably I'll revisit it before sending some official patch.
> >> >
> >> > Thanks!
> >> >
> >> > Em qua., 16 de dez. de 2020 às 10:39, Jean-Louis Monteiro <
> >> > jlmonte...@tomitribe.com> escreveu:
> >> >
> >> >> Hi Thiago,
> >> >>
> >> >> That is astonishing how deep you got in such a little amount of time.
> >> >> You have nothing to worry about or to be sorry about.
> >> >>
> >> >> We all truly appreciate the help.
> >> >>
> >> >> You are right on.
> >> >> Here are some pointers for debugging.
> >> >>
> >> >> Here is where we get notified by TCK stack about deployments and
> >> >> descriptors.
> >> >>
> >> >>
> >>
> https://github.com/apache/tomee-tck/blob/master/src/main/java/org/apache/openejb/cts/DeploymentImpl.java#L170
> >> >>
> >> >> L182, I added a hack the other day to support overriding the context
> >> from
> >> >> the sun descriptor.
> >>
Re: [TCK] Servlet status
Well, the AnnotationDeployer does in fact run on servlet classes, however
it doesn't process the security
annotations in the deploy method:
https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/config/AnnotationDeployer.java#L1084
I'll keep looking around.
Thanks
Em qua., 16 de dez. de 2020 às 13:48, Thiago Henrique Hupner <
thi...@gmail.com> escreveu:
> Hi.
>
> I tried to debug the DeploymentImpl however I wasn't able. Do you know if
> this class is only used by the
> full TCK run or if it used by single run?
>
> I'm running the TCK with:
> ./runtests -sql skip -ds --web tomee-plume
> com.sun.ts.tests.servlet.ee.spec.security.runAs
> And attaching the debugger to port 5005.
>
> I also find something weird: looks like the AnnotationDeployer class is
> not run on Servlet classes.
> From what I can tell, only the EJBs are been scanned. The
> com.sun.ts.tests.servlet.ee.spec.security.runAs.ServletTwo doesn't reach
> there and the applications
> doesn't know about the RunAs("Manager").
>
> About the DeploymentImpl probably I'll need to get more information to
> understand how it works.
> For now, I've applied a patch to the DeployerEjb:
>
> if (slash > 0) {
>String moduleId = name.substring(0, slash);
>// To remove ".war" from the module name
>moduleId = moduleId.substring(0, moduleId.length() - 4);
>name = name.substring(slash + 1);
>module = modules.get(moduleId);
> }
>
> Probably I'll revisit it before sending some official patch.
>
> Thanks!
>
> Em qua., 16 de dez. de 2020 às 10:39, Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> escreveu:
>
>> Hi Thiago,
>>
>> That is astonishing how deep you got in such a little amount of time.
>> You have nothing to worry about or to be sorry about.
>>
>> We all truly appreciate the help.
>>
>> You are right on.
>> Here are some pointers for debugging.
>>
>> Here is where we get notified by TCK stack about deployments and
>> descriptors.
>>
>> https://github.com/apache/tomee-tck/blob/master/src/main/java/org/apache/openejb/cts/DeploymentImpl.java#L170
>>
>> L182, I added a hack the other day to support overriding the context from
>> the sun descriptor.
>> I acknowledge it was a hack but changing the DeployerEjb is a bit tricky
>> and can break too many things
>> A solution would be to fork it in TomEE TCK and clean it up so we can
>> support all deployment descriptors for EAR, WAR packagings.
>>
>> We would use the TCK specific version to deploy and configure (finer).
>>
>> What do you think?
>>
>>
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Wed, Dec 16, 2020 at 12:14 PM Thiago Henrique Hupner > >
>> wrote:
>>
>> > Hi all!
>> >
>> > I started taking a look to get a feeling of the whole process.
>> > I guess I was able to configure the TCK because I'm able to use the
>> > "runtests" script and debug in my IDE.
>> >
>> > So, as far as I could tell, there isn't any processing of security for
>> any
>> > sun-*.xml.
>> >
>> > Another thing that I noticed is that the
>> > `webModule.getAltDDs().get("sun-web.xml");` is returning null. The
>> process
>> > of
>> > including the in the "altDDs"
>> (org.apache.openejb.assembler.DeployerEjb) is
>> > trying to find the module
>> > "servlet_ee_spec_security_runAs_second_module_web.war"
>> > while the correct (I guess) is
>> > "servlet_ee_spec_security_runAs_second_module_web" (because there's a
>> entry
>> > with this key).
>> >
>> > Sorry if I'm taking a lot of time to process all this information and
>> thank
>> > you for helping me.
>> >
>> > Em ter., 15 de dez. de 2020 às 12:41, Jonathan Gallimore <
>> > jonathan.gallim...@gmail.com> escreveu:
>> >
>> > > There's a similar issue for some of the JAX-RS tests as well which I
>> had
>> > > been meaning to tackle in the same way - if you have some joy with the
>> > > Servlet tests, you'll likely fix the JAX-RS tests too.
>> > >
>> > > Thanks for looking at this Thiago - let us know how you're getting on!
>> > >
>> > > Jon
>> > >
>> > > On Tue, Dec 15, 2020 at 1:02 PM Jean-Louis Monteiro <
>> > > jlmonte...@tomitribe.com> wrote:
>> >
Re: [TCK] Servlet status
Hi.
I tried to debug the DeploymentImpl however I wasn't able. Do you know if
this class is only used by the
full TCK run or if it used by single run?
I'm running the TCK with:
./runtests -sql skip -ds --web tomee-plume
com.sun.ts.tests.servlet.ee.spec.security.runAs
And attaching the debugger to port 5005.
I also find something weird: looks like the AnnotationDeployer class is not
run on Servlet classes.
>From what I can tell, only the EJBs are been scanned. The
com.sun.ts.tests.servlet.ee.spec.security.runAs.ServletTwo doesn't reach
there and the applications
doesn't know about the RunAs("Manager").
About the DeploymentImpl probably I'll need to get more information to
understand how it works.
For now, I've applied a patch to the DeployerEjb:
if (slash > 0) {
String moduleId = name.substring(0, slash);
// To remove ".war" from the module name
moduleId = moduleId.substring(0, moduleId.length() - 4);
name = name.substring(slash + 1);
module = modules.get(moduleId);
}
Probably I'll revisit it before sending some official patch.
Thanks!
Em qua., 16 de dez. de 2020 às 10:39, Jean-Louis Monteiro <
jlmonte...@tomitribe.com> escreveu:
> Hi Thiago,
>
> That is astonishing how deep you got in such a little amount of time.
> You have nothing to worry about or to be sorry about.
>
> We all truly appreciate the help.
>
> You are right on.
> Here are some pointers for debugging.
>
> Here is where we get notified by TCK stack about deployments and
> descriptors.
>
> https://github.com/apache/tomee-tck/blob/master/src/main/java/org/apache/openejb/cts/DeploymentImpl.java#L170
>
> L182, I added a hack the other day to support overriding the context from
> the sun descriptor.
> I acknowledge it was a hack but changing the DeployerEjb is a bit tricky
> and can break too many things
> A solution would be to fork it in TomEE TCK and clean it up so we can
> support all deployment descriptors for EAR, WAR packagings.
>
> We would use the TCK specific version to deploy and configure (finer).
>
> What do you think?
>
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Dec 16, 2020 at 12:14 PM Thiago Henrique Hupner
> wrote:
>
> > Hi all!
> >
> > I started taking a look to get a feeling of the whole process.
> > I guess I was able to configure the TCK because I'm able to use the
> > "runtests" script and debug in my IDE.
> >
> > So, as far as I could tell, there isn't any processing of security for
> any
> > sun-*.xml.
> >
> > Another thing that I noticed is that the
> > `webModule.getAltDDs().get("sun-web.xml");` is returning null. The
> process
> > of
> > including the in the "altDDs" (org.apache.openejb.assembler.DeployerEjb)
> is
> > trying to find the module
> > "servlet_ee_spec_security_runAs_second_module_web.war"
> > while the correct (I guess) is
> > "servlet_ee_spec_security_runAs_second_module_web" (because there's a
> entry
> > with this key).
> >
> > Sorry if I'm taking a lot of time to process all this information and
> thank
> > you for helping me.
> >
> > Em ter., 15 de dez. de 2020 às 12:41, Jonathan Gallimore <
> > jonathan.gallim...@gmail.com> escreveu:
> >
> > > There's a similar issue for some of the JAX-RS tests as well which I
> had
> > > been meaning to tackle in the same way - if you have some joy with the
> > > Servlet tests, you'll likely fix the JAX-RS tests too.
> > >
> > > Thanks for looking at this Thiago - let us know how you're getting on!
> > >
> > > Jon
> > >
> > > On Tue, Dec 15, 2020 at 1:02 PM Jean-Louis Monteiro <
> > > jlmonte...@tomitribe.com> wrote:
> > >
> > > > Hi Thiago,
> > > >
> > > > No the TCK setup is unfortunately a bit more complex.
> > > > You can have a look at the readme from this repo
> > > > https://github.com/apache/tomee-tck
> > > >
> > > > What I would recommend is either create a unit test in openejb-core
> to
> > > > reproduce the issue.
> > > > Or at least create an example (starting from
> > > examples/alternate-descriptors
> > > > is probably good).
> > > >
> > > > The TCK is very simple.
> > > > This is where you can find it
> > > >
> > > >
> > >
> >
> https://github.com/eclipse-ee4j/jakartaee-tck/tree/master/src/com/sun/ts/tests/servlet/ee/spec/security/runAs
> > > >
> > > > Basically S
Re: [TCK] Servlet status
Hi all!
I started taking a look to get a feeling of the whole process.
I guess I was able to configure the TCK because I'm able to use the
"runtests" script and debug in my IDE.
So, as far as I could tell, there isn't any processing of security for any
sun-*.xml.
Another thing that I noticed is that the
`webModule.getAltDDs().get("sun-web.xml");` is returning null. The process
of
including the in the "altDDs" (org.apache.openejb.assembler.DeployerEjb) is
trying to find the module
"servlet_ee_spec_security_runAs_second_module_web.war"
while the correct (I guess) is
"servlet_ee_spec_security_runAs_second_module_web" (because there's a entry
with this key).
Sorry if I'm taking a lot of time to process all this information and thank
you for helping me.
Em ter., 15 de dez. de 2020 às 12:41, Jonathan Gallimore <
jonathan.gallim...@gmail.com> escreveu:
> There's a similar issue for some of the JAX-RS tests as well which I had
> been meaning to tackle in the same way - if you have some joy with the
> Servlet tests, you'll likely fix the JAX-RS tests too.
>
> Thanks for looking at this Thiago - let us know how you're getting on!
>
> Jon
>
> On Tue, Dec 15, 2020 at 1:02 PM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
> > Hi Thiago,
> >
> > No the TCK setup is unfortunately a bit more complex.
> > You can have a look at the readme from this repo
> > https://github.com/apache/tomee-tck
> >
> > What I would recommend is either create a unit test in openejb-core to
> > reproduce the issue.
> > Or at least create an example (starting from
> examples/alternate-descriptors
> > is probably good).
> >
> > The TCK is very simple.
> > This is where you can find it
> >
> >
> https://github.com/eclipse-ee4j/jakartaee-tck/tree/master/src/com/sun/ts/tests/servlet/ee/spec/security/runAs
> >
> > Basically ServletTwo is secured and called with a user j2ee with
> > Administrator role.
> > It has @RunAs("Manager"), so it can call the EJB with Manager
> > @RolesAllowed.
> >
> > The goal is to map j2ee with javajoe which has Manager role.
> > Check out the comments for the following method
> >
> >
> https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/servlet/ee/spec/security/runAs/Client.java#L211
> >
> > If you want to go the junit simple test, have a look at
> >
> >
> https://github.com/apache/tomee/tree/master/container/openejb-core/src/test/java/org/apache/openejb/config
> > You can find a couple of Sun...Test files.
> >
> > The goal is pretty simple in essence.
> > In here
> >
> >
> https://github.com/apache/tomee/tree/master/container/openejb-jee/src/main/java/org/apache/openejb/jee
> > You have all descriptors supported.
> >
> > Under sun package, you will find deployment descriptors JAXB tree, for
> > instance to parse
> >
> >
> https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/servlet/ee/spec/security/runAs/servlet_ee_spec_security_runAs_second_module_web.war.sun-web.xml
> > The role mapping is here
> >
> >
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/sun/Servlet.java
> >
> > You need to convert to the JAXB tree under oejb3.
> > The role mapping is here
> >
> >
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/oejb3/RoleMapping.java
> >
> > Small trick to solve, for glassfish the mapping is done from servlet name
> > to principal.
> > For OpenEJB/TomEE the mapping is done from role to principal
> >
> > Hope it helps
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Tue, Dec 15, 2020 at 1:46 PM Thiago Henrique Hupner >
> > wrote:
> >
> > > I can have a look at the RunAs tests.
> > >
> > > I just want to know, if I make a change in the TomEE, using `mvn clean
> > > install` would be enough to the tomee-tck use the new jars or
> > > do I need to setup anything else?
> > >
> > > Thanks
> > >
> > > Em ter., 15 de dez. de 2020 às 08:16, Jean-Louis Monteiro <
> > > jlmonte...@tomitribe.com> escreveu:
> > >
> > > > Hi community,
> > > >
> > > > I was working on the Servlet, I I have been able to bring it down to
> > > >
> > > >
> > >
> >
> https://tck.work/tomee/tests?build=1607984842299=c
Re: [TCK] Servlet status
I can have a look at the RunAs tests. I just want to know, if I make a change in the TomEE, using `mvn clean install` would be enough to the tomee-tck use the new jars or do I need to setup anything else? Thanks Em ter., 15 de dez. de 2020 às 08:16, Jean-Louis Monteiro < jlmonte...@tomitribe.com> escreveu: > Hi community, > > I was working on the Servlet, I I have been able to bring it down to > > https://tck.work/tomee/tests?build=1607984842299=com.sun.ts.tests.servlet > > 22 remaining failures. > > Based on Tomcat's following page > https://cwiki.apache.org/confluence/display/TOMCAT/Servlet+TCK+4.0 > > I added some excludes for tests which were fix because of known bugs > See > > https://github.com/apache/tomee-tck/blob/master/src/test/resources/ts.jtx#L24 > > On the 22, we still have some pending tests as explained in the Tomcat > wiki. > I haven't excluded them because they aren't flagged as bugs on the TCK, so > until the challenge is accepted and fixed, we should leave them in my > opinion. > > I'm trying to get some of the permission fixed as well by adding the > security manager. > > >- com.sun.ts.tests.servlet.spec.security.clientcert.Client (1 >failure)--> JDK issue fixed with 1.8u221 - I already updated the >certificates because they were expired >- com.sun.ts.tests.servlet.ee.spec.security.permissiondd.Client (14 >failures) --> We need the security manager with Tomcat >- com.sun.ts.tests.servlet.ee.spec.security.runAs.Client (2 failures) >--> we need a role mapping so user can switch from j2ee to javajoe. We > do >support role mapping but with openejb-jar.xml (not standard way - each >container has its own). As the TCK provides Glassfish role mapping > already, >we should be able to easily pass this by just improving the > SunConversion >class to read and map the roles to our internal model. >- com.sun.ts.tests.servlet.api.javax_servlet.srevent.URLClient (1 >failure) >- com.sun.ts.tests.servlet.api.javax_servlet.asynccontext.URLClient (2 >failures) >- com.sun.ts.tests.servlet.spec.security.secbasic.Client (2 failures) >--> known. Under discussion > > If someone wants to take the RunAs, it's an easy one to do. I can provide > some guidance. > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com >
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 > rock, Thiago! > > Oh, we have another branch for the Jakarta EE 9 TCK here: > > - https://github.com/apache/tomee-tck/tree/jakartaee9-tck > > If you're up for pulling that commit over and submitting another PR, > awesome! Otherwise I'll do a cherry pick tomorrow. > > -David > > > > >> On Dec 8, 2020, at 4:36 PM, David Blevins > wrote: > >> > >> 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: > >> > >> - > https://github.com/apache/tomee-tck/blob/master/src/test/resources/testsuite.properties > >> > >> ...and fill out any variables that would otherwise have to be hardcoded > (versions in jar names, etc.). Then it overrides the ts.jte file that > comes with the TCK and that's the one that gets used. > >> > >> That said, there are still some hardcoded jar names, but... more > opportunities for contribution :) We build other paths here: > >> > >> - > https://github.com/apache/tomee-tck/blob/master/src/test/script/openejb/tck/commands/CommandSupport.groovy#L155 > >> > >> So the short answer is we can either do the work in the > testsuite.properties file or build the right path in initPaths and make the > generateTsJte function smart enough put it into the ts.jte. Or some > combination of both. > >> > >> Side note: if you start digging into these groovy files and have an > urge to refactor them go ahead :) We actually grabbed this setup from > Geronimo and it's only been minorly changed over the years. Any kind of > love is welcome. > >> > >> > >> -- > >> David Blevins > >> http://twitter.com/dblevins > >> http://www.tomitribe.com > >> > >>> On Dec 8, 2020, at 3:48 PM, Thiago Henrique Hupner > wrote: > >>> > >>> 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 included in the > >>> jakartaee-tck/endorsedlib/flow.jar. > >>> > >>> This jar has to be included in the java.endorsed.dirs property (but > only > >>> for JDK 8) or with -Xbootclasspath/a flag(to run with JDK 8 or higher). > >>> > >>> I guess the change must be in the ts.jte, but I couldn't figure out > where > >>> this file is in the current setup. > >>> > >>> Thanks > >> > > > >
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 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 only have the Servlet and Pages TCK in my > > machine. > > There'll be many people who will need help with the setup, so feel free to > be extra noisy and ask a lot of questions. All that will help improve the > documentation so more people can join in the fun. Here's what we have so > far: > > - https://github.com/apache/tomee-tck#getting-setup > > Meanwhile, you can get the test output and server logs from tck.work. > For example here are the test failures for > com.sun.ts.tests.servlet.spec.defaultcontextpath which has a table with > "Package" and "Test": > > - > https://tck.work/tomee/tests?path=com.sun.ts.tests.servlet.spec.defaultcontextpath=1607347669779=FAILED > > If you click the link under "Package" you get these server logs and Maven > output: > > - https://tck.work/tomee/api/build/file/1607347669779/247 > > If you click the link under "Test" you get the TCK test output: > > - https://tck.work/tomee/api/testlog/247/1607347937486 > > With that you've got the name of the test, all forms of server output and > the test output. It's enough to grab the test source and try and figure > out on which line the test is failing and what expectation isn't met. > People are always afraid of being too noisy and "bothering" others, but > honestly hitting the list with even those findings is a great start. It's > enough to start a conversation on what the fix might be and where it should > be (in the TCK or in TomEE). > > There are 300 failing tests, so if someone took even a small peak at each > one and posted some quick analysis of each one that'd be no small > contribution. On that note, there is a feature to help deal with the > volume of failures and focus on what might have the highest impact. Here's > a report of all the exceptions thrown by the failing Servlet tests and the > number of tests impacted: > > - > https://tck.work/tomee/issues?path=com.sun.ts.tests.servlet==1607347669779=FAILED > > Indeed, actually debugging a test to figure out what the fix is definitely > requires getting the TCK setup yourself. > > > > > And sure it will help me give a better view of the web platform and how > to > > set up things for Piranha in the future too :) > > > > One question I have is with respect to issuing a pull request: I should > > first open an issue at Jira then open a PR? This still confuses me a > little. > > First is hit the list with a short "I'm looking to hack on a PR for X, any > thoughts/tips before I start?" After that it doesn't really matter what > comes next PR or Issue. > > We used to use the Issues to automatically generate the changelog each > release. As long as we ensure there is a JIRA before we do the release, > that's the final deadline. Unfortunately, that system decayed due to > change in JIRA APIs over time and isn't being used currently and as a > result there is no changelog each release. There's a whole other > area/opportunity for contribution there. Sometimes I question the need for > JIRA anymore, but that's a whole other story. :) > > -David > > > Em ter., 8 de dez. de 2020 às 18:42, David Blevins < > david.blev...@gmail.com> > > escreveu: > > > >> 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 great place > to > >> dive in and help. In the earlier phases getting tests to pass is often, > >> "we need someone to create/integrate an implementation of X spec" which > is > >> definitely heavy work. > >> > >> At this stage the issues are more like, "the spec says this, we do that, > >> the TCK seems to do something entirely different." In this phase it's a > >> lot of reading test code, reading specifications to try and understand, > >> having disc
[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 included in the jakartaee-tck/endorsedlib/flow.jar. This jar has to be included in the java.endorsed.dirs property (but only for JDK 8) or with -Xbootclasspath/a flag(to run with JDK 8 or higher). I guess the change must be in the ts.jte, but I couldn't figure out where this file is in the current setup. Thanks
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 only have the Servlet and Pages TCK in my machine. And sure it will help me give a better view of the web platform and how to set up things for Piranha in the future too :) One question I have is with respect to issuing a pull request: I should first open an issue at Jira then open a PR? This still confuses me a little. Thanks! Em ter., 8 de dez. de 2020 às 18:42, David Blevins escreveu: > 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 great place to > dive in and help. In the earlier phases getting tests to pass is often, > "we need someone to create/integrate an implementation of X spec" which is > definitely heavy work. > > At this stage the issues are more like, "the spec says this, we do that, > the TCK seems to do something entirely different." In this phase it's a > lot of reading test code, reading specifications to try and understand, > having discussions here to get some consistent perspective then having > conversations with other people on the Jakarta EE side. > > It's one large learning opportunity for all of us, myself included. If > anyone is excited about potentially becoming an expert in Jakarta EE > through helping with the TCK, this is the phase to dig in. > > If this interests you, I recommend keeping an eye out for any threads with > the "[TCK]" prefix and asking questions to get more information and help > with the research. If you're feeling really aggressive, you can even find > a failing test, dig into the source code and see if you can understand what > the test is asking for that we aren't doing then post some details on what > you find (even if what you find is more questions -- that seems to be the > typical result). > > > -- > David Blevins > http://twitter.com/dblevins > http://www.tomitribe.com > > > On Oct 30, 2020, at 6:56 AM, Thiago Henrique Hupner > wrote: > > > > Hi all, > > > > Is there any place where we can see the current results of the TCK? > > > > If not, it would be possible to use the Github Actions to run it? > > > > Thanks > > > > Thiago > >
Jakarta TCK
Hi all, Is there any place where we can see the current results of the TCK? If not, it would be possible to use the Github Actions to run it? Thanks Thiago
Re: Documentation for TomEE 9
Pretty good job! Em qui., 9 de jul. de 2020 às 11:46, Daniel Dias Dos Santos < daniel.dias.analist...@gmail.com> escreveu: > Hello, > > Fantastic David : ) > > just a question, the website http://tomee.apache.org/docs.html does not > appear tomee 9.0. > > The link you provided is not available on the site for a new user to find. > > Em qui., 9 de jul. de 2020 às 00:26, David Blevins < > david.blev...@gmail.com> > escreveu: > > > I did some work in the site generator to add documentation for the TomEE > > 9.0.0-M1. > > > > First the results: > > > > - http://tomee.apache.org/tomee-9.0/pt/examples/ > > - http://tomee.apache.org/tomee-9.0/pt/examples/simple-rest.html > > - http://tomee.apache.org/tomee-9.0/examples/schedule-expression.html > > > > - http://tomee.apache.org/jakartaee-9.0/javadoc/ > > - > > > http://tomee.apache.org/jakartaee-9.0/javadoc/jakarta/ejb/SessionBean.html > > > > How this is done under the covers is that we: > > > > - Add a new "Source" for tomee-9.0 that points to `master` which is > still > > javax > > > > > https://github.com/apache/tomee-site-generator/blob/master/src/main/java/org/apache/tomee/website/Configuration.java#L101 > > > > - Then during processing if the Source is "tomee-9.0" we know it's > really > > a clone of `master`: > > > > > https://github.com/apache/tomee-site-generator/blob/master/src/main/java/org/apache/tomee/website/Jakartize.java#L45 > > > > - And we will do a javax-to-jakarta find/replace on all files we've > > cloned: > > > > > https://github.com/apache/tomee-site-generator/blob/master/src/main/java/org/apache/tomee/website/Jakartize.java#L61-L98 > > > > - Finally, add another new Source for "jakartaee-9.0" that aggregates > all > > the right EE4J branches to make javadocs > > > > > https://github.com/apache/tomee-site-generator/blob/master/src/main/java/org/apache/tomee/website/Configuration.java#L67-L90 > > > > That was basically it. > > > > Now we arguably have the largest set of Jakarta examples on the net :) > > > > I'd eventually like to do some more tooling (not related to the site) > that > > we can plug into our build and produce a jakarta version of our examples > > zip. Basically, this thing but migrated to the right namespace and > > completely functional: > > > > - > > http://archive.apache.org/dist/tomee/tomee-8.0.3/examples-8.0.3-src.zip > > > > Side note, we really need to link that on the download page and also add > > instructions on each example page. The old CMS version of the examples > > would automatically add instructions on how to checkout the examples > > source, navigate to the right directory and then run the example. > Another > > feature we really need to restore. > > > > > > -- > > David Blevins > > http://twitter.com/dblevins > > http://www.tomitribe.com > > > > >
TomEE builds with JDK 11+
Hello! I'd like to know if this topic still relevant to focus on. I know that Jakarta EE 9 requires to run on JDK 11, but I want to know if building the TomEE with JDK 11 is a problem to solve right now. I was searching around and I've found that were many attempts to do this, but I couldn't know why some commits were being reverted. If so, is there any branch that I should start with or should I start with the master branch? Kind regards
Re: [VOTE] Release Apache TomEE 9.0.0-M1 and Apache TomEE 8.0.3
+1 Em sex, 19 de jun de 2020 10:01, Jonathan Gallimore < jonathan.gallim...@gmail.com> escreveu: > Hi All, > > I am delighted to present a vote for Apache TomEE 9.0.0-M1 and Apache TomEE > 8.0.3. > > There's some background on this release here: > > https://lists.apache.org/thread.html/r1d89e3c1cd9dba9695e059c96efc8af0d68f18e40c4d4c688801db8d%40%3Cdev.tomee.apache.org%3E > > The key points here are: > > * TomEE 8.0.3 is essentially identical to TomEE 8.0.2, bar some changes to > examples. Release notes are below. > > * TomEE 9.0.0-M1 is a transformed version of TomEE 8.0.3, to shift TomEE > and all its dependencies from the javax to jakarta namespace. > > * If you're targeting Jakarta EE 8, use TomEE 8.0.3. If you would like to > try out Jakarta EE 9, with the new namespace, try TomEE 9.0.0-M1. If you > build the examples, for most of them you should get a `javax` version and a > `jakarta` version. Moviefun is a good app to use to play around. > > * TomEE 8.0.3 is production-ready. TomEE 9.0.0-M1 is a milestone. We'd love > you to try it, kick the tyres and provide feedback. There will likely be a > few milestone releases before we get to a production-ready 9.0.0. > > * We expect things to not work with the 9.0.0-M1 version. Feedback is > gratefully received, but will be addressed with subsequent releases. > Genuine show-stopper issues, such as legal issues, should be voted -1, but > bugs or functionality in the 9.0.0-M1 should not prevent this release going > ahead. If you have questions around this, please let us know. > > * Both versions are built from the same codebase, hence the single vote. > > * This vote includes the release of a patch plugin: > https://github.com/apache/tomee-patch-plugin, and one separate single > module to do the translation work for the jakarta version: > https://github.com/apache/tomee-jakarta. I'm expecting the > tomee-jakara repo to be removed and the module bought back under the tomee > tree when we can work out the build issues there. > > Maven Repo: > https://repository.apache.org/content/repositories/orgapachetomee-1172/ > > Binaries & Source: > https://dist.apache.org/repos/dist/dev/tomee/staging-1172/tomee-8.0.3/ > > Tags: > > > https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-project-8.0.3 > > https://gitbox.apache.org/repos/asf?p=tomee-patch-plugin.git;a=tag;h=refs/tags/tomee-patch-parent-0.1 > > https://gitbox.apache.org/repos/asf?p=tomee-jakarta.git;a=tag;h=refs/tags/apache-tomee-9.0.0-M1 > > Release notes: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12348219 > > Please VOTE: > > [+1] Yes, release it > [+0] Not fussed > [-1] Don't release, there's a showstopper (please specify what the > showstopper is) > > Vote will be open for 72 hours. > > Here is my +1. > > Thanks > > Jon >
Re: Initial Jakarta EE 9 snapshot TCK results (90%-ish)
+1 Em sex., 19 de jun. de 2020 às 00:14, David Blevins escreveu: > I've done a run in EC2 and here are the results I'm getting with the > potential TomEE 9.0.0-M1 binaries. > > If you didn't read the 100+ emails in the last week, these binaries are > created by taking TomEE 8.0.3-SNAPSHOT and running through the bytecode > transformation tools we've been working on (Eclipse Transformer and TomEE > Patch Plugin) to change all the code that references `javax` to instead > reference `jakarta`. All this is done in the TomEE master branch. We're > hoping this means we can stay focused on TomEE 8 / Jakarta EE 8 while > getting Jakarta EE 9 compliance for free (no having to maintain two > branches for code that only differs by namespace). > > Enough of that, now the data: > > # Overall > > PASSED 23843 91% > FAILED2133 8% > TOTAL25976 > > > # Breakdown by Section > > section totalpassed failed percent > ejb30 2120 1780 340 83% > ejb32 801 675 126 84% > el 147 1461 99% > jaspic 68 4 64 5% > jaxrs 2417 2229 188 92% > jpa 10071 9932 139 98% > jsf5419 5252 167 96% > jsonb 236 224 12 94% > jsonp 744 708 36 95% > jsp 711 676 35 95% > jstl524 453 71 86% > jta 195 141 54 72% > securityapi 86 1 85 1% > servlet1698 1622 76 95% > websocket 739 0 739 0% > > > Bear in mind we don't actually know if anyone can pass the Jakarta EE 9 > TCK yet. With that in mind, I'd say these results are astronomically good. > > Given how behind we've been in the last few years I think it would be > pretty awesome to hustle to get a release up for vote ASAP so we can have > binaries people can try in time for the Jakarta EE 9 Milestone release > Tuesday morning. > > With 72 hours to vote and 24 hours for mirrors to sync, if we rolled > binaries in the next 12 hours we could just make. > > If everyone bears in mind these two things, I think we can make it: > > 1. Any release we roll can immediately be fixed in a subsequent > release if there's a flaw; there's no time for rerolls. We could do > another release next week if we wanted. > > 2. Any discussion we want to have on how a Jakarta EE 9 effort > should go is still on the table. We can change literally anything > for potential future releases. Nothing is set in stone. > > > That said, let's give the world a taste of awesome. > > > -David > > > > > > >
Re: Possible help in Jakarta EE 8 TCK (Re: How can I help ?)
Are we focusing on the full profile or the web profile for now? Em seg., 15 de jun. de 2020 às 21:00, David Blevins escreveu: > > On Jun 15, 2020, at 4:34 PM, Helber Belmiro > wrote: > > > > Hi David. > > > > Sounds nice to me. > > But I’ll have to start with baby steps and certainly will need help. I > never actually ran any TCK. It’s the first time I’m trying. > > As you said in another email the documentation might be outdated, so I > guess it is a good place to start. > > Agree completely. I think we're all at the same stage :) Many of us were > heavy into running the TCK in 2010 and 2011, but Apache lost access to the > TCK shortly after, so this is really the first time any of us have had much > of a chance to dig in for a very long time. > > So it's baby steps for all of us :) > > I'll be trying to run the EE 9 TCK, which might not even be working yet. > It will probably be painful :) > > Brothers in arms. > > > -David > > >> On 15 Jun 2020, at 16:05, David Blevins > wrote: > >> > >>> On Jun 14, 2020, at 5:20 AM, Evaldo Junior > wrote: > >>> > >>> I am Developer, i have used different applications servers, among them > the > >>> Apache Tomcat, during many years. > >>> I have interested in contribute to JAX-RS module to TomEE. > >>> I want to contribute to TomEE project, i hope to start with simple > things. > >>> I can start to contribute in documentation of the project, with the > >>> translations, english to portuguese. > >> > >> Hi Evaldo! > >> > >> Are you possibly interested in teaming up with Helber to lead the > charge on some Jakarta EE 8 TCK work? One it's up and running you could > focus on the JAX-RS section of the TCK. > >> > >> Our overall status in this regard is this has seen little to no > attention since August, yet we have people showing up regularly offering to > help. > >> > >> What we need is a couple people to dig into this area and put their > minds to learning how to do it themselves, then to helping others do it > too; responding to "how can I help" emails with "work with us on the tck, > here's how." > >> > >> It's a no-fail task as easily there've been over 50 people offer to > help that we've not been able to get successfully enabled to help, so > honestly and truly any improvement is seriously impactful. Perfection is > impossible, any step forward is a good one. > >> > >> Does this sound like fun? > >> > >> Helber, what do you think? > >> > >> Anyone else think this sounds exciting? > >> > >> > >> -David > >> > >> > >> > >> > > > >
Re: TomEE Security API implementation
I'd like to run the TCK on my machine, is there any place where I can find how to do it? Em qua., 10 de jun. de 2020 às 14:47, Jean-Louis Monteiro < jlmonte...@tomitribe.com> escreveu: > Hey Thiago, > > Aside from JASPIC and SecurityAPI which are close to zero. > There is JAXRS and JTA which are around 50% > > Other specs are close to 100% coverage, so it's really a few edge cases to > fix. > JAX RS might be a good one to pick because I think it's more an infra/setup > issue in the TCK project. > We rely on CXF and we should not be this far. > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Wed, Jun 10, 2020 at 2:47 PM Thiago Henrique Hupner > wrote: > > > Besides the Security API, are there more components that need to be > > implemented to certify the TomEE? > > > > Em qua., 10 de jun. de 2020 às 09:43, Jean-Louis MONTEIRO < > > jeano...@gmail.com> escreveu: > > > > > Hello community, > > > > > > As part of the TCK work to certify TomEE, I started a few weeks ago to > > move > > > on with our Security API implementation. > > > > > > I pushed my latest changes to https://github.com/apache/tomee/pull/658 > > > > > > If someone wants to help, there is enough work to do ;-) > > > For a few days I won't be able to work on it. Back next week. > > > > > > So far we are halfway with Jakarta TCK. > > > > > > Completed running 86 tests (0:04:29.583): > > > > > > Passed: 44 > > > Failed: 42 > > > Errors: 0 > > > > > > LDAP is about 20 tests and the IdentityStore is for the moment wired > but > > > empty. > > > > > > -- > > > Jean-Louis > > > > > >
Re: TomEE Security API implementation
Besides the Security API, are there more components that need to be implemented to certify the TomEE? Em qua., 10 de jun. de 2020 às 09:43, Jean-Louis MONTEIRO < jeano...@gmail.com> escreveu: > Hello community, > > As part of the TCK work to certify TomEE, I started a few weeks ago to move > on with our Security API implementation. > > I pushed my latest changes to https://github.com/apache/tomee/pull/658 > > If someone wants to help, there is enough work to do ;-) > For a few days I won't be able to work on it. Back next week. > > So far we are halfway with Jakarta TCK. > > Completed running 86 tests (0:04:29.583): > > Passed: 44 > Failed: 42 > Errors: 0 > > LDAP is about 20 tests and the IdentityStore is for the moment wired but > empty. > > -- > Jean-Louis >
Re: [VOTE] Release TomEE 8.0.2
+1 Em sex., 22 de mai. de 2020 às 13:17, Jonathan Gallimore < jonathan.gallim...@gmail.com> escreveu: > Here's my +1 > > On Thu, May 14, 2020 at 2:27 PM Jonathan Gallimore < > jonathan.gallim...@gmail.com> wrote: > > > Hi All, > > > > Here's a third attempt at releasing of TomEE 8.0.2. Please can you take a > > careful look, review, test and provide feedback. > > > > Maven Repo: > > https://repository.apache.org/content/repositories/orgapachetomee-1168 > > > > Binaries & Source: > > https://dist.apache.org/repos/dist/dev/tomee/staging-1168/tomee-8.0.2 > > > > Tag: > > > > > > > https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-8.0.2 > > > > Release notes: > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12346650 > > > > Please VOTE: > > > > [+1] Yes, release it > > [+0] Not fussed > > [-1] Don't release, there's a showstopper (please specify what the > > showstopper is) > > > > Vote will be open for 72 hours or as needed. > > > > Thanks > > > > Jon > > >
Re: [VOTE] Move javaee-api to Git.
+1 Em qui., 30 de abr. de 2020 às 08:14, Daniel Dias Dos Santos < daniel.dias.analist...@gmail.com> escreveu: > +1 > -- > > *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 qui., 30 de abr. de 2020 às 07:52, Daniel "soro" Cunha < > daniels...@apache.org> escreveu: > > > +1 > > > > -- > > Daniel "soro" Cunha > > https://twitter.com/dvlc_ > > https://www.linkedin.com/in/danielvlcunha/ > > > > > On Apr 29, 2020, at 7:56 PM, David Jencks > > wrote: > > > > > > +1 > > > David Jencks > > > > > >> On Apr 29, 2020, at 2:50 PM, Jonathan Gallimore < > > jonathan.gallim...@gmail.com> wrote: > > >> > > >> +1 > > >> > > >> On Wed, Apr 29, 2020 at 10:40 PM Cesar Hernandez < > cesargu...@gmail.com> > > >> wrote: > > >> > > >>> Hi, > > >>> > > >>> As a follow up from the `Javax -> Jakarta rename` thread [1] > > >>> I would like to propose moving the existing SVN javaee-api repo [2] > to > > >>> Git[3] to enable wider visibility and collaboration either via GitHub > > or > > >>> gitbox.apache.org. > > >>> > > >>> I will create the Apache JIRA Infra migration ticket after the vote > has > > >>> passed. > > >>> > > >>> [ ] +1 approve the release move javaee-api repo to Git > > >>> [ ] +0 no opinion > > >>> [ ] -1 disapprove (and reason why) > > >>> > > >>> [1] > > >>> > > >>> > > > https://lists.apache.org/thread.html/refb945e599cad66d8508a540fa5801fd2b04682424e9e29b4e6dd7b4%40%3Cdev.tomee.apache.org%3E > > >>> [2] https://svn.apache.org/repos/asf/tomee/javaee-api/ > > >>> [3] https://gitbox.apache.org/ > > >>> -- > > >>> Atentamente: > > >>> César Hernández. > > >>> > > > > > > > >
Re: How can I help?
Hello! I tried both approaches (from Jonathan and Daniel), but I'm still having a hard time to figure it out to get it to work. According to my search, it's because the surefire plugin isn't including the JAXB API in its classpath, thus the Exception (java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException) is being thrown during the execution of integration tests. I'm not sure in how to proceed right now. Thank you Em seg., 30 de mar. de 2020 às 11:00, Jonathan Gallimore < jonathan.gallim...@gmail.com> escreveu: > > I don't know where to add the JAXB dependencies to get it in the runtime, > > any help would be appreciated. > > Take a look at the pom here - > https://github.com/apache/tomee/tree/master/boms/jaxb-runtime - that might > help. > > > I've tested the TomEE with Java 14 and it worked well. > > But I know that I haven't tested enough and I probably would be more > > confident > > about the status if I could run the tests that exist in the build of > TomEE. > > I think we have a config for buildbot that builds with Java 8 and runs the > tests with Java 11. Let me see if we can dig that out. > > Thanks for looking at this and for the writeup - that's really helpful! > > Jon > > On Mon, Mar 30, 2020 at 2:38 PM Thiago Henrique Hupner > wrote: > > > Hello! > > > > I've tested the TomEE with Java 14 and it worked well. > > But I know that I haven't tested enough and I probably would be more > > confident > > about the status if I could run the tests that exist in the build of > TomEE. > > > > I have started building with Java 14 and I'd like to point things that > > happened: > > > > * I have to include both JBoss RMI API / JacORB dependencies; > > * I think the agent isn't working. I get a lot of > > "java.lang.IllegalStateException: Unable to initialize agent" > > * I stuck in the integration test of TomEE: > >[INFO] --- maven-failsafe-plugin:2.20:integration-test (default) @ > > apache-tomee --- > >[WARNING] Error injecting: > > org.apache.maven.plugin.failsafe.IntegrationTestMojo > >java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException > > > > I don't know where to add the JAXB dependencies to get it in the runtime, > > any help would be appreciated. > > > > Thank you > > > > > > Em sex., 27 de mar. de 2020 às 13:49, Jonathan Gallimore < > > jonathan.gallim...@gmail.com> escreveu: > > > > > Hi Thiago! > > > > > > Welcome, and thanks for introducing yourself. Work on Java 14 support > > would > > > be fantastic. Some initial steps I'd suggest are: > > > > > > * Try running a current build on Java 14, and report issues you run > into > > > here. > > > * TomEE and a number of is components (OpenJPA, OpenWebBeans) use > > > xbean-asm, which may require an update: > > > https://github.com/apache/geronimo-xbean, so you may need to provide > > > patches to OpenJPA and OWB as well as TomEE. > > > > > > Getting TomEE to build with JDK14 will likely be more difficult, but by > > > all means give it a shot. I'd be inclined to get a view on the current > > > runtime status first. Please do feel welcome to ask questions and chat > on > > > the list. > > > > > > Cheers! > > > > > > Jon > > > > > > On Fri, Mar 27, 2020 at 2:48 PM Thiago Henrique Hupner < > thi...@gmail.com > > > > > > wrote: > > > > > > > Hello! > > > > > > > > I'm Thiago and I'd like to contribute with TomEE. > > > > I'm from Brazil and I'd like to help with the Java 14 support. > > > > > > > > Yours sincerely, > > > > Thiago > > > > > > > > > >
Re: How can I help?
Hello! I've tested the TomEE with Java 14 and it worked well. But I know that I haven't tested enough and I probably would be more confident about the status if I could run the tests that exist in the build of TomEE. I have started building with Java 14 and I'd like to point things that happened: * I have to include both JBoss RMI API / JacORB dependencies; * I think the agent isn't working. I get a lot of "java.lang.IllegalStateException: Unable to initialize agent" * I stuck in the integration test of TomEE: [INFO] --- maven-failsafe-plugin:2.20:integration-test (default) @ apache-tomee --- [WARNING] Error injecting: org.apache.maven.plugin.failsafe.IntegrationTestMojo java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException I don't know where to add the JAXB dependencies to get it in the runtime, any help would be appreciated. Thank you Em sex., 27 de mar. de 2020 às 13:49, Jonathan Gallimore < jonathan.gallim...@gmail.com> escreveu: > Hi Thiago! > > Welcome, and thanks for introducing yourself. Work on Java 14 support would > be fantastic. Some initial steps I'd suggest are: > > * Try running a current build on Java 14, and report issues you run into > here. > * TomEE and a number of is components (OpenJPA, OpenWebBeans) use > xbean-asm, which may require an update: > https://github.com/apache/geronimo-xbean, so you may need to provide > patches to OpenJPA and OWB as well as TomEE. > > Getting TomEE to build with JDK14 will likely be more difficult, but by > all means give it a shot. I'd be inclined to get a view on the current > runtime status first. Please do feel welcome to ask questions and chat on > the list. > > Cheers! > > Jon > > On Fri, Mar 27, 2020 at 2:48 PM Thiago Henrique Hupner > wrote: > > > Hello! > > > > I'm Thiago and I'd like to contribute with TomEE. > > I'm from Brazil and I'd like to help with the Java 14 support. > > > > Yours sincerely, > > Thiago > > >
How can I help?
Hello! I'm Thiago and I'd like to contribute with TomEE. I'm from Brazil and I'd like to help with the Java 14 support. Yours sincerely, Thiago
