Thank you very much for the explanation. In the Email, I noticed JMS wasn’t mentioned. I think amq 18 offers a native client, but I might be remembering that correctly.
What areas could we help with? Sent from my iPhone > On May 23, 2023, at 2:09 AM, Richard Zowalla <[email protected]> wrote: > > Hi Jonathan, > > from a spec perspective: > > - Tomcat 10.0.x -> EE9 > - Tomcat 10.1.x -> EE10 > > Our "main" branch (or TomEE 10) will support EE10 based upon Tomcat > 10.1.x - we are currently working on the various 3rd party libs to make > that happen and to pass the TCK again. There was a discussion of the > current process here: [1] > > A bit of a problem is, that setting up the EE10 tck changed quiet a lot > between EE9 and EE10 + various ongoing work in the projects we depend > on. > > I don't know the progress on the TCK side, though. > > Hope it helps a bit > > Gruß > Richard > > > [1] https://lists.apache.org/thread/6xfzslqrfqq3o1mdywro2vhl60540foc > >> Am Montag, dem 22.05.2023 um 15:45 -0400 schrieb Jonathan S. Fisher: >> Hello TomEE team, >> >> I apologize for missing the discussion, and I've searched the archive >> but >> can't seem to find the correct thread. Tomcat 10.0.x was EOL'd in >> October >> last year and replaced by Tomcat 10.1.x. TomEE mainline depends on >> Tomcat >> 10.0.x. >> >> I know the TomEE team is currently backporting CVE patches into >> Tomcat >> 10.0.x. And I apologize if this is a stupid question with a simpler >> answer: >> Does TomEE mainline need to be on 10.1.x and if so, what areas need >> work? >> What's preventing the move to 10.1.x? >> >> Asking because we're looking ahead to next year, and my organization >> will >> (finally) have to get off Tomcat 9.5.x/TomEE 8.0.x when it goes EOL. >> I do >> have a little bit of dev capacity I can voluntell to help squash some >> simpler issues; they're mostly app developers and maybe not well >> suited for >> low level work but there's a first time for everything. Looking for >> ways to >> help smooth the transition, and fixing TomEE bugs is time well spent. >> >> Thank you, >> >
