Thanks for all the information As you can imagine, we're being pressurised from the management hierarchy to make sure that our outside-exposed IT infrastructure is "secure". Sadly, these pressures manifest in demands for "the latest version" for everything. Quite often those demands come externally and/or from people with limited understanding or concern of the products they're condemning or the nuances/difficulties of keeping them up to date, or the difficulty caused simply by making those demands,.
I will summarise the information you've offered and pass it up the chain of command. Thanks for your all your hard work on an awesome product. M On Thu, 20 Apr 2023 at 08:01, Andrea Aime <andrea.a...@geosolutionsgroup.com> wrote: > Found out we'll also have to migrate to Wicket 10 in order to run on > JakartaEE: > > https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+10.0 > > Wicket 10 is not released yet, I cannot find a planned release date for it > yet. > > There might be other libraries that we depend on, that have a J2EE > dependency. > Generally speaking, we'll have to wait for all of them to have a release > based on JakartaEE, > and then we'll have to make a "big bang" upgrade of all of them, at the > same time, > hoping the pieces of the puzzle all fit together. > > Cheers > Andrea > > > On Wed, Apr 19, 2023 at 6:05 PM Andrea Aime < > andrea.a...@geosolutionsgroup.com> wrote: > >> The situation is a bit more complicated... GeoServer is based on Spring >> (mostly uses Servlets from the EE world), here is its compatibility matrix: >> >> - Spring 5 (what we use) requires at least Java 8 and uses J2EE >> - Spring 6 requires at least Java 17 and uses JakartaEE >> <https://spring.io/blog/2022/11/16/spring-framework-6-0-goes-ga> >> >> So the upgrade path that we are going to have to take is to upgrade to >> Spring 6 (major API breakages in it) and Java 17 as the minimum, in order >> to get JakartaEE conformance. In order to run on Java 17 without too many >> warnings, we'll also have to switch from JAI to ImageN (and take over the >> maintenance of such a project). >> >> We just requested Java 11 as the minimum, it's going to be a while before >> we can embark on the next jump, which by the looks of it, will be a long >> and complicated process >> >> Cheers >> Andrea >> >> >> On Wed, Apr 19, 2023 at 11:37 AM Rahkonen Jukka < >> jukka.rahko...@maanmittauslaitos.fi> wrote: >> >>> Hi, >>> >>> >>> >>> Sorry if I give misleading information, I am not so much in with >>> programming. >>> >>> >>> >>> That Geoserver 2.23 runs on Java 11/17 even it is using J2EE is possible >>> because Geoserver delivers the javax libraries in geoserver/WEB-INF/lib. >>> The server that is running Geoserver 2.23 must be able to run with Java 11 >>> or 17, and still use J2EE. Therefore Tomcat 9 can be used but Tomcat 10 >>> not. Some people have been able to do that with some fiddling by using a >>> migration tool https://github.com/apache/tomcat-jakartaee-migration, >>> see >>> https://stackoverflow.com/questions/75475861/will-geoserver-run-over-tomcat-10-x. >>> >>> >>> >>> >>> By the Glassfish matrix that you presented it seems to be impossible to >>> run Geoserver 2.23 with Glassfish at the moment. Glassfish 5 requires JDK8 >>> so Geoserver 2.23 does not run. And Glassfish 6 requires Jakarta and >>> Geoserver does not support that, so no go again. The situation is the same >>> than with Tomcat 10. I do not know if the above mentioned migration tool >>> could help with Glassfish 6 as it helped with Tomcat 10. In any case such >>> solution is untested by the Geoserver team. >>> >>> >>> >>> The alien and baffling situation will change in the future, if not >>> before then at latest when Tomcat 9 is reaching the end-of-life, which may >>> take a few years from now. Of course sooner would be better. Using >>> commercial support channels https://geoserver.org/support/ is an >>> effective way for getting more speed if that happens to be an alternative. >>> >>> >>> >>> -Jukka Rahkonen- >>> >>> >>> >>> >>> >>> *Lähettäjä:* Mark Hammond <mark.hamm...@bto.org> >>> *Lähetetty:* keskiviikko 19. huhtikuuta 2023 11.15 >>> *Vastaanottaja:* geoserver-users@lists.sourceforge.net >>> *Aihe:* Re: [Geoserver-users] Geoserver 2.23 requirements >>> >>> >>> >>> All versions of Glassfish ship with the version of J2EE appropriate to >>> the level of JDK it was designed to run on. >>> >>> >>> >>> So glassfish 4 required J2EE7/JDK7 but runs on J2EE8/JDK8 >>> >>> Glassfish 5 requires J2EE8/JDK8 >>> >>> Glassfish 6 requires Jakarta 9.1/JDK11 >>> >>> >>> >>> The notion that you would have a JDK11 or later application paired with >>> a much earlier J2EE version is alien and baffling to me. >>> >>> >>> >>> M >>> >>> >>> >>> On Tue, 18 Apr 2023 at 14:59, Jody Garnett <jody.garn...@gmail.com> >>> wrote: >>> >>> You are the first to run glass fish and tell us about it :) we have all >>> be running with tomcat … >>> >>> >>> >>> What version of J2EE does it support? >>> >>> >>> >>> If it only supports Jakarta we are not migrated to that yet. We tried >>> with tomcat 10 (where it changes javax to Jakarta packages in the fly) but >>> it did not work out so well. >>> >>> >>> >>> Jody >>> >>> >>> >>> On Tue, Apr 18, 2023 at 2:53 AM Ian Turton <ijtur...@gmail.com> wrote: >>> >>> I was looking at this section - >>> https://docs.geoserver.org/latest/en/user/production/java.html#running-on-java-11 >>> >>> >>> >>> > *GlassFish* does not currently [support] Java 11, although the >>> upcoming 5.0.1 release is expected to include support for it. >>> >>> >>> >>> To be honest, I don't know of anyone running on glassfish so I can >>> really comment. May be that page needs updating >>> >>> >>> >>> Ian >>> >>> >>> >>> On Tue, 18 Apr 2023 at 10:21, Mark Hammond <mark.hamm...@bto.org> wrote: >>> >>> Colour me even more confused - this is the release notes for 2.23.0 on >>> geoserver.org >>> >>> >>> >>> >>> >>> Or, if you can't view images: >>> >>> >>> >>> >>> https://geoserver.org/announcements/2023/04/05/geoserver-2-23-0-released.html >>> >>> >>> >>> *"Java 11 Minimum* >>> >>> *With this release GeoServer no longer supports Java 8, and it is time >>> to upgrade to Java 11 at a minimum. Our build system tests GeoServer in >>> with Java 11 and Java 17 which are both long-term-support OpenJDK >>> releases."* >>> >>> >>> >>> My existing servers are 2.15 running on JDK8 and Glassfish 4.x. >>> >>> Quite happy to upgrade to 2.23 running on JDK11 and Glassfish 6.x, or >>> even JDK17 and Glassfish 7.x >>> >>> Can someone advise? Because what I'm being told from the documentation, >>> and what I'm experiencing on the ground don't seem to marry up... >>> >>> >>> >>> Best wishes >>> >>> Mark >>> >>> >>> >>> >>> >>> On Mon, 17 Apr 2023 at 19:58, Jody Garnett <jody.garn...@gmail.com> >>> wrote: >>> >>> Mark may have been testing a newer glassfish based on Jakarta? >>> https://glassfish.org - it looks like version 6 does support Java 11 >>> and Jakarta. >>> >>> >>> >>> We have not migrated from J2EE to jakarta yet; although that is a good >>> task to do. If you are interested in working on that mark it would be a >>> welcome improvement. >>> >>> -- >>> >>> Jody Garnett >>> >>> >>> >>> >>> >>> On Mon, Apr 17, 2023 at 11:45 AM Ian Turton <ijtur...@gmail.com> wrote: >>> >>> According to our manual glassfish doesn't support java 11 while >>> GeoServer doesn't support java 8 any longer. So you may need to work with a >>> n older version, which do have the fixes applied. >>> >>> >>> >>> Ian >>> >>> >>> >>> On Mon, 17 Apr 2023, 18:39 Mark Hammond, <mark.hamm...@bto.org> wrote: >>> >>> Hi folks, >>> >>> >>> >>> >>> >>> I've been asked to upgrade our deployments of Geoserver due to the >>> recently discovered vulnerabilities. I would have been most content to >>> enact the workarounds wildly offered, but people above me in the pecking >>> order insisted. >>> >>> >>> >>> I've set up a vanilla test box with JDK11 and Glassfish 6.2.5 and >>> downloaded the ready-to-eat .WAR file for Geoserver 2.23 >>> >>> >>> >>> However, upon attempting to deploy, this is the message got: >>> >>> >>> >>> remote failure: Error occurred during deployment: Exception while >>> loading the app : java.lang.IllegalStateException: ContainerBase.addChild: >>> start: org.apache.catalina.LifecycleException: >>> java.lang.IllegalArgumentException: java.lang.NoClassDefFoundError: >>> javax/servlet/ServletContextListener. Please see server.log for more >>> details. >>> Command deploy failed. >>> >>> >>> >>> Please could someone offer idiot-proof instructions for a lay-person to >>> get this deployment to work? >>> >>> >>> >>> Kindest regards, >>> >>> Mark >>> >>> _______________________________________________ >>> Geoserver-users mailing list >>> >>> Please make sure you read the following two resources before posting to >>> this list: >>> - Earning your support instead of buying it, but Ian Turton: >>> http://www.ianturton.com/talks/foss4g.html#/ >>> - The GeoServer user list posting guidelines: >>> http://geoserver.org/comm/userlist-guidelines.html >>> >>> If you want to request a feature or an improvement, also see this: >>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >>> >>> >>> Geoserver-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-users >>> >>> _______________________________________________ >>> Geoserver-users mailing list >>> >>> Please make sure you read the following two resources before posting to >>> this list: >>> - Earning your support instead of buying it, but Ian Turton: >>> http://www.ianturton.com/talks/foss4g.html#/ >>> - The GeoServer user list posting guidelines: >>> http://geoserver.org/comm/userlist-guidelines.html >>> >>> If you want to request a feature or an improvement, also see this: >>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >>> >>> >>> Geoserver-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-users >>> >>> _______________________________________________ >>> Geoserver-users mailing list >>> >>> Please make sure you read the following two resources before posting to >>> this list: >>> - Earning your support instead of buying it, but Ian Turton: >>> http://www.ianturton.com/talks/foss4g.html#/ >>> - The GeoServer user list posting guidelines: >>> http://geoserver.org/comm/userlist-guidelines.html >>> >>> If you want to request a feature or an improvement, also see this: >>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >>> >>> >>> Geoserver-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-users >>> >>> >>> >>> -- >>> >>> Ian Turton >>> >>> _______________________________________________ >>> Geoserver-users mailing list >>> >>> Please make sure you read the following two resources before posting to >>> this list: >>> - Earning your support instead of buying it, but Ian Turton: >>> http://www.ianturton.com/talks/foss4g.html#/ >>> - The GeoServer user list posting guidelines: >>> http://geoserver.org/comm/userlist-guidelines.html >>> >>> If you want to request a feature or an improvement, also see this: >>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >>> >>> >>> Geoserver-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-users >>> >>> -- >>> >>> -- >>> >>> Jody Garnett >>> >>> _______________________________________________ >>> Geoserver-users mailing list >>> >>> Please make sure you read the following two resources before posting to >>> this list: >>> - Earning your support instead of buying it, but Ian Turton: >>> http://www.ianturton.com/talks/foss4g.html#/ >>> - The GeoServer user list posting guidelines: >>> http://geoserver.org/comm/userlist-guidelines.html >>> >>> If you want to request a feature or an improvement, also see this: >>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >>> >>> >>> Geoserver-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-users >>> >> >> >> -- >> >> Regards, >> >> Andrea Aime >> >> == >> GeoServer Professional Services from the experts! >> >> Visit http://bit.ly/gs-services-us for more information. >> == >> >> Ing. Andrea Aime >> @geowolf >> Technical Lead >> >> GeoSolutions Group >> phone: +39 0584 962313 >> >> fax: +39 0584 1660272 >> >> mob: +39 339 8844549 >> >> https://www.geosolutionsgroup.com/ >> >> http://twitter.com/geosolutions_it >> >> ------------------------------------------------------- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail >> > > > -- > > Regards, > > Andrea Aime > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
