Re: Updating a working installation
On 09.05.2018 17:09, James H. H. Lampert wrote: Question: Is there an easy way to bump a working Tomcat installation from one release to another, without benefit of Linux "apt-get" or "yum," or WinDoze "cab" (this is an OS/400 installation), without having to rebuild the whole configuration (webapps, keystore, server.xml, web.xml, &c.) from scratch? Depending on the changes in your configuration and changes introduced between your "come from" version versus the "go to" version. IMHO the easiest way to figure out is to download your source and target version of vanilla tomcat and compare them with a diff tool. Pay special attention to the conf folder, and if any of the changes there are actual changes or in comments/documentation. That will show you if * it's enough to replace files * you should delete files * the default configuration of tomcat has changed and you'll need to validate if you need to bring those changes forward. Of course, you'll also need to compare your current custom installation with the source version, to figure out which files you use out-of-the-box, and which ones you have changed. It's hard to be more specific with this generic question. Olaf - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Updating a working installation
Question: Is there an easy way to bump a working Tomcat installation from one release to another, without benefit of Linux "apt-get" or "yum," or WinDoze "cab" (this is an OS/400 installation), without having to rebuild the whole configuration (webapps, keystore, server.xml, web.xml, &c.) from scratch? -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Which maven provided dependencies to target Tomcat ?
Hi Luis, I'm sorry to say that if you use javaee-web-api on Tomcat, you will pull, among others, javax.transaction:javax.transaction-api:1.2 which contains, for example, javax.transaction.HeuristicCommitException and if you try to put resp.getWriter.println(HeuristicCommitException.class.getName()); your IDE won't complain but the servlet will throw a ClassNotFound exception at runtime. This assuming javax.transaction.HeuristicCommitException is not brought by some other dependency. You will get the same result with many other dependencies of javaee-web-api. I actually performed the same experience with all 17 dependencies of javaee-web-api, selecting one arbitrary class and checking if it was found when deployed on tomcat, and I found that only the following should be included in a project which targets tomcat 8.5 / Java EE 7 javax.el javax.el-api 3.0.0 provided javax.servlet javax.servlet-api 3.1.0 provided javax.servlet.jsp javax.servlet.jsp-api 2.3.1 provided javax.websocket javax.websocket-api 1.0 provided javax.annotation javax.annotation-api 1.2 provided Xavier 2018-05-09 18:17 GMT+02:00 Luis Rodríguez Fernández : > Hello Xavier, > > Perhaps you can have a look here: > https://wiki.apache.org/tomcat/Specifications. > > Me, I have: > > > javax > javaee-web-api > 7.0 > provided > > > Hope it helps, > > Luis > > > > > > 2018-05-09 16:35 GMT+02:00 Xavier Dupont : > > > Hi guys. > > > > If I want to target the Java EE full profile, I use go here > > https://mvnrepository.com/artifact/javax/javaee-api/8.0 and get the > > following XML snippet. > > > > > > javax > > javaee-api > > 8.0 > > provided > > > > > > If I want to target the Java EE web profile, I use this url instead > > https://mvnrepository.com/artifact/javax/javaee-web-api/8.0 > > > > And if I only need a subset of JSRs included in the javaee web profile, > > they are all nicely included in the list of compile dependencies, this is > > all very nice. > > > > Since tomcat only supports a subset of the web profile, which > dependencies > > should be added in maven ? > > > > Here's the full list for the Java EE 7 Web profile. > > > > javax.annotation:javax.annotation-api:1.2 > > javax.ejb:javax.ejb-api:3.2 > > javax.el:javax.el-api:3.0.0 > > javax.enterprise:cdi-api:1.1 > > javax.faces:javax.faces-api:2.2 > > javax.inject:javax.inject:1 > > javax.interceptor:javax.interceptor-api:1.2 > > javax.json:javax.json-api:1.0 > > javax.servlet:javax.servlet-api:3.1.0 > > javax.servlet.jsp:javax.servlet.jsp-api:2.3.1 > > javax.servlet.jsp.jstl:javax.servlet.jsp.jstl-api:1.2.1 > > javax.transaction:javax.transaction-api:1.2 > > javax.validation:validation-api:1.1.0.Final > > javax.websocket:javax.websocket-api:1.0 > > javax.ws.rs:javax.ws.rs-api:2.0 > > org.eclipse.persistence:javax.persistence:2.1.0 > > org.glassfish:javax.faces:2.2.0 > > > > I ask because I couldn't find the answer on the web, and it seems to me > > that many sources are actually quite wrong and how it should be done. > > I believe this should appear in a section of the tomcat documentation, at > > least for versions 6, 7, and 8 of Java EE, which Tomcat seems to track. > > > > Xavier. > > > > > > -- > > "Ever tried. Ever failed. No matter. Try Again. Fail again. Fail better." > > - Samuel Beckett >
Re: Which maven provided dependencies to target Tomcat ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Xavier, On 5/9/18 10:35 AM, Xavier Dupont wrote: > Hi guys. > > If I want to target the Java EE full profile, I use go here > https://mvnrepository.com/artifact/javax/javaee-api/8.0 and get > the following XML snippet. > > javax > javaee-api 8.0 > provided > > If I want to target the Java EE web profile, I use this url > instead > https://mvnrepository.com/artifact/javax/javaee-web-api/8.0 > > And if I only need a subset of JSRs included in the javaee web > profile, they are all nicely included in the list of compile > dependencies, this is all very nice. > > Since tomcat only supports a subset of the web profile, which > dependencies should be added in maven ? You may want to use Apache TomEE instead of Tomcat. TomEE uses Tomcat at the code, but already provides the remaining "web profile" dependencies. - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlrzIU0ACgkQHPApP6U8 pFg/cBAAsE6GKtB1TBerw8FnF6dCDKjOyGm6pKiMpcLNH/Dun9e9l/TDCkHCsS2j ep2tG+DrWDMrJ+oIX8A69WyZqRcRLNgNYj5/SJIZWyJtXBCeZ6IIZOl7c/3QfXgO 3MxTXiOmdae7g6oPlc6Yja8uqCIaxL5ZjvCOXHaa2EN3Qe17ypkJqDX5YDZ5UDcO KuYJotWs1DpC+dlVTqD/MdJ1wxU0yu9YU7kiRxD8FsHj1DBsmnqM6V69mturztmz FDBI+imGXpAWFWaH7KD8HgWC5qBQq8ERNbzlq/J9L8H/xtPNfJnMkBlPG4OstboK 4bbcuILgmbi9N9UiCJcYygfeDrTnqlp34j/UfqSuGn6YYCgKA17w2d0q1bJCrjLy wYTpKZ89wFMBkR9fqe2BmhwyVs1Dr5RplRzcbT3jSdL/cjZt73kXSe2jFqBjvp+H 1uKF1D8OeQF0XKGaEEnV57L5iGeOjy708jc12a+ZR1peDcmmQ7UUDLLCZzj6Acdr AS5rY72rpO3brvFX9FQBvW7PgftDH29WUiVMA/zO4kuZd5963tV4S701SOV9wQ5W bgugC6x0lq0pENt7mILj1+19+1adH4gbZzNWXTvMk7H47AgfcEiYWe6D3P3K8R3o iUMLZ1kNwEnXwX6Mpu8WT3EwwpN8rURlRvYIYlKXrCeSR4D3MWo= =X9i6 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Which maven provided dependencies to target Tomcat ?
Hello Xavier, Perhaps you can have a look here: https://wiki.apache.org/tomcat/Specifications. Me, I have: javax javaee-web-api 7.0 provided Hope it helps, Luis 2018-05-09 16:35 GMT+02:00 Xavier Dupont : > Hi guys. > > If I want to target the Java EE full profile, I use go here > https://mvnrepository.com/artifact/javax/javaee-api/8.0 and get the > following XML snippet. > > > javax > javaee-api > 8.0 > provided > > > If I want to target the Java EE web profile, I use this url instead > https://mvnrepository.com/artifact/javax/javaee-web-api/8.0 > > And if I only need a subset of JSRs included in the javaee web profile, > they are all nicely included in the list of compile dependencies, this is > all very nice. > > Since tomcat only supports a subset of the web profile, which dependencies > should be added in maven ? > > Here's the full list for the Java EE 7 Web profile. > > javax.annotation:javax.annotation-api:1.2 > javax.ejb:javax.ejb-api:3.2 > javax.el:javax.el-api:3.0.0 > javax.enterprise:cdi-api:1.1 > javax.faces:javax.faces-api:2.2 > javax.inject:javax.inject:1 > javax.interceptor:javax.interceptor-api:1.2 > javax.json:javax.json-api:1.0 > javax.servlet:javax.servlet-api:3.1.0 > javax.servlet.jsp:javax.servlet.jsp-api:2.3.1 > javax.servlet.jsp.jstl:javax.servlet.jsp.jstl-api:1.2.1 > javax.transaction:javax.transaction-api:1.2 > javax.validation:validation-api:1.1.0.Final > javax.websocket:javax.websocket-api:1.0 > javax.ws.rs:javax.ws.rs-api:2.0 > org.eclipse.persistence:javax.persistence:2.1.0 > org.glassfish:javax.faces:2.2.0 > > I ask because I couldn't find the answer on the web, and it seems to me > that many sources are actually quite wrong and how it should be done. > I believe this should appear in a section of the tomcat documentation, at > least for versions 6, 7, and 8 of Java EE, which Tomcat seems to track. > > Xavier. > -- "Ever tried. Ever failed. No matter. Try Again. Fail again. Fail better." - Samuel Beckett
Which maven provided dependencies to target Tomcat ?
Hi guys. If I want to target the Java EE full profile, I use go here https://mvnrepository.com/artifact/javax/javaee-api/8.0 and get the following XML snippet. javax javaee-api 8.0 provided If I want to target the Java EE web profile, I use this url instead https://mvnrepository.com/artifact/javax/javaee-web-api/8.0 And if I only need a subset of JSRs included in the javaee web profile, they are all nicely included in the list of compile dependencies, this is all very nice. Since tomcat only supports a subset of the web profile, which dependencies should be added in maven ? Here's the full list for the Java EE 7 Web profile. javax.annotation:javax.annotation-api:1.2 javax.ejb:javax.ejb-api:3.2 javax.el:javax.el-api:3.0.0 javax.enterprise:cdi-api:1.1 javax.faces:javax.faces-api:2.2 javax.inject:javax.inject:1 javax.interceptor:javax.interceptor-api:1.2 javax.json:javax.json-api:1.0 javax.servlet:javax.servlet-api:3.1.0 javax.servlet.jsp:javax.servlet.jsp-api:2.3.1 javax.servlet.jsp.jstl:javax.servlet.jsp.jstl-api:1.2.1 javax.transaction:javax.transaction-api:1.2 javax.validation:validation-api:1.1.0.Final javax.websocket:javax.websocket-api:1.0 javax.ws.rs:javax.ws.rs-api:2.0 org.eclipse.persistence:javax.persistence:2.1.0 org.glassfish:javax.faces:2.2.0 I ask because I couldn't find the answer on the web, and it seems to me that many sources are actually quite wrong and how it should be done. I believe this should appear in a section of the tomcat documentation, at least for versions 6, 7, and 8 of Java EE, which Tomcat seems to track. Xavier.
[ANN] Apache Tomcat 8.0.52 released
The Apache Tomcat team announces the immediate availability of Apache Tomcat 8.0.52. Please note that Apache Tomcat 8.x users should normally be using 8.5.x releases in preference to 8.0.x releases. The Apache Tomcat team announced that support for Apache Tomcat 8.0.x will end on 30 June 2018. Apache Tomcat 8.0 is an open source software implementation of the Java Servlet, JavaServer Pages, Java Unified Expression Language and Java WebSocket technologies. Apache Tomcat 8.0.52 includes fixes for issues identified in 8.0.51 as well as other enhancements and changes. The notable changes since 8.0.51 include: - Implement configuration options to work-around specification non-compliant user agents (including all the major browsers) that do not correctly %nn encode URI paths and query strings as required by RFC 7230 and RFC 3986 - Enable the CrawlerSessionManagerValve to correctly handle bots that crawl multiple hosts and/or web applications when the Valve is configured on a Host or an Engine. Please refer to the change log for the complete list of changes: http://tomcat.apache.org/tomcat-8.0-doc/changelog.html Apache Tomcat website: http://tomcat.apache.org Downloads: http://tomcat.apache.org/download-80.cgi Migration guides from Apache Tomcat 5.5.x, 6.0.x and 7.0.x: http://tomcat.apache.org/migration.html Enjoy The Apache Tomcat team
