Re: OpenJDK is no more? [action required, please]

2022-05-06 Thread Jenkins, Rodney J (Rod)
All,

I have created the PR to the official images folks for the new TomEE images.

https://github.com/docker-library/official-images/pull/12385

Please go out and look at the new tags.  I have included many tags so that 
users can be very selective on the images they wish to use.

If anyone has an issue, please comment here or in the PR.  This was very 
complicated and I hope I did not make a mistake, lol.

Thanks,
Rod.


On 5/2/22, 12:41 PM, "Zowalla, Richard"  
wrote:

Thanks Rod!!

Am Montag, dem 02.05.2022 um 17:33 + schrieb Jenkins, Rodney J
(Rod):
> All,
> 
> I have added the Semeru images for Java 11 and 17 for TomEE 8 and 9.
> 
> Anything else anyone wants?
> 
> Thanks,
> Rod.
> 
> 
> 
> On 4/30/22, 12:35 PM, "Zowalla, Richard" <
> richard.zowa...@hs-heilbronn.de> wrote:
> 
> Nationwide Information Security Warning: This is an EXTERNAL
> email. Use CAUTION before clicking on links, opening attachments, or
> responding. (Sender: 
> dev-return-29380-JENKIR14=nationwide@tomee.apache.org)
> 
> -
> -
> 
> 
> Maybe 11 + 17 for OpenJ9/Semeru? ;)
> 
> Thanks.
> 
> Gruß
> Richard
> 
> Von: Jenkins, Rodney J (Rod) 
> Gesendet: Samstag, 30. April 2022 19:12:40
> An: dev@tomee.apache.org
> Betreff: Re: Re: Re: OpenJDK is no more?
> 
> Alex,
> 
> That explains why I did not see it, lol.
> 
> 
> 
> All,
> 
> I have created this PR for review:  
> https://github.com/tomitribe/docker-tomee/pull/66
> 
> This is not final, so if we want to add Semeru, I just need to
> know what java versions we would like to add.
> 
> Thank you,
> Rod.
> 
> 
> On 4/30/22, 11:16 AM, "Alex The Rocker" 
> wrote:
> 
> Nationwide Information Security Warning: This is an EXTERNAL
> email. Use CAUTION before clicking on links, opening attachments, or
> responding. (Sender: 
> dev-return-29378-JENKIR14=nationwide@tomee.apache.org)
> 
> -
> -
> 
> 
> Hi Rod,
> 
> You won't find any Semeru/OpenJ9 image based on Alpine,
> because this
> JVM is not supporter on Alpine (alas...)
> 
> Thanks,
> Alex
> 
> Le sam. 30 avr. 2022 à 18:10, Jenkins, Rodney J (Rod)
>  a écrit :
> >
> > Richard,
> >
> > I am fine with providing a Semeru/OpenJ9.  Would we want
> that or 8, 11, and 17?
> >
> > I do not see an alpine image, so it would just be adding a
> ubuntu image.
> >
> > Rod.
> >
> >
> > On 4/30/22, 1:30 AM, "Zowalla, Richard" <
> richard.zowa...@hs-heilbronn.de> wrote:
> >
> > Nationwide Information Security Warning: This is an
> EXTERNAL email. Use CAUTION before clicking on links, opening
> attachments, or responding. (Sender: 
> dev-return-29375-JENKIR14=nationwide@tomee.apache.org)
> >
> > ---
> ---
> >
> >
> > Hi,
> >
> > I think, that Alpine would be a great addition to
> shrink the images
> > sizes if it isn't too much work.
> >
> > I am also wondering, if we should provide a
> Semeru/OpenJ9
> > runtime - but I guess, that there isn't too much need
> for it, so it is
> > super low prio :D
> >
> > Gruß
> > Richard
> >
> >
> >
> > Am Freitag, dem 29.04.2022 um 21:18 + schrieb
> Jenkins, Rodney J
> > (Rod):
> > > Hello all,
> > >
> > > There is more information on the PR I noted earlier.
> > >
> > > Essentially, OpenJDK 17 is being dereplicated.  In
> addition OpenJDK 8
> > > and OpenJDK 11, "are not updated on an extreme
> priority."
> > >
> > > Given this new information, I propose the following:
> > > Move immediately to Temurin for Java 17.  (There have
> been many +1
> > > votes for this)
> > > We add a Temurin option for Java 8 and 11 should we
> lose support for
> > > those.  We would still leave OpenJDK as the default.
> 

Re: How Can I Help ?

2022-05-06 Thread AD
Hello Richard

Thank you so much for responding to my email request. Much appreciated.

Thanks for explaining in detail about how this works.

I do have experience in Java , Web services, Microservices , Azure , Cloud
development.

I do have experience in application servers as well , I have contributed in
migration of Weblogic/Websphere applications to Tomcat/Tomee and Jboss as
well

So I would like to know here how and where I can contribute , is it only in
the Tomee world ? or is there something else as well  .

Would be great if you can brief out the areas typically where we can
contribute

Thank you so much
-AD







On Fri, May 6, 2022 at 12:00 AM Zowalla, Richard <
richard.zowa...@hs-heilbronn.de> wrote:

> Hi AD,
>
> welcome to the mailing list and TomEE community.
>
> Do you have areas of expertise or a special field or topic of interest,
> you would like to contribute to?
>
> 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] as well as to get the EE9 plattform TCK
> running. If you are interested in contributing to our TomEE 9 efforts,
> we can surely find some beginner friendly tasks in this area.
>
> There was also some interest in doing another maintaince release of
> 7.1.x with some fixes and dependency updates, which could also be an
> area for contribution [3].
>
> It fully depends on your field of interest and your available resources
> / time, so it would be interesting to hear back from you.
>
> Last but not least: 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.
>
> Gruß
> Richard
>
>
> [1] https://issues.apache.org/jira/browse/TOMEE-3862
> [2] https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
> [3] https://lists.apache.org/thread/sz0kfocgd6248l2vxxgv3wjc5snh79q6
>
>
>
> Am Donnerstag, dem 05.05.2022 um 14:00 -0600 schrieb AD:
> > Hello
> >
> > I am new to this group and would like to offer help in any way I can.
> >
> > Please let me know
> >
> > Thank you
> > -AD
>


Re: TOMEE-3824 New Jakarta EE 9 XML namespace not recognized in web-fragment.xml (was Re: How can I help?)

2022-05-06 Thread Jonathan Gallimore
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 
wrote:

> Hi David!
>
> My JIRA username is eagleegg
>
> Thanks: Zoltán
>
>
> On Fri, May 6, 2022 at 1:27 AM David Blevins 
> 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 
> > 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.zowa...@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.zowa...@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 :)
> 

Re: TOMEE-3824 New Jakarta EE 9 XML namespace not recognized in web-fragment.xml (was Re: How can I help?)

2022-05-06 Thread Zoltán Tichov
Hi David!

My JIRA username is eagleegg

Thanks: Zoltán


On Fri, May 6, 2022 at 1:27 AM David Blevins 
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 
> 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.zowa...@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.zowa...@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
> 

[GitHub] [tomee] rzo1 merged pull request #882: Regenerated BOMs after dependency upgrades

2022-05-06 Thread GitBox


rzo1 merged PR #882:
URL: https://github.com/apache/tomee/pull/882


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [tomee] github-actions[bot] opened a new pull request, #882: Regenerated BOMs after dependency upgrades

2022-05-06 Thread GitBox


github-actions[bot] opened a new pull request, #882:
URL: https://github.com/apache/tomee/pull/882

   Found some uncommited changes (from BOM regeneration) after running build on 
TomEE 8.x branch


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [tomee] rzo1 merged pull request #881: Regenerated BOMs after dependency upgrades

2022-05-06 Thread GitBox


rzo1 merged PR #881:
URL: https://github.com/apache/tomee/pull/881


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: How Can I Help ?

2022-05-06 Thread Zowalla, Richard
Hi AD,
 
welcome to the mailing list and TomEE community.

Do you have areas of expertise or a special field or topic of interest,
you would like to contribute to?

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] as well as to get the EE9 plattform TCK
running. If you are interested in contributing to our TomEE 9 efforts,
we can surely find some beginner friendly tasks in this area.

There was also some interest in doing another maintaince release of
7.1.x with some fixes and dependency updates, which could also be an
area for contribution [3].

It fully depends on your field of interest and your available resources
/ time, so it would be interesting to hear back from you.

Last but not least: 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.

Gruß
Richard


[1] https://issues.apache.org/jira/browse/TOMEE-3862
[2] https://lists.apache.org/thread/hdntdhwqkr91o2mszojq66qcfzszw96p
[3] https://lists.apache.org/thread/sz0kfocgd6248l2vxxgv3wjc5snh79q6



Am Donnerstag, dem 05.05.2022 um 14:00 -0600 schrieb AD:
> Hello
> 
> I am new to this group and would like to offer help in any way I can.
> 
> Please let me know
> 
> Thank you
> -AD


smime.p7s
Description: S/MIME cryptographic signature