You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Zoltán Tichov <zo...@gmail.com> on 2022/04/23 18:21:47 UTC
How can I help?
Hi!
I live in Hungary. I am working at an IT company as a software developer, I
develop java
webapps with jsf (PrimeFaces) and microservice like apps without any
container technology
and Oracle database.
We want to switch to jakarta ee 9 at the company, but unfortunately we ran
into problems with tomee 9 and I would like to contribute to fixing these
bugs and possibly improving tomee jakarta 10. (I'm sorry to read on another
tomee mailing list, that you had to skip jakarta ee 8 and 9 compliance
entirely)
I use java 11 and netbeans on windows 10. If we don't have to, we don't
want to use another app server because we've been using tomee since 1.7.3.
Best regards: Zoltán Tichov
Re: TCK Work - Smoothing the path (was Re: How can I help?)
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
I slightly increased the default stack size limit of the forked test
jvm in the related groovy script. It now works with Java 11 too.
To summarize: The documentation is updated and setting up the EE9.1 TCK
is quite easy. It basically boils down to:
(0) Ensure to have Maven and Java (11/14).
(1) Run on a Linux / Mac OS system.
(2) Adjust the settings.xml according to the template
(3) Run the setup script (only oncE)
(4) Check that everything is available
(5) Add the TCK install into a local git repository to reset easily
without delete & extract it again and again (as a TCK run modifies the
isntallation)
(6) Run the TCK and have fun.
Nevertheless, we need to fix the javamail (javax vs jakarta) thing
first, but afterwards any new volunteer can happily start TCK work.
Gruß
Richard
Am Dienstag, dem 26.04.2022 um 18:34 +0000 schrieb Zowalla, Richard:
> Thanks & You are right! Running with JDK 14 works.
>
> JDK 17 has some issues with illegal access within the groovy code
> used.
>
> With JDK 14 I am hitting the Javamail issue - so the setup procedere
> basically works. That are good news.
>
> Gruß
> Richard
>
>
> Am Dienstag, dem 26.04.2022 um 19:48 +0200 schrieb Jean-Louis
> Monteiro:
> > Sorry for the late reply.
> > I managed to reproduce your issue. It does not seem to be a regular
> > stackoverflow (loop without exit condition).
> > Debugging the code with some additional traces, it looks like we
> > are
> > loading jar after jar and the stack isn't big enough to handle it
> > in
> > Java
> > 11.
> >
> > I moved to a newer JDK like 14 or 17 and it worked.
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Tue, Apr 26, 2022 at 7:42 PM Zowalla, Richard <
> > richard.zowalla@hs-heilbronn.de> wrote:
> >
> > > It looks like the SQL is not the real issue here - although it is
> > > a
> > > bit
> > > confusing because the select statements look ok to me.
> > >
> > > However, after same additional digging / fiddling arround, I am
> > > at
> > > a
> > > point, there the JVM for the tests does not startup due to an
> > > StackOverflowError [1].
> > >
> > > I tried remote debugging via "-dj" but have no glue why I am
> > > running to
> > > this StackOverflowError during the "ant.java(...)" call in the
> > > related
> > > groovy command. I bet, that I miss a little detail - so happy to
> > > any
> > > additional input ;)
> > >
> > > Gruß
> > > R
> > >
> > >
> > > [1] https://gist.github.com/rzo1/0af90723dc0c6689a6f7d7bae9d2e8da
> > >
> > >
> > > Am Dienstag, dem 26.04.2022 um 09:59 +0000 schrieb Zowalla,
> > > Richard:
> > > > Hi,
> > > >
> > > > I changed the script pointing to the released ee9.1 tck now and
> > > > updated
> > > > the README accordingly. If the instructions are followed
> > > > carefully,
> > > > it
> > > > will lead to a fresh installation.
> > > >
> > > > In the process, I noticed, that Glassfish 6.0.0 isn't available
> > > > anymore
> > > > and is replaced by 6.2.5 - JL mentioned on Slack, that 6.2.5
> > > > should
> > > > also work.
> > > >
> > > > I think, that we do not really need a public git repository.
> > > > Setting
> > > > it
> > > > up with the script is really straight forward. However, putting
> > > > the
> > > > TCK
> > > > installation into a local git repository makes totally sense in
> > > > order
> > > > to avoid delete / unpack cycles due to the modifications on the
> > > > installation, if the TCK is run.
> > > >
> > > > I added some instructions in the README.
> > > >
> > > > Currently, I am struggling with
> > > >
> > > > [ERROR] java.sql.SQLSyntaxErrorException: Syntax error:
> > > > Encountered
> > > > "Simple_Select_Query" at line 1, column 1.
> > > > [INFO] 1130 of 1307 SQL statements executed successfully
> > > >
> > > > when running
> > > >
> > > > rm -rf target/ && ./runtests -Dhttps.protocols=TLSv1.1,TLSv1.2
> > > > --
> > > > ee91
> > > > --env -nc -c -U -w tomee-plume
> > > > com.sun.ts.tests.ejb30.lite.appexception.singleton.annotated.Cl
> > > > ie
> > > > nt
> > > >
> > > > as the initial setup of the derby database seem to fail - don't
> > > > have
> > > > much ideas but using the search engine of trust I found an
> > > > entry,
> > > > that
> > > > this also happened on a tck.work build long time ago.
> > > >
> > > > I guess, that I am just missing a little thing to fix it for my
> > > > setup.
> > > >
> > > > Currently, the TCK runs will fail anyway as we need to fix java
> > > > mail
> > > > first but getting the same exception / outcome as JL would be
> > > > beneficial as it would prove, that the setup works and others
> > > > can
> > > > simply replicate - if this work, I will re-evaluate the
> > > > instructions
> > > > for debugging ;)
> > > >
> > > >
> > > > Gruß & thanks
> > > > Richard
> > > >
> > > >
> > > > Am Montag, dem 25.04.2022 um 14:13 -0700 schrieb David Blevins:
> > > > > Thanks for digging into this, Richard!
> > > > >
> > > > > Agree with your prior statements about updating the README,
> > > > > branching
> > > > > for TomEE 8 and making TomEE 9 the master branch in the
> > > > > tomee-
> > > > > tck
> > > > > project.
> > > > >
> > > > >
> > > > > > On Apr 24, 2022, at 11:14 PM, Zowalla, Richard <
> > > > > > richard.zowalla@hs-heilbronn.de> wrote:
> > > > > >
> > > > > > Ok, I found it:
> > > > > >
> > > > > > -
> > > > > > https://lists.apache.org/thread/sfbvz76c527wojym71csv72k8j2qrrg7
> > > > > >
> > > > > > If we adjust the script to target the (released) ee9.1 tck
> > > > > > (instead
> > > > > > of
> > > > > > the snapshots), it will certainly help. (This was the
> > > > > > script
> > > > > > I
> > > > > > had
> > > > > > in
> > > > > > mint)
> > > > >
> > > > > Agree. Maybe it needs a new name as well so it's more clear
> > > > > that
> > > > > it
> > > > > can be used to create a fresh setup.
> > > > >
> > > > > > But while searching the list archive, I also found this
> > > > > > post
> > > > > > on
> > > > > > happy
> > > > > > TCK work:
> > > > > >
> > > > > > -
> > > > > > https://lists.apache.org/thread/vgthyd8d7rww2p398r9swx8y37mwxf9c
> > > > > >
> > > > > > Sadly the setup images from IntelliJ IDEA are gone (maybe
> > > > > > you
> > > > > > have
> > > > > > them
> > > > > > somewhere, David?).
> > > > >
> > > > > Unfortunately, I don't have those images anymore. We can
> > > > > maybe
> > > > > describe the menu steps instead of showing images. Getting
> > > > > that on
> > > > > the website in the developer area would be good.
> > > > >
> > > > > > Perhaps we should provide a similar jakartaeetck-9.x
> > > > > > installation
> > > > > > via a
> > > > > > Git repository?
> > > > > >
> > > > > > Then we could adjust the "update" script and make it an
> > > > > > "install"
> > > > > > script.
> > > > >
> > > > > The trick here is licensing of the TCK source code, which is
> > > > > EPL. Here's the source of truth on "is this license ok"
> > > > > questions:
> > > > >
> > > > > -
> > > > > https://www.apache.org/legal/resolved.html#weak-copyleft-licenses
> > > > >
> > > > > Effectively, we can use EPL in binary form. In source form
> > > > > it's ok
> > > > > in small amounts where it generally can't be avoided. An
> > > > > entire
> > > > > repository of EPL source code living under
> > > > > https://github.com/apache/
> > > > > is likely not ok.
> > > > >
> > > > > It doesn't mean the idea is shot, but it does mean that repo
> > > > > would
> > > > > have to live outside the Apache org in github.
> > > > >
> > > > > > That would ease the necessary setup steps. Wdyt?
> > > > >
> > > > > Definitely agree it's a great idea. Perhaps we could create
> > > > > an
> > > > > org
> > > > > of our own?
> > > > >
> > > > >
> > > > > -David
> > > > >
Re: TCK Work - Smoothing the path (was Re: How can I help?)
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
Thanks & You are right! Running with JDK 14 works.
JDK 17 has some issues with illegal access within the groovy code
used.
With JDK 14 I am hitting the Javamail issue - so the setup procedere
basically works. That are good news.
Gruß
Richard
Am Dienstag, dem 26.04.2022 um 19:48 +0200 schrieb Jean-Louis Monteiro:
> Sorry for the late reply.
> I managed to reproduce your issue. It does not seem to be a regular
> stackoverflow (loop without exit condition).
> Debugging the code with some additional traces, it looks like we are
> loading jar after jar and the stack isn't big enough to handle it in
> Java
> 11.
>
> I moved to a newer JDK like 14 or 17 and it worked.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Tue, Apr 26, 2022 at 7:42 PM Zowalla, Richard <
> richard.zowalla@hs-heilbronn.de> wrote:
>
> > It looks like the SQL is not the real issue here - although it is a
> > bit
> > confusing because the select statements look ok to me.
> >
> > However, after same additional digging / fiddling arround, I am at
> > a
> > point, there the JVM for the tests does not startup due to an
> > StackOverflowError [1].
> >
> > I tried remote debugging via "-dj" but have no glue why I am
> > running to
> > this StackOverflowError during the "ant.java(...)" call in the
> > related
> > groovy command. I bet, that I miss a little detail - so happy to
> > any
> > additional input ;)
> >
> > Gruß
> > R
> >
> >
> > [1] https://gist.github.com/rzo1/0af90723dc0c6689a6f7d7bae9d2e8da
> >
> >
> > Am Dienstag, dem 26.04.2022 um 09:59 +0000 schrieb Zowalla,
> > Richard:
> > > Hi,
> > >
> > > I changed the script pointing to the released ee9.1 tck now and
> > > updated
> > > the README accordingly. If the instructions are followed
> > > carefully,
> > > it
> > > will lead to a fresh installation.
> > >
> > > In the process, I noticed, that Glassfish 6.0.0 isn't available
> > > anymore
> > > and is replaced by 6.2.5 - JL mentioned on Slack, that 6.2.5
> > > should
> > > also work.
> > >
> > > I think, that we do not really need a public git repository.
> > > Setting
> > > it
> > > up with the script is really straight forward. However, putting
> > > the
> > > TCK
> > > installation into a local git repository makes totally sense in
> > > order
> > > to avoid delete / unpack cycles due to the modifications on the
> > > installation, if the TCK is run.
> > >
> > > I added some instructions in the README.
> > >
> > > Currently, I am struggling with
> > >
> > > [ERROR] java.sql.SQLSyntaxErrorException: Syntax error:
> > > Encountered
> > > "Simple_Select_Query" at line 1, column 1.
> > > [INFO] 1130 of 1307 SQL statements executed successfully
> > >
> > > when running
> > >
> > > rm -rf target/ && ./runtests -Dhttps.protocols=TLSv1.1,TLSv1.2 --
> > > ee91
> > > --env -nc -c -U -w tomee-plume
> > > com.sun.ts.tests.ejb30.lite.appexception.singleton.annotated.Clie
> > > nt
> > >
> > > as the initial setup of the derby database seem to fail - don't
> > > have
> > > much ideas but using the search engine of trust I found an entry,
> > > that
> > > this also happened on a tck.work build long time ago.
> > >
> > > I guess, that I am just missing a little thing to fix it for my
> > > setup.
> > >
> > > Currently, the TCK runs will fail anyway as we need to fix java
> > > mail
> > > first but getting the same exception / outcome as JL would be
> > > beneficial as it would prove, that the setup works and others can
> > > simply replicate - if this work, I will re-evaluate the
> > > instructions
> > > for debugging ;)
> > >
> > >
> > > Gruß & thanks
> > > Richard
> > >
> > >
> > > Am Montag, dem 25.04.2022 um 14:13 -0700 schrieb David Blevins:
> > > > Thanks for digging into this, Richard!
> > > >
> > > > Agree with your prior statements about updating the README,
> > > > branching
> > > > for TomEE 8 and making TomEE 9 the master branch in the tomee-
> > > > tck
> > > > project.
> > > >
> > > >
> > > > > On Apr 24, 2022, at 11:14 PM, Zowalla, Richard <
> > > > > richard.zowalla@hs-heilbronn.de> wrote:
> > > > >
> > > > > Ok, I found it:
> > > > >
> > > > > -
> > > > > https://lists.apache.org/thread/sfbvz76c527wojym71csv72k8j2qrrg7
> > > > >
> > > > > If we adjust the script to target the (released) ee9.1 tck
> > > > > (instead
> > > > > of
> > > > > the snapshots), it will certainly help. (This was the script
> > > > > I
> > > > > had
> > > > > in
> > > > > mint)
> > > >
> > > > Agree. Maybe it needs a new name as well so it's more clear
> > > > that
> > > > it
> > > > can be used to create a fresh setup.
> > > >
> > > > > But while searching the list archive, I also found this post
> > > > > on
> > > > > happy
> > > > > TCK work:
> > > > >
> > > > > -
> > > > > https://lists.apache.org/thread/vgthyd8d7rww2p398r9swx8y37mwxf9c
> > > > >
> > > > > Sadly the setup images from IntelliJ IDEA are gone (maybe you
> > > > > have
> > > > > them
> > > > > somewhere, David?).
> > > >
> > > > Unfortunately, I don't have those images anymore. We can maybe
> > > > describe the menu steps instead of showing images. Getting
> > > > that on
> > > > the website in the developer area would be good.
> > > >
> > > > > Perhaps we should provide a similar jakartaeetck-9.x
> > > > > installation
> > > > > via a
> > > > > Git repository?
> > > > >
> > > > > Then we could adjust the "update" script and make it an
> > > > > "install"
> > > > > script.
> > > >
> > > > The trick here is licensing of the TCK source code, which is
> > > > EPL. Here's the source of truth on "is this license ok"
> > > > questions:
> > > >
> > > > -
> > > > https://www.apache.org/legal/resolved.html#weak-copyleft-licenses
> > > >
> > > > Effectively, we can use EPL in binary form. In source form
> > > > it's ok
> > > > in small amounts where it generally can't be avoided. An
> > > > entire
> > > > repository of EPL source code living under
> > > > https://github.com/apache/
> > > > is likely not ok.
> > > >
> > > > It doesn't mean the idea is shot, but it does mean that repo
> > > > would
> > > > have to live outside the Apache org in github.
> > > >
> > > > > That would ease the necessary setup steps. Wdyt?
> > > >
> > > > Definitely agree it's a great idea. Perhaps we could create an
> > > > org
> > > > of our own?
> > > >
> > > >
> > > > -David
> > > >
Re: TCK Work - Smoothing the path (was Re: How can I help?)
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Sorry for the late reply.
I managed to reproduce your issue. It does not seem to be a regular
stackoverflow (loop without exit condition).
Debugging the code with some additional traces, it looks like we are
loading jar after jar and the stack isn't big enough to handle it in Java
11.
I moved to a newer JDK like 14 or 17 and it worked.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Apr 26, 2022 at 7:42 PM Zowalla, Richard <
richard.zowalla@hs-heilbronn.de> wrote:
> It looks like the SQL is not the real issue here - although it is a bit
> confusing because the select statements look ok to me.
>
> However, after same additional digging / fiddling arround, I am at a
> point, there the JVM for the tests does not startup due to an
> StackOverflowError [1].
>
> I tried remote debugging via "-dj" but have no glue why I am running to
> this StackOverflowError during the "ant.java(...)" call in the related
> groovy command. I bet, that I miss a little detail - so happy to any
> additional input ;)
>
> Gruß
> R
>
>
> [1] https://gist.github.com/rzo1/0af90723dc0c6689a6f7d7bae9d2e8da
>
>
> Am Dienstag, dem 26.04.2022 um 09:59 +0000 schrieb Zowalla, Richard:
> > Hi,
> >
> > I changed the script pointing to the released ee9.1 tck now and
> > updated
> > the README accordingly. If the instructions are followed carefully,
> > it
> > will lead to a fresh installation.
> >
> > In the process, I noticed, that Glassfish 6.0.0 isn't available
> > anymore
> > and is replaced by 6.2.5 - JL mentioned on Slack, that 6.2.5 should
> > also work.
> >
> > I think, that we do not really need a public git repository. Setting
> > it
> > up with the script is really straight forward. However, putting the
> > TCK
> > installation into a local git repository makes totally sense in order
> > to avoid delete / unpack cycles due to the modifications on the
> > installation, if the TCK is run.
> >
> > I added some instructions in the README.
> >
> > Currently, I am struggling with
> >
> > [ERROR] java.sql.SQLSyntaxErrorException: Syntax error: Encountered
> > "Simple_Select_Query" at line 1, column 1.
> > [INFO] 1130 of 1307 SQL statements executed successfully
> >
> > when running
> >
> > rm -rf target/ && ./runtests -Dhttps.protocols=TLSv1.1,TLSv1.2 --ee91
> > --env -nc -c -U -w tomee-plume
> > com.sun.ts.tests.ejb30.lite.appexception.singleton.annotated.Client
> >
> > as the initial setup of the derby database seem to fail - don't have
> > much ideas but using the search engine of trust I found an entry,
> > that
> > this also happened on a tck.work build long time ago.
> >
> > I guess, that I am just missing a little thing to fix it for my
> > setup.
> >
> > Currently, the TCK runs will fail anyway as we need to fix java mail
> > first but getting the same exception / outcome as JL would be
> > beneficial as it would prove, that the setup works and others can
> > simply replicate - if this work, I will re-evaluate the instructions
> > for debugging ;)
> >
> >
> > Gruß & thanks
> > Richard
> >
> >
> > Am Montag, dem 25.04.2022 um 14:13 -0700 schrieb David Blevins:
> > > Thanks for digging into this, Richard!
> > >
> > > Agree with your prior statements about updating the README,
> > > branching
> > > for TomEE 8 and making TomEE 9 the master branch in the tomee-tck
> > > project.
> > >
> > >
> > > > On Apr 24, 2022, at 11:14 PM, Zowalla, Richard <
> > > > richard.zowalla@hs-heilbronn.de> wrote:
> > > >
> > > > Ok, I found it:
> > > >
> > > > -
> > > > https://lists.apache.org/thread/sfbvz76c527wojym71csv72k8j2qrrg7
> > > >
> > > > If we adjust the script to target the (released) ee9.1 tck
> > > > (instead
> > > > of
> > > > the snapshots), it will certainly help. (This was the script I
> > > > had
> > > > in
> > > > mint)
> > >
> > > Agree. Maybe it needs a new name as well so it's more clear that
> > > it
> > > can be used to create a fresh setup.
> > >
> > > > But while searching the list archive, I also found this post on
> > > > happy
> > > > TCK work:
> > > >
> > > > -
> > > > https://lists.apache.org/thread/vgthyd8d7rww2p398r9swx8y37mwxf9c
> > > >
> > > > Sadly the setup images from IntelliJ IDEA are gone (maybe you
> > > > have
> > > > them
> > > > somewhere, David?).
> > >
> > > Unfortunately, I don't have those images anymore. We can maybe
> > > describe the menu steps instead of showing images. Getting that on
> > > the website in the developer area would be good.
> > >
> > > > Perhaps we should provide a similar jakartaeetck-9.x installation
> > > > via a
> > > > Git repository?
> > > >
> > > > Then we could adjust the "update" script and make it an "install"
> > > > script.
> > >
> > > The trick here is licensing of the TCK source code, which is
> > > EPL. Here's the source of truth on "is this license ok" questions:
> > >
> > > -
> > > https://www.apache.org/legal/resolved.html#weak-copyleft-licenses
> > >
> > > Effectively, we can use EPL in binary form. In source form it's ok
> > > in small amounts where it generally can't be avoided. An entire
> > > repository of EPL source code living under
> > > https://github.com/apache/
> > > is likely not ok.
> > >
> > > It doesn't mean the idea is shot, but it does mean that repo would
> > > have to live outside the Apache org in github.
> > >
> > > > That would ease the necessary setup steps. Wdyt?
> > >
> > > Definitely agree it's a great idea. Perhaps we could create an org
> > > of our own?
> > >
> > >
> > > -David
> > >
>
Re: TCK Work - Smoothing the path (was Re: How can I help?)
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
It looks like the SQL is not the real issue here - although it is a bit
confusing because the select statements look ok to me.
However, after same additional digging / fiddling arround, I am at a
point, there the JVM for the tests does not startup due to an
StackOverflowError [1].
I tried remote debugging via "-dj" but have no glue why I am running to
this StackOverflowError during the "ant.java(...)" call in the related
groovy command. I bet, that I miss a little detail - so happy to any
additional input ;)
Gruß
R
[1] https://gist.github.com/rzo1/0af90723dc0c6689a6f7d7bae9d2e8da
Am Dienstag, dem 26.04.2022 um 09:59 +0000 schrieb Zowalla, Richard:
> Hi,
>
> I changed the script pointing to the released ee9.1 tck now and
> updated
> the README accordingly. If the instructions are followed carefully,
> it
> will lead to a fresh installation.
>
> In the process, I noticed, that Glassfish 6.0.0 isn't available
> anymore
> and is replaced by 6.2.5 - JL mentioned on Slack, that 6.2.5 should
> also work.
>
> I think, that we do not really need a public git repository. Setting
> it
> up with the script is really straight forward. However, putting the
> TCK
> installation into a local git repository makes totally sense in order
> to avoid delete / unpack cycles due to the modifications on the
> installation, if the TCK is run.
>
> I added some instructions in the README.
>
> Currently, I am struggling with
>
> [ERROR] java.sql.SQLSyntaxErrorException: Syntax error: Encountered
> "Simple_Select_Query" at line 1, column 1.
> [INFO] 1130 of 1307 SQL statements executed successfully
>
> when running
>
> rm -rf target/ && ./runtests -Dhttps.protocols=TLSv1.1,TLSv1.2 --ee91
> --env -nc -c -U -w tomee-plume
> com.sun.ts.tests.ejb30.lite.appexception.singleton.annotated.Client
>
> as the initial setup of the derby database seem to fail - don't have
> much ideas but using the search engine of trust I found an entry,
> that
> this also happened on a tck.work build long time ago.
>
> I guess, that I am just missing a little thing to fix it for my
> setup.
>
> Currently, the TCK runs will fail anyway as we need to fix java mail
> first but getting the same exception / outcome as JL would be
> beneficial as it would prove, that the setup works and others can
> simply replicate - if this work, I will re-evaluate the instructions
> for debugging ;)
>
>
> Gruß & thanks
> Richard
>
>
> Am Montag, dem 25.04.2022 um 14:13 -0700 schrieb David Blevins:
> > Thanks for digging into this, Richard!
> >
> > Agree with your prior statements about updating the README,
> > branching
> > for TomEE 8 and making TomEE 9 the master branch in the tomee-tck
> > project.
> >
> >
> > > On Apr 24, 2022, at 11:14 PM, Zowalla, Richard <
> > > richard.zowalla@hs-heilbronn.de> wrote:
> > >
> > > Ok, I found it:
> > >
> > > -
> > > https://lists.apache.org/thread/sfbvz76c527wojym71csv72k8j2qrrg7
> > >
> > > If we adjust the script to target the (released) ee9.1 tck
> > > (instead
> > > of
> > > the snapshots), it will certainly help. (This was the script I
> > > had
> > > in
> > > mint)
> >
> > Agree. Maybe it needs a new name as well so it's more clear that
> > it
> > can be used to create a fresh setup.
> >
> > > But while searching the list archive, I also found this post on
> > > happy
> > > TCK work:
> > >
> > > -
> > > https://lists.apache.org/thread/vgthyd8d7rww2p398r9swx8y37mwxf9c
> > >
> > > Sadly the setup images from IntelliJ IDEA are gone (maybe you
> > > have
> > > them
> > > somewhere, David?).
> >
> > Unfortunately, I don't have those images anymore. We can maybe
> > describe the menu steps instead of showing images. Getting that on
> > the website in the developer area would be good.
> >
> > > Perhaps we should provide a similar jakartaeetck-9.x installation
> > > via a
> > > Git repository?
> > >
> > > Then we could adjust the "update" script and make it an "install"
> > > script.
> >
> > The trick here is licensing of the TCK source code, which is
> > EPL. Here's the source of truth on "is this license ok" questions:
> >
> > -
> > https://www.apache.org/legal/resolved.html#weak-copyleft-licenses
> >
> > Effectively, we can use EPL in binary form. In source form it's ok
> > in small amounts where it generally can't be avoided. An entire
> > repository of EPL source code living under
> > https://github.com/apache/
> > is likely not ok.
> >
> > It doesn't mean the idea is shot, but it does mean that repo would
> > have to live outside the Apache org in github.
> >
> > > That would ease the necessary setup steps. Wdyt?
> >
> > Definitely agree it's a great idea. Perhaps we could create an org
> > of our own?
> >
> >
> > -David
> >
Re: TCK Work - Smoothing the path (was Re: How can I help?)
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
Hi,
I changed the script pointing to the released ee9.1 tck now and updated
the README accordingly. If the instructions are followed carefully, it
will lead to a fresh installation.
In the process, I noticed, that Glassfish 6.0.0 isn't available anymore
and is replaced by 6.2.5 - JL mentioned on Slack, that 6.2.5 should
also work.
I think, that we do not really need a public git repository. Setting it
up with the script is really straight forward. However, putting the TCK
installation into a local git repository makes totally sense in order
to avoid delete / unpack cycles due to the modifications on the
installation, if the TCK is run.
I added some instructions in the README.
Currently, I am struggling with
[ERROR] java.sql.SQLSyntaxErrorException: Syntax error: Encountered
"Simple_Select_Query" at line 1, column 1.
[INFO] 1130 of 1307 SQL statements executed successfully
when running
rm -rf target/ && ./runtests -Dhttps.protocols=TLSv1.1,TLSv1.2 --ee91
--env -nc -c -U -w tomee-plume
com.sun.ts.tests.ejb30.lite.appexception.singleton.annotated.Client
as the initial setup of the derby database seem to fail - don't have
much ideas but using the search engine of trust I found an entry, that
this also happened on a tck.work build long time ago.
I guess, that I am just missing a little thing to fix it for my setup.
Currently, the TCK runs will fail anyway as we need to fix java mail
first but getting the same exception / outcome as JL would be
beneficial as it would prove, that the setup works and others can
simply replicate - if this work, I will re-evaluate the instructions
for debugging ;)
Gruß & thanks
Richard
Am Montag, dem 25.04.2022 um 14:13 -0700 schrieb David Blevins:
> Thanks for digging into this, Richard!
>
> Agree with your prior statements about updating the README, branching
> for TomEE 8 and making TomEE 9 the master branch in the tomee-tck
> project.
>
>
> > On Apr 24, 2022, at 11:14 PM, Zowalla, Richard <
> > richard.zowalla@hs-heilbronn.de> wrote:
> >
> > Ok, I found it:
> >
> > - https://lists.apache.org/thread/sfbvz76c527wojym71csv72k8j2qrrg7
> >
> > If we adjust the script to target the (released) ee9.1 tck (instead
> > of
> > the snapshots), it will certainly help. (This was the script I had
> > in
> > mint)
>
> Agree. Maybe it needs a new name as well so it's more clear that it
> can be used to create a fresh setup.
>
> > But while searching the list archive, I also found this post on
> > happy
> > TCK work:
> >
> > - https://lists.apache.org/thread/vgthyd8d7rww2p398r9swx8y37mwxf9c
> >
> > Sadly the setup images from IntelliJ IDEA are gone (maybe you have
> > them
> > somewhere, David?).
>
> Unfortunately, I don't have those images anymore. We can maybe
> describe the menu steps instead of showing images. Getting that on
> the website in the developer area would be good.
>
> > Perhaps we should provide a similar jakartaeetck-9.x installation
> > via a
> > Git repository?
> >
> > Then we could adjust the "update" script and make it an "install"
> > script.
>
> The trick here is licensing of the TCK source code, which is
> EPL. Here's the source of truth on "is this license ok" questions:
>
> - https://www.apache.org/legal/resolved.html#weak-copyleft-licenses
>
> Effectively, we can use EPL in binary form. In source form it's ok
> in small amounts where it generally can't be avoided. An entire
> repository of EPL source code living under https://github.com/apache/
> is likely not ok.
>
> It doesn't mean the idea is shot, but it does mean that repo would
> have to live outside the Apache org in github.
>
> > That would ease the necessary setup steps. Wdyt?
>
> Definitely agree it's a great idea. Perhaps we could create an org
> of our own?
>
>
> -David
>
Re: TCK Work - Smoothing the path (was Re: How can I help?)
Posted by David Blevins <da...@gmail.com>.
Thanks for digging into this, Richard!
Agree with your prior statements about updating the README, branching for TomEE 8 and making TomEE 9 the master branch in the tomee-tck project.
> On Apr 24, 2022, at 11:14 PM, Zowalla, Richard <ri...@hs-heilbronn.de> wrote:
>
> Ok, I found it:
>
> - https://lists.apache.org/thread/sfbvz76c527wojym71csv72k8j2qrrg7
>
> If we adjust the script to target the (released) ee9.1 tck (instead of
> the snapshots), it will certainly help. (This was the script I had in
> mint)
Agree. Maybe it needs a new name as well so it's more clear that it can be used to create a fresh setup.
> But while searching the list archive, I also found this post on happy
> TCK work:
>
> - https://lists.apache.org/thread/vgthyd8d7rww2p398r9swx8y37mwxf9c
>
> Sadly the setup images from IntelliJ IDEA are gone (maybe you have them
> somewhere, David?).
Unfortunately, I don't have those images anymore. We can maybe describe the menu steps instead of showing images. Getting that on the website in the developer area would be good.
> Perhaps we should provide a similar jakartaeetck-9.x installation via a
> Git repository?
>
> Then we could adjust the "update" script and make it an "install"
> script.
The trick here is licensing of the TCK source code, which is EPL. Here's the source of truth on "is this license ok" questions:
- https://www.apache.org/legal/resolved.html#weak-copyleft-licenses
Effectively, we can use EPL in binary form. In source form it's ok in small amounts where it generally can't be avoided. An entire repository of EPL source code living under https://github.com/apache/ is likely not ok.
It doesn't mean the idea is shot, but it does mean that repo would have to live outside the Apache org in github.
> That would ease the necessary setup steps. Wdyt?
Definitely agree it's a great idea. Perhaps we could create an org of our own?
-David
Re: TCK Work - Smoothing the path (was Re: How can I help?)
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
Ok, I found it:
- https://lists.apache.org/thread/sfbvz76c527wojym71csv72k8j2qrrg7
If we adjust the script to target the (released) ee9.1 tck (instead of
the snapshots), it will certainly help. (This was the script I had in
mint)
But while searching the list archive, I also found this post on happy
TCK work:
- https://lists.apache.org/thread/vgthyd8d7rww2p398r9swx8y37mwxf9c
Sadly the setup images from IntelliJ IDEA are gone (maybe you have them
somewhere, David?).
Perhaps we should provide a similar jakartaeetck-9.x installation via a
Git repository?
Then we could adjust the "update" script and make it an "install"
script.
That would ease the necessary setup steps. Wdyt?
Gruß
Richard
Am Montag, dem 25.04.2022 um 05:54 +0000 schrieb Zowalla, Richard:
> > > The trick is that setup is difficult to maintain and can be quite
> > > intimidating.
>
> I can remember ;) - my first attempts in May 21 were indeed
> intimidating.
>
> > Richard, have you tried to run any tests yet? If not, are you
> > possibly willing to be the brave guy who tries it first, hits the
> > issues and works with myself or Jean-Louis to smooth the path for
> > Zoltán and others?
>
> Not for the current M8 Snapshot yet. Last time I did run (some) tests
> of the ee9 tck was in May 21 - my tech stack switched, so I have to
> set
> it up from scratch again.
>
> There can be no better environment to try and hit the (setup) issues
> -
> so yes, count me in ;)
>
> As far as I can remember, the README also needs an overhaul and we
> should include the handy script, which does some of the setup
> automatically. I think, that David posted it on the list.
>
> I think, that we also need to switch to a dedicated tomee-8.x branch
> and move the tomee-9.x branch to master in the tomee-tck harness
> repo.
>
> Gruß
> Richard
>
> Am Sonntag, dem 24.04.2022 um 13:47 -0700 schrieb David Blevins:
> > If we could get a few more people familiar with running the Jakarta
> > EE TCK in TomEE and ready to start fixing test failures, that'd be
> > the biggest impact on all our current and future certification
> > efforts.
> >
> > The trick is that setup is difficult to maintain and can be quite
> > intimidating.
> >
> > Richard, have you tried to run any tests yet? If not, are you
> > possibly willing to be the brave guy who tries it first, hits the
> > issues and works with myself or Jean-Louis to smooth the path for
> > Zoltán and others?
> >
> > Truthfully, it's something we should be doing before every release
> > on
> > any branch. It's another particularly large release process gap we
> > do need to eventually fill.
> >
> >
> > -David
> >
> >
> > > On Apr 24, 2022, at 2:06 AM, Zowalla, Richard <
> > > richard.zowalla@hs-heilbronn.de> wrote:
> > >
> > > Hi Zoltán,
> > >
> > > It's very great from you and it's truly awesome when a long time
> > > user
> > > of TomEE decides to contribute :)
> > >
> > > First of all, do not get intimidated by your first ticket. If it
> > > ends
> > > up being too hard or just not fun, let's find something else for
> > > you.
> > > There is always plenty of work to do.
> > >
> > > We are currently working on TomEE 9. Therefore, we moved away
> > > from
> > > our
> > > previous byte code transformation approach and switched TomEE
> > > master to
> > > TomEE 9 (Jakarta).
> > >
> > > While we made good progress, there is still a lot todo. The
> > > efforts
> > > and
> > > open tasks are tracked in [1]. A lot of effort is currently done
> > > to
> > > switch the MicroProfile impl to MP Smallrye impls in order to
> > > move
> > > to
> > > the jakarta namespace [2].
> > >
> > > If you are interested in contributing to our TomEE 9 efforts, we
> > > can
> > > surely find some beginner friendly tasks in this area.
> > >
> > > Gruß
> > > Richard
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/TOMEE-3862
> > > [2]
> > > https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
> > >
> > >
> > > Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
> > > > Hi!
> > > >
> > > > I live in Hungary. I am working at an IT company as a software
> > > > developer, I
> > > > develop java
> > > > webapps with jsf (PrimeFaces) and microservice like apps
> > > > without
> > > > any
> > > > container technology
> > > > and Oracle database.
> > > >
> > > > We want to switch to jakarta ee 9 at the company, but
> > > > unfortunately
> > > > we ran
> > > > into problems with tomee 9 and I would like to contribute to
> > > > fixing
> > > > these
> > > > bugs and possibly improving tomee jakarta 10. (I'm sorry to
> > > > read
> > > > on
> > > > another
> > > > tomee mailing list, that you had to skip jakarta ee 8 and 9
> > > > compliance
> > > > entirely)
> > > > I use java 11 and netbeans on windows 10. If we don't have to,
> > > > we
> > > > don't
> > > > want to use another app server because we've been using tomee
> > > > since
> > > > 1.7.3.
> > > >
> > > > Best regards: Zoltán Tichov
TCK Work - Smoothing the path (was Re: How can I help?)
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
>
> > The trick is that setup is difficult to maintain and can be quite
> > intimidating.
I can remember ;) - my first attempts in May 21 were indeed
intimidating.
> Richard, have you tried to run any tests yet? If not, are you
> possibly willing to be the brave guy who tries it first, hits the
> issues and works with myself or Jean-Louis to smooth the path for
> Zoltán and others?
Not for the current M8 Snapshot yet. Last time I did run (some) tests
of the ee9 tck was in May 21 - my tech stack switched, so I have to set
it up from scratch again.
There can be no better environment to try and hit the (setup) issues -
so yes, count me in ;)
As far as I can remember, the README also needs an overhaul and we
should include the handy script, which does some of the setup
automatically. I think, that David posted it on the list.
I think, that we also need to switch to a dedicated tomee-8.x branch
and move the tomee-9.x branch to master in the tomee-tck harness repo.
Gruß
Richard
Am Sonntag, dem 24.04.2022 um 13:47 -0700 schrieb David Blevins:
> If we could get a few more people familiar with running the Jakarta
> EE TCK in TomEE and ready to start fixing test failures, that'd be
> the biggest impact on all our current and future certification
> efforts.
>
> The trick is that setup is difficult to maintain and can be quite
> intimidating.
>
> Richard, have you tried to run any tests yet? If not, are you
> possibly willing to be the brave guy who tries it first, hits the
> issues and works with myself or Jean-Louis to smooth the path for
> Zoltán and others?
>
> Truthfully, it's something we should be doing before every release on
> any branch. It's another particularly large release process gap we
> do need to eventually fill.
>
>
> -David
>
>
> > On Apr 24, 2022, at 2:06 AM, Zowalla, Richard <
> > richard.zowalla@hs-heilbronn.de> wrote:
> >
> > Hi Zoltán,
> >
> > It's very great from you and it's truly awesome when a long time
> > user
> > of TomEE decides to contribute :)
> >
> > First of all, do not get intimidated by your first ticket. If it
> > ends
> > up being too hard or just not fun, let's find something else for
> > you.
> > There is always plenty of work to do.
> >
> > We are currently working on TomEE 9. Therefore, we moved away from
> > our
> > previous byte code transformation approach and switched TomEE
> > master to
> > TomEE 9 (Jakarta).
> >
> > While we made good progress, there is still a lot todo. The efforts
> > and
> > open tasks are tracked in [1]. A lot of effort is currently done to
> > switch the MicroProfile impl to MP Smallrye impls in order to move
> > to
> > the jakarta namespace [2].
> >
> > If you are interested in contributing to our TomEE 9 efforts, we
> > can
> > surely find some beginner friendly tasks in this area.
> >
> > Gruß
> > Richard
> >
> >
> > [1] https://issues.apache.org/jira/browse/TOMEE-3862
> > [2]
> > https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
> >
> >
> > Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
> > > Hi!
> > >
> > > I live in Hungary. I am working at an IT company as a software
> > > developer, I
> > > develop java
> > > webapps with jsf (PrimeFaces) and microservice like apps without
> > > any
> > > container technology
> > > and Oracle database.
> > >
> > > We want to switch to jakarta ee 9 at the company, but
> > > unfortunately
> > > we ran
> > > into problems with tomee 9 and I would like to contribute to
> > > fixing
> > > these
> > > bugs and possibly improving tomee jakarta 10. (I'm sorry to read
> > > on
> > > another
> > > tomee mailing list, that you had to skip jakarta ee 8 and 9
> > > compliance
> > > entirely)
> > > I use java 11 and netbeans on windows 10. If we don't have to, we
> > > don't
> > > want to use another app server because we've been using tomee
> > > since
> > > 1.7.3.
> > >
> > > Best regards: Zoltán Tichov
Re: How can I help?
Posted by David Blevins <da...@gmail.com>.
If we could get a few more people familiar with running the Jakarta EE TCK in TomEE and ready to start fixing test failures, that'd be the biggest impact on all our current and future certification efforts.
The trick is that setup is difficult to maintain and can be quite intimidating.
Richard, have you tried to run any tests yet? If not, are you possibly willing to be the brave guy who tries it first, hits the issues and works with myself or Jean-Louis to smooth the path for Zoltán and others?
Truthfully, it's something we should be doing before every release on any branch. It's another particularly large release process gap we do need to eventually fill.
-David
> On Apr 24, 2022, at 2:06 AM, Zowalla, Richard <ri...@hs-heilbronn.de> wrote:
>
> Hi Zoltán,
>
> It's very great from you and it's truly awesome when a long time user
> of TomEE decides to contribute :)
>
> First of all, do not get intimidated by your first ticket. If it ends
> up being too hard or just not fun, let's find something else for you.
> There is always plenty of work to do.
>
> We are currently working on TomEE 9. Therefore, we moved away from our
> previous byte code transformation approach and switched TomEE master to
> TomEE 9 (Jakarta).
>
> While we made good progress, there is still a lot todo. The efforts and
> open tasks are tracked in [1]. A lot of effort is currently done to
> switch the MicroProfile impl to MP Smallrye impls in order to move to
> the jakarta namespace [2].
>
> If you are interested in contributing to our TomEE 9 efforts, we can
> surely find some beginner friendly tasks in this area.
>
> Gruß
> Richard
>
>
> [1] https://issues.apache.org/jira/browse/TOMEE-3862
> [2] https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
>
>
> Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
>> Hi!
>>
>> I live in Hungary. I am working at an IT company as a software
>> developer, I
>> develop java
>> webapps with jsf (PrimeFaces) and microservice like apps without any
>> container technology
>> and Oracle database.
>>
>> We want to switch to jakarta ee 9 at the company, but unfortunately
>> we ran
>> into problems with tomee 9 and I would like to contribute to fixing
>> these
>> bugs and possibly improving tomee jakarta 10. (I'm sorry to read on
>> another
>> tomee mailing list, that you had to skip jakarta ee 8 and 9
>> compliance
>> entirely)
>> I use java 11 and netbeans on windows 10. If we don't have to, we
>> don't
>> want to use another app server because we've been using tomee since
>> 1.7.3.
>>
>> Best regards: Zoltán Tichov
Re: TOMEE-3824 New Jakarta EE 9 XML namespace not recognized in web-fragment.xml (was Re: How can I help?)
Posted by Jonathan Gallimore <jo...@gmail.com>.
Hi Zoltán
I've assigned that JIRA to you.
Many thanks
Jon
On Fri, May 6, 2022 at 9:14 AM Zoltán Tichov <zo...@gmail.com>
wrote:
> Hi David!
>
> My JIRA username is eagleegg
>
> Thanks: Zoltán
>
>
> On Fri, May 6, 2022 at 1:27 AM David Blevins <da...@gmail.com>
> wrote:
>
> > Hey Zoltán!
> >
> > Absolutely, you're welcome to fix the issue. I can assign the issue to
> > you if you let me know your JIRA username. Make a comment on the issue
> and
> > that'll be the quickest way to send it.
> >
> > We intentionally have it setup so new people can't assign issues to
> > themselves so that they're forced to come to the list where we can get
> them
> > off to the right start.
> >
> > On the issue you want to fix, most the code that would be involved in the
> > fix is here:
> >
> > -
> >
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java
> >
> > Some important history to help you. When J2EE got renamed to Java EE,
> the
> > namespaces changed. The TCK for full Java EE server tests that all
> > historic namespaces can be supported. Our solution was to create an
> > org.xml.sax.XMLFilter and dynamically rewrite the namespace on any
> document
> > we were given to the then latest namespace
> > http://java.sun.com/xml/ns/javaee
> >
> > -
> >
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java#L291
> >
> > The way JAXB works is all the namespaces are hardcoded and without a
> > filter like the one we made, there'd be no way to support multiple
> > namespaces. Those namespaces are all here:
> >
> > -
> >
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/ObjectFactory.java
> >
> > I did most that work, but it was 15 years ago and I don't recall all the
> > details. Jean-Louis did the work for the Jakarta namespace. I know
> we're
> > testing at least some those old namespaces and the new namespace. We
> have
> > some test descriptors here:
> >
> > -
> >
> https://github.com/apache/tomee/tree/master/container/openejb-jee/src/test/resources
> >
> > I don't recall the name of those tests offhand, but if you search for the
> > names of some of those files that should get you close.
> >
> >
> > Now a couple thoughts as I see potential for some short-term work and
> some
> > longer-term work.
> >
> > - Long-term: We're clearly still referring to "
> > http://java.sun.com/xml/ns/javaee" as the primary namespace. That's not
> > going to age well. If someone has to write an email like this in 15
> years,
> > they'll likely have to explain what "javaee" is like I had to harken back
> > to "J2EE". We should probably make the new Jakarta EE namespace be the
> > primary namespace and rework all the JAXB code and namespace filters
> > accordingly.
> >
> > - Short-term: Do not do any of that and avoid opening that can of worms
> > at all cost. Get the file to parse with the minimum change possible.
> Get
> > some experience with the code and a successful contribution in the can.
> >
> > This is what I'd do regardless of (or because of?) years of experience.
> I
> > always take the quick win before attempting the big one.
> >
> > If you get into the code and decide the big change sounds like fun, we
> can
> > make a ticket for it and plan it. Probably we'd want to shore up any
> test
> > coverage we'd be lacking and also get a full TCK run to see what those
> > numbers look like so we can spot regressions.
> >
> > Hope some of this is helpful!
> >
> > Don't hesitate to be super noisy and ask lots and lots of questions.
> > Silence is death. :)
> >
> >
> > -David
> >
> >
> > > On May 5, 2022, at 3:31 PM, Zoltán Tichov <zo...@gmail.com>
> > wrote:
> > >
> > > Hi Richard!
> > > I found a ticket with a bug that I also encountered.The ticket is open
> > and
> > > unassigned.
> > > Should I try to fix it? If so, how can it be assigned to me?
> > > https://issues.apache.org/jira/browse/TOMEE-3824
> > >
> > > Best: Zoltán
> > >
> > > On Wed, Apr 27, 2022 at 8:36 AM Zowalla, Richard <
> > > richard.zowalla@hs-heilbronn.de> wrote:
> > >
> > >> Hi,
> > >>
> > >> it would certainly help to track these issues as an issue.
> > >>
> > >> Maybe they are already solved (as the code has evolved) but maybe not,
> > >> so it would be good to have them.
> > >>
> > >> Gruß
> > >> Richard
> > >>
> > >> Am Dienstag, dem 26.04.2022 um 21:54 +0200 schrieb Zoltán Tichov:
> > >>> Hi Richard!
> > >>>
> > >>> I have found two errors in Tomee 9.0.0-M7. Should I make tickets for
> > >>> these
> > >>> errors and try to fix them?
> > >>> Although they may have been fixed in the next version (9.0.0-M8)
> > >>>
> > >>> Zoltán
> > >>>
> > >>> On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
> > >>> richard.zowalla@hs-heilbronn.de> wrote:
> > >>>
> > >>>> Hi Zoltán,
> > >>>>
> > >>>> It's very great from you and it's truly awesome when a long time
> > >>>> user
> > >>>> of TomEE decides to contribute :)
> > >>>>
> > >>>> First of all, do not get intimidated by your first ticket. If it
> > >>>> ends
> > >>>> up being too hard or just not fun, let's find something else for
> > >>>> you.
> > >>>> There is always plenty of work to do.
> > >>>>
> > >>>> We are currently working on TomEE 9. Therefore, we moved away from
> > >>>> our
> > >>>> previous byte code transformation approach and switched TomEE
> > >>>> master to
> > >>>> TomEE 9 (Jakarta).
> > >>>>
> > >>>> While we made good progress, there is still a lot todo. The efforts
> > >>>> and
> > >>>> open tasks are tracked in [1]. A lot of effort is currently done to
> > >>>> switch the MicroProfile impl to MP Smallrye impls in order to move
> > >>>> to
> > >>>> the jakarta namespace [2].
> > >>>>
> > >>>> If you are interested in contributing to our TomEE 9 efforts, we
> > >>>> can
> > >>>> surely find some beginner friendly tasks in this area.
> > >>>>
> > >>>> Gruß
> > >>>> Richard
> > >>>>
> > >>>>
> > >>>> [1] https://issues.apache.org/jira/browse/TOMEE-3862
> > >>>> [2]
> > >>>> https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
> > >>>>
> > >>>>
> > >>>> Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
> > >>>>> Hi!
> > >>>>>
> > >>>>> I live in Hungary. I am working at an IT company as a software
> > >>>>> developer, I
> > >>>>> develop java
> > >>>>> webapps with jsf (PrimeFaces) and microservice like apps without
> > >>>>> any
> > >>>>> container technology
> > >>>>> and Oracle database.
> > >>>>>
> > >>>>> We want to switch to jakarta ee 9 at the company, but
> > >>>>> unfortunately
> > >>>>> we ran
> > >>>>> into problems with tomee 9 and I would like to contribute to
> > >>>>> fixing
> > >>>>> these
> > >>>>> bugs and possibly improving tomee jakarta 10. (I'm sorry to read
> > >>>>> on
> > >>>>> another
> > >>>>> tomee mailing list, that you had to skip jakarta ee 8 and 9
> > >>>>> compliance
> > >>>>> entirely)
> > >>>>> I use java 11 and netbeans on windows 10. If we don't have to, we
> > >>>>> don't
> > >>>>> want to use another app server because we've been using tomee
> > >>>>> since
> > >>>>> 1.7.3.
> > >>>>>
> > >>>>> Best regards: Zoltán Tichov
> > >>
> >
> >
>
Re: TOMEE-3824 New Jakarta EE 9 XML namespace not recognized in web-fragment.xml (was Re: How can I help?)
Posted by Zoltán Tichov <zo...@gmail.com>.
Hi David!
My JIRA username is eagleegg
Thanks: Zoltán
On Fri, May 6, 2022 at 1:27 AM David Blevins <da...@gmail.com>
wrote:
> Hey Zoltán!
>
> Absolutely, you're welcome to fix the issue. I can assign the issue to
> you if you let me know your JIRA username. Make a comment on the issue and
> that'll be the quickest way to send it.
>
> We intentionally have it setup so new people can't assign issues to
> themselves so that they're forced to come to the list where we can get them
> off to the right start.
>
> On the issue you want to fix, most the code that would be involved in the
> fix is here:
>
> -
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java
>
> Some important history to help you. When J2EE got renamed to Java EE, the
> namespaces changed. The TCK for full Java EE server tests that all
> historic namespaces can be supported. Our solution was to create an
> org.xml.sax.XMLFilter and dynamically rewrite the namespace on any document
> we were given to the then latest namespace
> http://java.sun.com/xml/ns/javaee
>
> -
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java#L291
>
> The way JAXB works is all the namespaces are hardcoded and without a
> filter like the one we made, there'd be no way to support multiple
> namespaces. Those namespaces are all here:
>
> -
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/ObjectFactory.java
>
> I did most that work, but it was 15 years ago and I don't recall all the
> details. Jean-Louis did the work for the Jakarta namespace. I know we're
> testing at least some those old namespaces and the new namespace. We have
> some test descriptors here:
>
> -
> https://github.com/apache/tomee/tree/master/container/openejb-jee/src/test/resources
>
> I don't recall the name of those tests offhand, but if you search for the
> names of some of those files that should get you close.
>
>
> Now a couple thoughts as I see potential for some short-term work and some
> longer-term work.
>
> - Long-term: We're clearly still referring to "
> http://java.sun.com/xml/ns/javaee" as the primary namespace. That's not
> going to age well. If someone has to write an email like this in 15 years,
> they'll likely have to explain what "javaee" is like I had to harken back
> to "J2EE". We should probably make the new Jakarta EE namespace be the
> primary namespace and rework all the JAXB code and namespace filters
> accordingly.
>
> - Short-term: Do not do any of that and avoid opening that can of worms
> at all cost. Get the file to parse with the minimum change possible. Get
> some experience with the code and a successful contribution in the can.
>
> This is what I'd do regardless of (or because of?) years of experience. I
> always take the quick win before attempting the big one.
>
> If you get into the code and decide the big change sounds like fun, we can
> make a ticket for it and plan it. Probably we'd want to shore up any test
> coverage we'd be lacking and also get a full TCK run to see what those
> numbers look like so we can spot regressions.
>
> Hope some of this is helpful!
>
> Don't hesitate to be super noisy and ask lots and lots of questions.
> Silence is death. :)
>
>
> -David
>
>
> > On May 5, 2022, at 3:31 PM, Zoltán Tichov <zo...@gmail.com>
> wrote:
> >
> > Hi Richard!
> > I found a ticket with a bug that I also encountered.The ticket is open
> and
> > unassigned.
> > Should I try to fix it? If so, how can it be assigned to me?
> > https://issues.apache.org/jira/browse/TOMEE-3824
> >
> > Best: Zoltán
> >
> > On Wed, Apr 27, 2022 at 8:36 AM Zowalla, Richard <
> > richard.zowalla@hs-heilbronn.de> wrote:
> >
> >> Hi,
> >>
> >> it would certainly help to track these issues as an issue.
> >>
> >> Maybe they are already solved (as the code has evolved) but maybe not,
> >> so it would be good to have them.
> >>
> >> Gruß
> >> Richard
> >>
> >> Am Dienstag, dem 26.04.2022 um 21:54 +0200 schrieb Zoltán Tichov:
> >>> Hi Richard!
> >>>
> >>> I have found two errors in Tomee 9.0.0-M7. Should I make tickets for
> >>> these
> >>> errors and try to fix them?
> >>> Although they may have been fixed in the next version (9.0.0-M8)
> >>>
> >>> Zoltán
> >>>
> >>> On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
> >>> richard.zowalla@hs-heilbronn.de> wrote:
> >>>
> >>>> Hi Zoltán,
> >>>>
> >>>> It's very great from you and it's truly awesome when a long time
> >>>> user
> >>>> of TomEE decides to contribute :)
> >>>>
> >>>> First of all, do not get intimidated by your first ticket. If it
> >>>> ends
> >>>> up being too hard or just not fun, let's find something else for
> >>>> you.
> >>>> There is always plenty of work to do.
> >>>>
> >>>> We are currently working on TomEE 9. Therefore, we moved away from
> >>>> our
> >>>> previous byte code transformation approach and switched TomEE
> >>>> master to
> >>>> TomEE 9 (Jakarta).
> >>>>
> >>>> While we made good progress, there is still a lot todo. The efforts
> >>>> and
> >>>> open tasks are tracked in [1]. A lot of effort is currently done to
> >>>> switch the MicroProfile impl to MP Smallrye impls in order to move
> >>>> to
> >>>> the jakarta namespace [2].
> >>>>
> >>>> If you are interested in contributing to our TomEE 9 efforts, we
> >>>> can
> >>>> surely find some beginner friendly tasks in this area.
> >>>>
> >>>> Gruß
> >>>> Richard
> >>>>
> >>>>
> >>>> [1] https://issues.apache.org/jira/browse/TOMEE-3862
> >>>> [2]
> >>>> https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
> >>>>
> >>>>
> >>>> Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
> >>>>> Hi!
> >>>>>
> >>>>> I live in Hungary. I am working at an IT company as a software
> >>>>> developer, I
> >>>>> develop java
> >>>>> webapps with jsf (PrimeFaces) and microservice like apps without
> >>>>> any
> >>>>> container technology
> >>>>> and Oracle database.
> >>>>>
> >>>>> We want to switch to jakarta ee 9 at the company, but
> >>>>> unfortunately
> >>>>> we ran
> >>>>> into problems with tomee 9 and I would like to contribute to
> >>>>> fixing
> >>>>> these
> >>>>> bugs and possibly improving tomee jakarta 10. (I'm sorry to read
> >>>>> on
> >>>>> another
> >>>>> tomee mailing list, that you had to skip jakarta ee 8 and 9
> >>>>> compliance
> >>>>> entirely)
> >>>>> I use java 11 and netbeans on windows 10. If we don't have to, we
> >>>>> don't
> >>>>> want to use another app server because we've been using tomee
> >>>>> since
> >>>>> 1.7.3.
> >>>>>
> >>>>> Best regards: Zoltán Tichov
> >>
>
>
Re: TOMEE-3824 New Jakarta EE 9 XML namespace not recognized in web-fragment.xml (was Re: How can I help?)
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
Hi Zoltán,
thanks for your PR [1] !
It usually takes some time for peope to review a PR. The best way to
proceed is, that - after you created a PR - you sent a follow up email
on your mail thread in which you asked for issue assignment.
GitHub mails are flodding our mailboxes and some people might have
filters in place and do not see it.
I left some comments. From a quick look at the codebase, I think, that
we need to add the web fragment to the "openejb-jee-accessors" module
as well (but I might be wrong ;) - at least this is done for all other
descriptor types.
A good place for a unit test would probably "openejb-core". Maybe
something like org.apache.openejb.jee.servlet31.DontFailOnUnusedTagTest
Gruß
Richard
[1] https://github.com/apache/tomee/pull/883
Am Donnerstag, dem 12.05.2022 um 18:10 +0200 schrieb Zoltán Tichov:
> Hi!
>
> If I have a pending pull request, can I work on another issue as
> well?
>
> Thanks: Zoltán
>
> On Tue, May 10, 2022 at 10:48 PM David Blevins <
> david.blevins@gmail.com>
> wrote:
>
> > Hi Zoltán!
> >
> > Really fantastic you have something working!
> >
> > If you create a PR that'a the best way to say "here are my changes,
> > can
> > you please review?"
> >
> > -
> > https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
> >
> > Any JDK 11 is fine since TomEE doesn't require a specific Java
> > vendor --
> > any Java 11 version is good.
> >
> > Once you have that PR ready, feel free to update this thread with
> > the
> > link. Discussion can happen in the PR as well, but definitely more
> > people
> > see it here.
> >
> >
> > -David
> >
> >
> > > On May 10, 2022, at 11:06 AM, Zoltán Tichov <
> > > zoltan.tichov@gmail.com>
> > wrote:
> > > Hi David!
> > >
> > > I made some changes and a testcase, how can I show these changes
> > > to
> > > somebody?
> > > Which JDK should I use? Now I use adoptOpenJDK 11 to run the
> > > tests.
> > >
> > > Thanks: Zoltán
> > >
> > > On Fri, May 6, 2022 at 1:27 AM David Blevins <
> > > david.blevins@gmail.com>
> > > wrote:
> > >
> > > > Hey Zoltán!
> > > >
> > > > Absolutely, you're welcome to fix the issue. I can assign the
> > > > issue to
> > > > you if you let me know your JIRA username. Make a comment on
> > > > the issue
> > and
> > > > that'll be the quickest way to send it.
> > > >
> > > > We intentionally have it setup so new people can't assign
> > > > issues to
> > > > themselves so that they're forced to come to the list where we
> > > > can get
> > them
> > > > off to the right start.
> > > >
> > > > On the issue you want to fix, most the code that would be
> > > > involved in
> > the
> > > > fix is here:
> > > >
> > > > -
> > > >
> > https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java
> > > > Some important history to help you. When J2EE got renamed to
> > > > Java EE,
> > the
> > > > namespaces changed. The TCK for full Java EE server tests that
> > > > all
> > > > historic namespaces can be supported. Our solution was to
> > > > create an
> > > > org.xml.sax.XMLFilter and dynamically rewrite the namespace on
> > > > any
> > document
> > > > we were given to the then latest namespace
> > > > http://java.sun.com/xml/ns/javaee
> > > >
> > > > -
> > > >
> > https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java#L291
> > > > The way JAXB works is all the namespaces are hardcoded and
> > > > without a
> > > > filter like the one we made, there'd be no way to support
> > > > multiple
> > > > namespaces. Those namespaces are all here:
> > > >
> > > > -
> > > >
> > https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/ObjectFactory.java
> > > > I did most that work, but it was 15 years ago and I don't
> > > > recall all the
> > > > details. Jean-Louis did the work for the Jakarta namespace. I
> > > > know
> > we're
> > > > testing at least some those old namespaces and the new
> > > > namespace. We
> > have
> > > > some test descriptors here:
> > > >
> > > > -
> > > >
> > https://github.com/apache/tomee/tree/master/container/openejb-jee/src/test/resources
> > > > I don't recall the name of those tests offhand, but if you
> > > > search for
> > the
> > > > names of some of those files that should get you close.
> > > >
> > > >
> > > > Now a couple thoughts as I see potential for some short-term
> > > > work and
> > some
> > > > longer-term work.
> > > >
> > > > - Long-term: We're clearly still referring to "
> > > > http://java.sun.com/xml/ns/javaee" as the primary
> > > > namespace. That's
> > not
> > > > going to age well. If someone has to write an email like this
> > > > in 15
> > years,
> > > > they'll likely have to explain what "javaee" is like I had to
> > > > harken
> > back
> > > > to "J2EE". We should probably make the new Jakarta EE
> > > > namespace be the
> > > > primary namespace and rework all the JAXB code and namespace
> > > > filters
> > > > accordingly.
> > > >
> > > > - Short-term: Do not do any of that and avoid opening that can
> > > > of worms
> > > > at all cost. Get the file to parse with the minimum change
> > > > possible.
> > Get
> > > > some experience with the code and a successful contribution in
> > > > the can.
> > > >
> > > > This is what I'd do regardless of (or because of?) years of
> > experience. I
> > > > always take the quick win before attempting the big one.
> > > >
> > > > If you get into the code and decide the big change sounds like
> > > > fun, we
> > can
> > > > make a ticket for it and plan it. Probably we'd want to shore
> > > > up any
> > test
> > > > coverage we'd be lacking and also get a full TCK run to see
> > > > what those
> > > > numbers look like so we can spot regressions.
> > > >
> > > > Hope some of this is helpful!
> > > >
> > > > Don't hesitate to be super noisy and ask lots and lots of
> > > > questions.
> > > > Silence is death. :)
> > > >
> > > >
> > > > -David
> > > >
> > > >
> > > > > On May 5, 2022, at 3:31 PM, Zoltán Tichov <
> > > > > zoltan.tichov@gmail.com>
> > > > wrote:
> > > > > Hi Richard!
> > > > > I found a ticket with a bug that I also encountered.The
> > > > > ticket is open
> > > > and
> > > > > unassigned.
> > > > > Should I try to fix it? If so, how can it be assigned to me?
> > > > > https://issues.apache.org/jira/browse/TOMEE-3824
> > > > >
> > > > > Best: Zoltán
> > > > >
> > > > > On Wed, Apr 27, 2022 at 8:36 AM Zowalla, Richard <
> > > > > richard.zowalla@hs-heilbronn.de> wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > it would certainly help to track these issues as an issue.
> > > > > >
> > > > > > Maybe they are already solved (as the code has evolved) but
> > > > > > maybe not,
> > > > > > so it would be good to have them.
> > > > > >
> > > > > > Gruß
> > > > > > Richard
> > > > > >
> > > > > > Am Dienstag, dem 26.04.2022 um 21:54 +0200 schrieb Zoltán
> > > > > > Tichov:
> > > > > > > Hi Richard!
> > > > > > >
> > > > > > > I have found two errors in Tomee 9.0.0-M7. Should I make
> > > > > > > tickets for
> > > > > > > these
> > > > > > > errors and try to fix them?
> > > > > > > Although they may have been fixed in the next version
> > > > > > > (9.0.0-M8)
> > > > > > >
> > > > > > > Zoltán
> > > > > > >
> > > > > > > On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
> > > > > > > richard.zowalla@hs-heilbronn.de> wrote:
> > > > > > >
> > > > > > > > Hi Zoltán,
> > > > > > > >
> > > > > > > > It's very great from you and it's truly awesome when a
> > > > > > > > long time
> > > > > > > > user
> > > > > > > > of TomEE decides to contribute :)
> > > > > > > >
> > > > > > > > First of all, do not get intimidated by your first
> > > > > > > > ticket. If it
> > > > > > > > ends
> > > > > > > > up being too hard or just not fun, let's find something
> > > > > > > > else for
> > > > > > > > you.
> > > > > > > > There is always plenty of work to do.
> > > > > > > >
> > > > > > > > We are currently working on TomEE 9. Therefore, we
> > > > > > > > moved away from
> > > > > > > > our
> > > > > > > > previous byte code transformation approach and switched
> > > > > > > > TomEE
> > > > > > > > master to
> > > > > > > > TomEE 9 (Jakarta).
> > > > > > > >
> > > > > > > > While we made good progress, there is still a lot todo.
> > > > > > > > The efforts
> > > > > > > > and
> > > > > > > > open tasks are tracked in [1]. A lot of effort is
> > > > > > > > currently done to
> > > > > > > > switch the MicroProfile impl to MP Smallrye impls in
> > > > > > > > order to move
> > > > > > > > to
> > > > > > > > the jakarta namespace [2].
> > > > > > > >
> > > > > > > > If you are interested in contributing to our TomEE 9
> > > > > > > > efforts, we
> > > > > > > > can
> > > > > > > > surely find some beginner friendly tasks in this area.
> > > > > > > >
> > > > > > > > Gruß
> > > > > > > > Richard
> > > > > > > >
> > > > > > > >
> > > > > > > > [1] https://issues.apache.org/jira/browse/TOMEE-3862
> > > > > > > > [2]
> > > > > > > > https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
> > > > > > > >
> > > > > > > >
> > > > > > > > Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb
> > > > > > > > Zoltán Tichov:
> > > > > > > > > Hi!
> > > > > > > > >
> > > > > > > > > I live in Hungary. I am working at an IT company as a
> > > > > > > > > software
> > > > > > > > > developer, I
> > > > > > > > > develop java
> > > > > > > > > webapps with jsf (PrimeFaces) and microservice like
> > > > > > > > > apps without
> > > > > > > > > any
> > > > > > > > > container technology
> > > > > > > > > and Oracle database.
> > > > > > > > >
> > > > > > > > > We want to switch to jakarta ee 9 at the company, but
> > > > > > > > > unfortunately
> > > > > > > > > we ran
> > > > > > > > > into problems with tomee 9 and I would like to
> > > > > > > > > contribute to
> > > > > > > > > fixing
> > > > > > > > > these
> > > > > > > > > bugs and possibly improving tomee jakarta 10. (I'm
> > > > > > > > > sorry to read
> > > > > > > > > on
> > > > > > > > > another
> > > > > > > > > tomee mailing list, that you had to skip jakarta ee 8
> > > > > > > > > and 9
> > > > > > > > > compliance
> > > > > > > > > entirely)
> > > > > > > > > I use java 11 and netbeans on windows 10. If we don't
> > > > > > > > > have to, we
> > > > > > > > > don't
> > > > > > > > > want to use another app server because we've been
> > > > > > > > > using tomee
> > > > > > > > > since
> > > > > > > > > 1.7.3.
> > > > > > > > >
> > > > > > > > > Best regards: Zoltán Tichov
Re: TOMEE-3824 New Jakarta EE 9 XML namespace not recognized in web-fragment.xml (was Re: How can I help?)
Posted by Zoltán Tichov <zo...@gmail.com>.
Hi!
If I have a pending pull request, can I work on another issue as well?
Thanks: Zoltán
On Tue, May 10, 2022 at 10:48 PM David Blevins <da...@gmail.com>
wrote:
> Hi Zoltán!
>
> Really fantastic you have something working!
>
> If you create a PR that'a the best way to say "here are my changes, can
> you please review?"
>
> -
> https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
>
> Any JDK 11 is fine since TomEE doesn't require a specific Java vendor --
> any Java 11 version is good.
>
> Once you have that PR ready, feel free to update this thread with the
> link. Discussion can happen in the PR as well, but definitely more people
> see it here.
>
>
> -David
>
>
> > On May 10, 2022, at 11:06 AM, Zoltán Tichov <zo...@gmail.com>
> wrote:
> >
> > Hi David!
> >
> > I made some changes and a testcase, how can I show these changes to
> > somebody?
> > Which JDK should I use? Now I use adoptOpenJDK 11 to run the tests.
> >
> > Thanks: Zoltán
> >
> > On Fri, May 6, 2022 at 1:27 AM David Blevins <da...@gmail.com>
> > wrote:
> >
> >> Hey Zoltán!
> >>
> >> Absolutely, you're welcome to fix the issue. I can assign the issue to
> >> you if you let me know your JIRA username. Make a comment on the issue
> and
> >> that'll be the quickest way to send it.
> >>
> >> We intentionally have it setup so new people can't assign issues to
> >> themselves so that they're forced to come to the list where we can get
> them
> >> off to the right start.
> >>
> >> On the issue you want to fix, most the code that would be involved in
> the
> >> fix is here:
> >>
> >> -
> >>
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java
> >>
> >> Some important history to help you. When J2EE got renamed to Java EE,
> the
> >> namespaces changed. The TCK for full Java EE server tests that all
> >> historic namespaces can be supported. Our solution was to create an
> >> org.xml.sax.XMLFilter and dynamically rewrite the namespace on any
> document
> >> we were given to the then latest namespace
> >> http://java.sun.com/xml/ns/javaee
> >>
> >> -
> >>
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java#L291
> >>
> >> The way JAXB works is all the namespaces are hardcoded and without a
> >> filter like the one we made, there'd be no way to support multiple
> >> namespaces. Those namespaces are all here:
> >>
> >> -
> >>
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/ObjectFactory.java
> >>
> >> I did most that work, but it was 15 years ago and I don't recall all the
> >> details. Jean-Louis did the work for the Jakarta namespace. I know
> we're
> >> testing at least some those old namespaces and the new namespace. We
> have
> >> some test descriptors here:
> >>
> >> -
> >>
> https://github.com/apache/tomee/tree/master/container/openejb-jee/src/test/resources
> >>
> >> I don't recall the name of those tests offhand, but if you search for
> the
> >> names of some of those files that should get you close.
> >>
> >>
> >> Now a couple thoughts as I see potential for some short-term work and
> some
> >> longer-term work.
> >>
> >> - Long-term: We're clearly still referring to "
> >> http://java.sun.com/xml/ns/javaee" as the primary namespace. That's
> not
> >> going to age well. If someone has to write an email like this in 15
> years,
> >> they'll likely have to explain what "javaee" is like I had to harken
> back
> >> to "J2EE". We should probably make the new Jakarta EE namespace be the
> >> primary namespace and rework all the JAXB code and namespace filters
> >> accordingly.
> >>
> >> - Short-term: Do not do any of that and avoid opening that can of worms
> >> at all cost. Get the file to parse with the minimum change possible.
> Get
> >> some experience with the code and a successful contribution in the can.
> >>
> >> This is what I'd do regardless of (or because of?) years of
> experience. I
> >> always take the quick win before attempting the big one.
> >>
> >> If you get into the code and decide the big change sounds like fun, we
> can
> >> make a ticket for it and plan it. Probably we'd want to shore up any
> test
> >> coverage we'd be lacking and also get a full TCK run to see what those
> >> numbers look like so we can spot regressions.
> >>
> >> Hope some of this is helpful!
> >>
> >> Don't hesitate to be super noisy and ask lots and lots of questions.
> >> Silence is death. :)
> >>
> >>
> >> -David
> >>
> >>
> >>> On May 5, 2022, at 3:31 PM, Zoltán Tichov <zo...@gmail.com>
> >> wrote:
> >>>
> >>> Hi Richard!
> >>> I found a ticket with a bug that I also encountered.The ticket is open
> >> and
> >>> unassigned.
> >>> Should I try to fix it? If so, how can it be assigned to me?
> >>> https://issues.apache.org/jira/browse/TOMEE-3824
> >>>
> >>> Best: Zoltán
> >>>
> >>> On Wed, Apr 27, 2022 at 8:36 AM Zowalla, Richard <
> >>> richard.zowalla@hs-heilbronn.de> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> it would certainly help to track these issues as an issue.
> >>>>
> >>>> Maybe they are already solved (as the code has evolved) but maybe not,
> >>>> so it would be good to have them.
> >>>>
> >>>> Gruß
> >>>> Richard
> >>>>
> >>>> Am Dienstag, dem 26.04.2022 um 21:54 +0200 schrieb Zoltán Tichov:
> >>>>> Hi Richard!
> >>>>>
> >>>>> I have found two errors in Tomee 9.0.0-M7. Should I make tickets for
> >>>>> these
> >>>>> errors and try to fix them?
> >>>>> Although they may have been fixed in the next version (9.0.0-M8)
> >>>>>
> >>>>> Zoltán
> >>>>>
> >>>>> On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
> >>>>> richard.zowalla@hs-heilbronn.de> wrote:
> >>>>>
> >>>>>> Hi Zoltán,
> >>>>>>
> >>>>>> It's very great from you and it's truly awesome when a long time
> >>>>>> user
> >>>>>> of TomEE decides to contribute :)
> >>>>>>
> >>>>>> First of all, do not get intimidated by your first ticket. If it
> >>>>>> ends
> >>>>>> up being too hard or just not fun, let's find something else for
> >>>>>> you.
> >>>>>> There is always plenty of work to do.
> >>>>>>
> >>>>>> We are currently working on TomEE 9. Therefore, we moved away from
> >>>>>> our
> >>>>>> previous byte code transformation approach and switched TomEE
> >>>>>> master to
> >>>>>> TomEE 9 (Jakarta).
> >>>>>>
> >>>>>> While we made good progress, there is still a lot todo. The efforts
> >>>>>> and
> >>>>>> open tasks are tracked in [1]. A lot of effort is currently done to
> >>>>>> switch the MicroProfile impl to MP Smallrye impls in order to move
> >>>>>> to
> >>>>>> the jakarta namespace [2].
> >>>>>>
> >>>>>> If you are interested in contributing to our TomEE 9 efforts, we
> >>>>>> can
> >>>>>> surely find some beginner friendly tasks in this area.
> >>>>>>
> >>>>>> Gruß
> >>>>>> Richard
> >>>>>>
> >>>>>>
> >>>>>> [1] https://issues.apache.org/jira/browse/TOMEE-3862
> >>>>>> [2]
> >>>>>> https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
> >>>>>>
> >>>>>>
> >>>>>> Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
> >>>>>>> Hi!
> >>>>>>>
> >>>>>>> I live in Hungary. I am working at an IT company as a software
> >>>>>>> developer, I
> >>>>>>> develop java
> >>>>>>> webapps with jsf (PrimeFaces) and microservice like apps without
> >>>>>>> any
> >>>>>>> container technology
> >>>>>>> and Oracle database.
> >>>>>>>
> >>>>>>> We want to switch to jakarta ee 9 at the company, but
> >>>>>>> unfortunately
> >>>>>>> we ran
> >>>>>>> into problems with tomee 9 and I would like to contribute to
> >>>>>>> fixing
> >>>>>>> these
> >>>>>>> bugs and possibly improving tomee jakarta 10. (I'm sorry to read
> >>>>>>> on
> >>>>>>> another
> >>>>>>> tomee mailing list, that you had to skip jakarta ee 8 and 9
> >>>>>>> compliance
> >>>>>>> entirely)
> >>>>>>> I use java 11 and netbeans on windows 10. If we don't have to, we
> >>>>>>> don't
> >>>>>>> want to use another app server because we've been using tomee
> >>>>>>> since
> >>>>>>> 1.7.3.
> >>>>>>>
> >>>>>>> Best regards: Zoltán Tichov
> >>>>
> >>
> >>
>
>
Re: TOMEE-3824 New Jakarta EE 9 XML namespace not recognized in web-fragment.xml (was Re: How can I help?)
Posted by David Blevins <da...@gmail.com>.
Hi Zoltán!
Really fantastic you have something working!
If you create a PR that'a the best way to say "here are my changes, can you please review?"
- https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
Any JDK 11 is fine since TomEE doesn't require a specific Java vendor -- any Java 11 version is good.
Once you have that PR ready, feel free to update this thread with the link. Discussion can happen in the PR as well, but definitely more people see it here.
-David
> On May 10, 2022, at 11:06 AM, Zoltán Tichov <zo...@gmail.com> wrote:
>
> Hi David!
>
> I made some changes and a testcase, how can I show these changes to
> somebody?
> Which JDK should I use? Now I use adoptOpenJDK 11 to run the tests.
>
> Thanks: Zoltán
>
> On Fri, May 6, 2022 at 1:27 AM David Blevins <da...@gmail.com>
> wrote:
>
>> Hey Zoltán!
>>
>> Absolutely, you're welcome to fix the issue. I can assign the issue to
>> you if you let me know your JIRA username. Make a comment on the issue and
>> that'll be the quickest way to send it.
>>
>> We intentionally have it setup so new people can't assign issues to
>> themselves so that they're forced to come to the list where we can get them
>> off to the right start.
>>
>> On the issue you want to fix, most the code that would be involved in the
>> fix is here:
>>
>> -
>> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java
>>
>> Some important history to help you. When J2EE got renamed to Java EE, the
>> namespaces changed. The TCK for full Java EE server tests that all
>> historic namespaces can be supported. Our solution was to create an
>> org.xml.sax.XMLFilter and dynamically rewrite the namespace on any document
>> we were given to the then latest namespace
>> http://java.sun.com/xml/ns/javaee
>>
>> -
>> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java#L291
>>
>> The way JAXB works is all the namespaces are hardcoded and without a
>> filter like the one we made, there'd be no way to support multiple
>> namespaces. Those namespaces are all here:
>>
>> -
>> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/ObjectFactory.java
>>
>> I did most that work, but it was 15 years ago and I don't recall all the
>> details. Jean-Louis did the work for the Jakarta namespace. I know we're
>> testing at least some those old namespaces and the new namespace. We have
>> some test descriptors here:
>>
>> -
>> https://github.com/apache/tomee/tree/master/container/openejb-jee/src/test/resources
>>
>> I don't recall the name of those tests offhand, but if you search for the
>> names of some of those files that should get you close.
>>
>>
>> Now a couple thoughts as I see potential for some short-term work and some
>> longer-term work.
>>
>> - Long-term: We're clearly still referring to "
>> http://java.sun.com/xml/ns/javaee" as the primary namespace. That's not
>> going to age well. If someone has to write an email like this in 15 years,
>> they'll likely have to explain what "javaee" is like I had to harken back
>> to "J2EE". We should probably make the new Jakarta EE namespace be the
>> primary namespace and rework all the JAXB code and namespace filters
>> accordingly.
>>
>> - Short-term: Do not do any of that and avoid opening that can of worms
>> at all cost. Get the file to parse with the minimum change possible. Get
>> some experience with the code and a successful contribution in the can.
>>
>> This is what I'd do regardless of (or because of?) years of experience. I
>> always take the quick win before attempting the big one.
>>
>> If you get into the code and decide the big change sounds like fun, we can
>> make a ticket for it and plan it. Probably we'd want to shore up any test
>> coverage we'd be lacking and also get a full TCK run to see what those
>> numbers look like so we can spot regressions.
>>
>> Hope some of this is helpful!
>>
>> Don't hesitate to be super noisy and ask lots and lots of questions.
>> Silence is death. :)
>>
>>
>> -David
>>
>>
>>> On May 5, 2022, at 3:31 PM, Zoltán Tichov <zo...@gmail.com>
>> wrote:
>>>
>>> Hi Richard!
>>> I found a ticket with a bug that I also encountered.The ticket is open
>> and
>>> unassigned.
>>> Should I try to fix it? If so, how can it be assigned to me?
>>> https://issues.apache.org/jira/browse/TOMEE-3824
>>>
>>> Best: Zoltán
>>>
>>> On Wed, Apr 27, 2022 at 8:36 AM Zowalla, Richard <
>>> richard.zowalla@hs-heilbronn.de> wrote:
>>>
>>>> Hi,
>>>>
>>>> it would certainly help to track these issues as an issue.
>>>>
>>>> Maybe they are already solved (as the code has evolved) but maybe not,
>>>> so it would be good to have them.
>>>>
>>>> Gruß
>>>> Richard
>>>>
>>>> Am Dienstag, dem 26.04.2022 um 21:54 +0200 schrieb Zoltán Tichov:
>>>>> Hi Richard!
>>>>>
>>>>> I have found two errors in Tomee 9.0.0-M7. Should I make tickets for
>>>>> these
>>>>> errors and try to fix them?
>>>>> Although they may have been fixed in the next version (9.0.0-M8)
>>>>>
>>>>> Zoltán
>>>>>
>>>>> On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
>>>>> richard.zowalla@hs-heilbronn.de> wrote:
>>>>>
>>>>>> Hi Zoltán,
>>>>>>
>>>>>> It's very great from you and it's truly awesome when a long time
>>>>>> user
>>>>>> of TomEE decides to contribute :)
>>>>>>
>>>>>> First of all, do not get intimidated by your first ticket. If it
>>>>>> ends
>>>>>> up being too hard or just not fun, let's find something else for
>>>>>> you.
>>>>>> There is always plenty of work to do.
>>>>>>
>>>>>> We are currently working on TomEE 9. Therefore, we moved away from
>>>>>> our
>>>>>> previous byte code transformation approach and switched TomEE
>>>>>> master to
>>>>>> TomEE 9 (Jakarta).
>>>>>>
>>>>>> While we made good progress, there is still a lot todo. The efforts
>>>>>> and
>>>>>> open tasks are tracked in [1]. A lot of effort is currently done to
>>>>>> switch the MicroProfile impl to MP Smallrye impls in order to move
>>>>>> to
>>>>>> the jakarta namespace [2].
>>>>>>
>>>>>> If you are interested in contributing to our TomEE 9 efforts, we
>>>>>> can
>>>>>> surely find some beginner friendly tasks in this area.
>>>>>>
>>>>>> Gruß
>>>>>> Richard
>>>>>>
>>>>>>
>>>>>> [1] https://issues.apache.org/jira/browse/TOMEE-3862
>>>>>> [2]
>>>>>> https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
>>>>>>
>>>>>>
>>>>>> Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
>>>>>>> Hi!
>>>>>>>
>>>>>>> I live in Hungary. I am working at an IT company as a software
>>>>>>> developer, I
>>>>>>> develop java
>>>>>>> webapps with jsf (PrimeFaces) and microservice like apps without
>>>>>>> any
>>>>>>> container technology
>>>>>>> and Oracle database.
>>>>>>>
>>>>>>> We want to switch to jakarta ee 9 at the company, but
>>>>>>> unfortunately
>>>>>>> we ran
>>>>>>> into problems with tomee 9 and I would like to contribute to
>>>>>>> fixing
>>>>>>> these
>>>>>>> bugs and possibly improving tomee jakarta 10. (I'm sorry to read
>>>>>>> on
>>>>>>> another
>>>>>>> tomee mailing list, that you had to skip jakarta ee 8 and 9
>>>>>>> compliance
>>>>>>> entirely)
>>>>>>> I use java 11 and netbeans on windows 10. If we don't have to, we
>>>>>>> don't
>>>>>>> want to use another app server because we've been using tomee
>>>>>>> since
>>>>>>> 1.7.3.
>>>>>>>
>>>>>>> Best regards: Zoltán Tichov
>>>>
>>
>>
Re: TOMEE-3824 New Jakarta EE 9 XML namespace not recognized in web-fragment.xml (was Re: How can I help?)
Posted by Zoltán Tichov <zo...@gmail.com>.
Hi David!
I made some changes and a testcase, how can I show these changes to
somebody?
Which JDK should I use? Now I use adoptOpenJDK 11 to run the tests.
Thanks: Zoltán
On Fri, May 6, 2022 at 1:27 AM David Blevins <da...@gmail.com>
wrote:
> Hey Zoltán!
>
> Absolutely, you're welcome to fix the issue. I can assign the issue to
> you if you let me know your JIRA username. Make a comment on the issue and
> that'll be the quickest way to send it.
>
> We intentionally have it setup so new people can't assign issues to
> themselves so that they're forced to come to the list where we can get them
> off to the right start.
>
> On the issue you want to fix, most the code that would be involved in the
> fix is here:
>
> -
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java
>
> Some important history to help you. When J2EE got renamed to Java EE, the
> namespaces changed. The TCK for full Java EE server tests that all
> historic namespaces can be supported. Our solution was to create an
> org.xml.sax.XMLFilter and dynamically rewrite the namespace on any document
> we were given to the then latest namespace
> http://java.sun.com/xml/ns/javaee
>
> -
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java#L291
>
> The way JAXB works is all the namespaces are hardcoded and without a
> filter like the one we made, there'd be no way to support multiple
> namespaces. Those namespaces are all here:
>
> -
> https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/ObjectFactory.java
>
> I did most that work, but it was 15 years ago and I don't recall all the
> details. Jean-Louis did the work for the Jakarta namespace. I know we're
> testing at least some those old namespaces and the new namespace. We have
> some test descriptors here:
>
> -
> https://github.com/apache/tomee/tree/master/container/openejb-jee/src/test/resources
>
> I don't recall the name of those tests offhand, but if you search for the
> names of some of those files that should get you close.
>
>
> Now a couple thoughts as I see potential for some short-term work and some
> longer-term work.
>
> - Long-term: We're clearly still referring to "
> http://java.sun.com/xml/ns/javaee" as the primary namespace. That's not
> going to age well. If someone has to write an email like this in 15 years,
> they'll likely have to explain what "javaee" is like I had to harken back
> to "J2EE". We should probably make the new Jakarta EE namespace be the
> primary namespace and rework all the JAXB code and namespace filters
> accordingly.
>
> - Short-term: Do not do any of that and avoid opening that can of worms
> at all cost. Get the file to parse with the minimum change possible. Get
> some experience with the code and a successful contribution in the can.
>
> This is what I'd do regardless of (or because of?) years of experience. I
> always take the quick win before attempting the big one.
>
> If you get into the code and decide the big change sounds like fun, we can
> make a ticket for it and plan it. Probably we'd want to shore up any test
> coverage we'd be lacking and also get a full TCK run to see what those
> numbers look like so we can spot regressions.
>
> Hope some of this is helpful!
>
> Don't hesitate to be super noisy and ask lots and lots of questions.
> Silence is death. :)
>
>
> -David
>
>
> > On May 5, 2022, at 3:31 PM, Zoltán Tichov <zo...@gmail.com>
> wrote:
> >
> > Hi Richard!
> > I found a ticket with a bug that I also encountered.The ticket is open
> and
> > unassigned.
> > Should I try to fix it? If so, how can it be assigned to me?
> > https://issues.apache.org/jira/browse/TOMEE-3824
> >
> > Best: Zoltán
> >
> > On Wed, Apr 27, 2022 at 8:36 AM Zowalla, Richard <
> > richard.zowalla@hs-heilbronn.de> wrote:
> >
> >> Hi,
> >>
> >> it would certainly help to track these issues as an issue.
> >>
> >> Maybe they are already solved (as the code has evolved) but maybe not,
> >> so it would be good to have them.
> >>
> >> Gruß
> >> Richard
> >>
> >> Am Dienstag, dem 26.04.2022 um 21:54 +0200 schrieb Zoltán Tichov:
> >>> Hi Richard!
> >>>
> >>> I have found two errors in Tomee 9.0.0-M7. Should I make tickets for
> >>> these
> >>> errors and try to fix them?
> >>> Although they may have been fixed in the next version (9.0.0-M8)
> >>>
> >>> Zoltán
> >>>
> >>> On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
> >>> richard.zowalla@hs-heilbronn.de> wrote:
> >>>
> >>>> Hi Zoltán,
> >>>>
> >>>> It's very great from you and it's truly awesome when a long time
> >>>> user
> >>>> of TomEE decides to contribute :)
> >>>>
> >>>> First of all, do not get intimidated by your first ticket. If it
> >>>> ends
> >>>> up being too hard or just not fun, let's find something else for
> >>>> you.
> >>>> There is always plenty of work to do.
> >>>>
> >>>> We are currently working on TomEE 9. Therefore, we moved away from
> >>>> our
> >>>> previous byte code transformation approach and switched TomEE
> >>>> master to
> >>>> TomEE 9 (Jakarta).
> >>>>
> >>>> While we made good progress, there is still a lot todo. The efforts
> >>>> and
> >>>> open tasks are tracked in [1]. A lot of effort is currently done to
> >>>> switch the MicroProfile impl to MP Smallrye impls in order to move
> >>>> to
> >>>> the jakarta namespace [2].
> >>>>
> >>>> If you are interested in contributing to our TomEE 9 efforts, we
> >>>> can
> >>>> surely find some beginner friendly tasks in this area.
> >>>>
> >>>> Gruß
> >>>> Richard
> >>>>
> >>>>
> >>>> [1] https://issues.apache.org/jira/browse/TOMEE-3862
> >>>> [2]
> >>>> https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
> >>>>
> >>>>
> >>>> Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
> >>>>> Hi!
> >>>>>
> >>>>> I live in Hungary. I am working at an IT company as a software
> >>>>> developer, I
> >>>>> develop java
> >>>>> webapps with jsf (PrimeFaces) and microservice like apps without
> >>>>> any
> >>>>> container technology
> >>>>> and Oracle database.
> >>>>>
> >>>>> We want to switch to jakarta ee 9 at the company, but
> >>>>> unfortunately
> >>>>> we ran
> >>>>> into problems with tomee 9 and I would like to contribute to
> >>>>> fixing
> >>>>> these
> >>>>> bugs and possibly improving tomee jakarta 10. (I'm sorry to read
> >>>>> on
> >>>>> another
> >>>>> tomee mailing list, that you had to skip jakarta ee 8 and 9
> >>>>> compliance
> >>>>> entirely)
> >>>>> I use java 11 and netbeans on windows 10. If we don't have to, we
> >>>>> don't
> >>>>> want to use another app server because we've been using tomee
> >>>>> since
> >>>>> 1.7.3.
> >>>>>
> >>>>> Best regards: Zoltán Tichov
> >>
>
>
TOMEE-3824 New Jakarta EE 9 XML namespace not recognized in web-fragment.xml (was Re: How can I help?)
Posted by David Blevins <da...@gmail.com>.
Hey Zoltán!
Absolutely, you're welcome to fix the issue. I can assign the issue to you if you let me know your JIRA username. Make a comment on the issue and that'll be the quickest way to send it.
We intentionally have it setup so new people can't assign issues to themselves so that they're forced to come to the list where we can get them off to the right start.
On the issue you want to fix, most the code that would be involved in the fix is here:
- https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java
Some important history to help you. When J2EE got renamed to Java EE, the namespaces changed. The TCK for full Java EE server tests that all historic namespaces can be supported. Our solution was to create an org.xml.sax.XMLFilter and dynamically rewrite the namespace on any document we were given to the then latest namespace http://java.sun.com/xml/ns/javaee
- https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/JaxbJavaee.java#L291
The way JAXB works is all the namespaces are hardcoded and without a filter like the one we made, there'd be no way to support multiple namespaces. Those namespaces are all here:
- https://github.com/apache/tomee/blob/master/container/openejb-jee/src/main/java/org/apache/openejb/jee/ObjectFactory.java
I did most that work, but it was 15 years ago and I don't recall all the details. Jean-Louis did the work for the Jakarta namespace. I know we're testing at least some those old namespaces and the new namespace. We have some test descriptors here:
- https://github.com/apache/tomee/tree/master/container/openejb-jee/src/test/resources
I don't recall the name of those tests offhand, but if you search for the names of some of those files that should get you close.
Now a couple thoughts as I see potential for some short-term work and some longer-term work.
- Long-term: We're clearly still referring to "http://java.sun.com/xml/ns/javaee" as the primary namespace. That's not going to age well. If someone has to write an email like this in 15 years, they'll likely have to explain what "javaee" is like I had to harken back to "J2EE". We should probably make the new Jakarta EE namespace be the primary namespace and rework all the JAXB code and namespace filters accordingly.
- Short-term: Do not do any of that and avoid opening that can of worms at all cost. Get the file to parse with the minimum change possible. Get some experience with the code and a successful contribution in the can.
This is what I'd do regardless of (or because of?) years of experience. I always take the quick win before attempting the big one.
If you get into the code and decide the big change sounds like fun, we can make a ticket for it and plan it. Probably we'd want to shore up any test coverage we'd be lacking and also get a full TCK run to see what those numbers look like so we can spot regressions.
Hope some of this is helpful!
Don't hesitate to be super noisy and ask lots and lots of questions. Silence is death. :)
-David
> On May 5, 2022, at 3:31 PM, Zoltán Tichov <zo...@gmail.com> wrote:
>
> Hi Richard!
> I found a ticket with a bug that I also encountered.The ticket is open and
> unassigned.
> Should I try to fix it? If so, how can it be assigned to me?
> https://issues.apache.org/jira/browse/TOMEE-3824
>
> Best: Zoltán
>
> On Wed, Apr 27, 2022 at 8:36 AM Zowalla, Richard <
> richard.zowalla@hs-heilbronn.de> wrote:
>
>> Hi,
>>
>> it would certainly help to track these issues as an issue.
>>
>> Maybe they are already solved (as the code has evolved) but maybe not,
>> so it would be good to have them.
>>
>> Gruß
>> Richard
>>
>> Am Dienstag, dem 26.04.2022 um 21:54 +0200 schrieb Zoltán Tichov:
>>> Hi Richard!
>>>
>>> I have found two errors in Tomee 9.0.0-M7. Should I make tickets for
>>> these
>>> errors and try to fix them?
>>> Although they may have been fixed in the next version (9.0.0-M8)
>>>
>>> Zoltán
>>>
>>> On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
>>> richard.zowalla@hs-heilbronn.de> wrote:
>>>
>>>> Hi Zoltán,
>>>>
>>>> It's very great from you and it's truly awesome when a long time
>>>> user
>>>> of TomEE decides to contribute :)
>>>>
>>>> First of all, do not get intimidated by your first ticket. If it
>>>> ends
>>>> up being too hard or just not fun, let's find something else for
>>>> you.
>>>> There is always plenty of work to do.
>>>>
>>>> We are currently working on TomEE 9. Therefore, we moved away from
>>>> our
>>>> previous byte code transformation approach and switched TomEE
>>>> master to
>>>> TomEE 9 (Jakarta).
>>>>
>>>> While we made good progress, there is still a lot todo. The efforts
>>>> and
>>>> open tasks are tracked in [1]. A lot of effort is currently done to
>>>> switch the MicroProfile impl to MP Smallrye impls in order to move
>>>> to
>>>> the jakarta namespace [2].
>>>>
>>>> If you are interested in contributing to our TomEE 9 efforts, we
>>>> can
>>>> surely find some beginner friendly tasks in this area.
>>>>
>>>> Gruß
>>>> Richard
>>>>
>>>>
>>>> [1] https://issues.apache.org/jira/browse/TOMEE-3862
>>>> [2]
>>>> https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
>>>>
>>>>
>>>> Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
>>>>> Hi!
>>>>>
>>>>> I live in Hungary. I am working at an IT company as a software
>>>>> developer, I
>>>>> develop java
>>>>> webapps with jsf (PrimeFaces) and microservice like apps without
>>>>> any
>>>>> container technology
>>>>> and Oracle database.
>>>>>
>>>>> We want to switch to jakarta ee 9 at the company, but
>>>>> unfortunately
>>>>> we ran
>>>>> into problems with tomee 9 and I would like to contribute to
>>>>> fixing
>>>>> these
>>>>> bugs and possibly improving tomee jakarta 10. (I'm sorry to read
>>>>> on
>>>>> another
>>>>> tomee mailing list, that you had to skip jakarta ee 8 and 9
>>>>> compliance
>>>>> entirely)
>>>>> I use java 11 and netbeans on windows 10. If we don't have to, we
>>>>> don't
>>>>> want to use another app server because we've been using tomee
>>>>> since
>>>>> 1.7.3.
>>>>>
>>>>> Best regards: Zoltán Tichov
>>
Re: How can I help?
Posted by Zoltán Tichov <zo...@gmail.com>.
Hi Richard!
I found a ticket with a bug that I also encountered.The ticket is open and
unassigned.
Should I try to fix it? If so, how can it be assigned to me?
https://issues.apache.org/jira/browse/TOMEE-3824
Best: Zoltán
On Wed, Apr 27, 2022 at 8:36 AM Zowalla, Richard <
richard.zowalla@hs-heilbronn.de> wrote:
> Hi,
>
> it would certainly help to track these issues as an issue.
>
> Maybe they are already solved (as the code has evolved) but maybe not,
> so it would be good to have them.
>
> Gruß
> Richard
>
> Am Dienstag, dem 26.04.2022 um 21:54 +0200 schrieb Zoltán Tichov:
> > Hi Richard!
> >
> > I have found two errors in Tomee 9.0.0-M7. Should I make tickets for
> > these
> > errors and try to fix them?
> > Although they may have been fixed in the next version (9.0.0-M8)
> >
> > Zoltán
> >
> > On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
> > richard.zowalla@hs-heilbronn.de> wrote:
> >
> > > Hi Zoltán,
> > >
> > > It's very great from you and it's truly awesome when a long time
> > > user
> > > of TomEE decides to contribute :)
> > >
> > > First of all, do not get intimidated by your first ticket. If it
> > > ends
> > > up being too hard or just not fun, let's find something else for
> > > you.
> > > There is always plenty of work to do.
> > >
> > > We are currently working on TomEE 9. Therefore, we moved away from
> > > our
> > > previous byte code transformation approach and switched TomEE
> > > master to
> > > TomEE 9 (Jakarta).
> > >
> > > While we made good progress, there is still a lot todo. The efforts
> > > and
> > > open tasks are tracked in [1]. A lot of effort is currently done to
> > > switch the MicroProfile impl to MP Smallrye impls in order to move
> > > to
> > > the jakarta namespace [2].
> > >
> > > If you are interested in contributing to our TomEE 9 efforts, we
> > > can
> > > surely find some beginner friendly tasks in this area.
> > >
> > > Gruß
> > > Richard
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/TOMEE-3862
> > > [2]
> > > https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
> > >
> > >
> > > Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
> > > > Hi!
> > > >
> > > > I live in Hungary. I am working at an IT company as a software
> > > > developer, I
> > > > develop java
> > > > webapps with jsf (PrimeFaces) and microservice like apps without
> > > > any
> > > > container technology
> > > > and Oracle database.
> > > >
> > > > We want to switch to jakarta ee 9 at the company, but
> > > > unfortunately
> > > > we ran
> > > > into problems with tomee 9 and I would like to contribute to
> > > > fixing
> > > > these
> > > > bugs and possibly improving tomee jakarta 10. (I'm sorry to read
> > > > on
> > > > another
> > > > tomee mailing list, that you had to skip jakarta ee 8 and 9
> > > > compliance
> > > > entirely)
> > > > I use java 11 and netbeans on windows 10. If we don't have to, we
> > > > don't
> > > > want to use another app server because we've been using tomee
> > > > since
> > > > 1.7.3.
> > > >
> > > > Best regards: Zoltán Tichov
>
Re: How can I help?
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
Hi,
it would certainly help to track these issues as an issue.
Maybe they are already solved (as the code has evolved) but maybe not,
so it would be good to have them.
Gruß
Richard
Am Dienstag, dem 26.04.2022 um 21:54 +0200 schrieb Zoltán Tichov:
> Hi Richard!
>
> I have found two errors in Tomee 9.0.0-M7. Should I make tickets for
> these
> errors and try to fix them?
> Although they may have been fixed in the next version (9.0.0-M8)
>
> Zoltán
>
> On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
> richard.zowalla@hs-heilbronn.de> wrote:
>
> > Hi Zoltán,
> >
> > It's very great from you and it's truly awesome when a long time
> > user
> > of TomEE decides to contribute :)
> >
> > First of all, do not get intimidated by your first ticket. If it
> > ends
> > up being too hard or just not fun, let's find something else for
> > you.
> > There is always plenty of work to do.
> >
> > We are currently working on TomEE 9. Therefore, we moved away from
> > our
> > previous byte code transformation approach and switched TomEE
> > master to
> > TomEE 9 (Jakarta).
> >
> > While we made good progress, there is still a lot todo. The efforts
> > and
> > open tasks are tracked in [1]. A lot of effort is currently done to
> > switch the MicroProfile impl to MP Smallrye impls in order to move
> > to
> > the jakarta namespace [2].
> >
> > If you are interested in contributing to our TomEE 9 efforts, we
> > can
> > surely find some beginner friendly tasks in this area.
> >
> > Gruß
> > Richard
> >
> >
> > [1] https://issues.apache.org/jira/browse/TOMEE-3862
> > [2]
> > https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
> >
> >
> > Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
> > > Hi!
> > >
> > > I live in Hungary. I am working at an IT company as a software
> > > developer, I
> > > develop java
> > > webapps with jsf (PrimeFaces) and microservice like apps without
> > > any
> > > container technology
> > > and Oracle database.
> > >
> > > We want to switch to jakarta ee 9 at the company, but
> > > unfortunately
> > > we ran
> > > into problems with tomee 9 and I would like to contribute to
> > > fixing
> > > these
> > > bugs and possibly improving tomee jakarta 10. (I'm sorry to read
> > > on
> > > another
> > > tomee mailing list, that you had to skip jakarta ee 8 and 9
> > > compliance
> > > entirely)
> > > I use java 11 and netbeans on windows 10. If we don't have to, we
> > > don't
> > > want to use another app server because we've been using tomee
> > > since
> > > 1.7.3.
> > >
> > > Best regards: Zoltán Tichov
Re: How can I help?
Posted by Zoltán Tichov <zo...@gmail.com>.
Hi Richard!
I have found two errors in Tomee 9.0.0-M7. Should I make tickets for these
errors and try to fix them?
Although they may have been fixed in the next version (9.0.0-M8)
Zoltán
On Sun, Apr 24, 2022 at 11:06 AM Zowalla, Richard <
richard.zowalla@hs-heilbronn.de> wrote:
> Hi Zoltán,
>
> It's very great from you and it's truly awesome when a long time user
> of TomEE decides to contribute :)
>
> First of all, do not get intimidated by your first ticket. If it ends
> up being too hard or just not fun, let's find something else for you.
> There is always plenty of work to do.
>
> We are currently working on TomEE 9. Therefore, we moved away from our
> previous byte code transformation approach and switched TomEE master to
> TomEE 9 (Jakarta).
>
> While we made good progress, there is still a lot todo. The efforts and
> open tasks are tracked in [1]. A lot of effort is currently done to
> switch the MicroProfile impl to MP Smallrye impls in order to move to
> the jakarta namespace [2].
>
> If you are interested in contributing to our TomEE 9 efforts, we can
> surely find some beginner friendly tasks in this area.
>
> Gruß
> Richard
>
>
> [1] https://issues.apache.org/jira/browse/TOMEE-3862
> [2] https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
>
>
> Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
> > Hi!
> >
> > I live in Hungary. I am working at an IT company as a software
> > developer, I
> > develop java
> > webapps with jsf (PrimeFaces) and microservice like apps without any
> > container technology
> > and Oracle database.
> >
> > We want to switch to jakarta ee 9 at the company, but unfortunately
> > we ran
> > into problems with tomee 9 and I would like to contribute to fixing
> > these
> > bugs and possibly improving tomee jakarta 10. (I'm sorry to read on
> > another
> > tomee mailing list, that you had to skip jakarta ee 8 and 9
> > compliance
> > entirely)
> > I use java 11 and netbeans on windows 10. If we don't have to, we
> > don't
> > want to use another app server because we've been using tomee since
> > 1.7.3.
> >
> > Best regards: Zoltán Tichov
>
Re: How can I help?
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
Hi Zoltán,
It's very great from you and it's truly awesome when a long time user
of TomEE decides to contribute :)
First of all, do not get intimidated by your first ticket. If it ends
up being too hard or just not fun, let's find something else for you.
There is always plenty of work to do.
We are currently working on TomEE 9. Therefore, we moved away from our
previous byte code transformation approach and switched TomEE master to
TomEE 9 (Jakarta).
While we made good progress, there is still a lot todo. The efforts and
open tasks are tracked in [1]. A lot of effort is currently done to
switch the MicroProfile impl to MP Smallrye impls in order to move to
the jakarta namespace [2].
If you are interested in contributing to our TomEE 9 efforts, we can
surely find some beginner friendly tasks in this area.
Gruß
Richard
[1] https://issues.apache.org/jira/browse/TOMEE-3862
[2] https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
Am Samstag, dem 23.04.2022 um 20:21 +0200 schrieb Zoltán Tichov:
> Hi!
>
> I live in Hungary. I am working at an IT company as a software
> developer, I
> develop java
> webapps with jsf (PrimeFaces) and microservice like apps without any
> container technology
> and Oracle database.
>
> We want to switch to jakarta ee 9 at the company, but unfortunately
> we ran
> into problems with tomee 9 and I would like to contribute to fixing
> these
> bugs and possibly improving tomee jakarta 10. (I'm sorry to read on
> another
> tomee mailing list, that you had to skip jakarta ee 8 and 9
> compliance
> entirely)
> I use java 11 and netbeans on windows 10. If we don't have to, we
> don't
> want to use another app server because we've been using tomee since
> 1.7.3.
>
> Best regards: Zoltán Tichov