RE: JASPER libraries incompatibilities
Thank you very much Chris and Chuk. Regards, -Hitesh -Original Message- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 7:58 PM To: Tomcat Users List Subject: Re: JASPER libraries incompatibilities -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hitesh, Hitesh Raghav wrote: | Is there any URLs about these backward incompatibilities (i.e. | Servlet/JSP specs backward incompatibilities)? As Chuck suggests, the servlet specification has changed between versions, and the best reference for that is the specification itself. There are even sections titled changes since spec vX.Y that you can read to get an overview of the changes, instead of reading the entire document start-to-finish. My concern was less with the servlet specification (because your old JSPs and tag libraries probably implement the old specification, but so does the Jasper version you are trying to jam into the newer TC version) and more with incompatibility between the old Jasper and the new TC. Since Tomcat is bundled with TC and all the APIs are proprietary (and not defined by some specification), there's no guarantee that they will be compatible if you mix-and-match versions. Furthermore, there's no need for documentation outlining all the incompatibilities between, say, TC 6.x and Jasper that came from TC 4.x because there is simply no reason to put the two together. Stick with a matched TC + Jasper pair. Your life will be much simpler. Until then, stick with TC 4.1. The best reason to stick with your server version is that it works! I would definitely take some time to assign some folks to port your application to TC 5.5 or 6.0. It doesn't look like like support for 4.1 will be dropped anytime soon, but it /is/ really /really/ old. The newer versions are generally better and faster, anyway. Good luck with your upgrade, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAke9ilsACgkQ9CaO5/Lv0PCDEQCgtu5NT4ag7opi0M+BByhJ5vLA MRsAn2ZWfkle6EfAJ79IQpCF3PEi0Dxx =MH0G -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JASPER libraries incompatibilities
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hitesh, Hitesh Raghav wrote: | Is there any URLs about these backward incompatibilities (i.e. | Servlet/JSP specs backward incompatibilities)? As Chuck suggests, the servlet specification has changed between versions, and the best reference for that is the specification itself. There are even sections titled changes since spec vX.Y that you can read to get an overview of the changes, instead of reading the entire document start-to-finish. My concern was less with the servlet specification (because your old JSPs and tag libraries probably implement the old specification, but so does the Jasper version you are trying to jam into the newer TC version) and more with incompatibility between the old Jasper and the new TC. Since Tomcat is bundled with TC and all the APIs are proprietary (and not defined by some specification), there's no guarantee that they will be compatible if you mix-and-match versions. Furthermore, there's no need for documentation outlining all the incompatibilities between, say, TC 6.x and Jasper that came from TC 4.x because there is simply no reason to put the two together. Stick with a matched TC + Jasper pair. Your life will be much simpler. Until then, stick with TC 4.1. The best reason to stick with your server version is that it works! I would definitely take some time to assign some folks to port your application to TC 5.5 or 6.0. It doesn't look like like support for 4.1 will be dropped anytime soon, but it /is/ really /really/ old. The newer versions are generally better and faster, anyway. Good luck with your upgrade, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAke9ilsACgkQ9CaO5/Lv0PCDEQCgtu5NT4ag7opi0M+BByhJ5vLA MRsAn2ZWfkle6EfAJ79IQpCF3PEi0Dxx =MH0G -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JASPER libraries incompatibilities
From: Hitesh Raghav [mailto:[EMAIL PROTECTED] Subject: RE: JASPER libraries incompatibilities Is there any URLs about these backward incompatibilities (i.e. Servlet/JSP specs backward incompatibilities)? The specs themselves usually document incompatibilities. Servlet spec: http://jcp.org/aboutJava/communityprocess/mrel/jsr154/index2.html JSP spec: http://jcp.org/aboutJava/communityprocess/final/jsr245/index.html - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JASPER libraries incompatibilities
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hitesh, Hitesh Raghav wrote: | I've web-app developed to run with Tomcat 4.2. It used to work perfectly | fine with Tomcat 4.2. 4.2? I don't think there was ever a Tomcat 4.2. Do you mean 4.1? | When same web-app is deployed on Tomcat v5.5.x or v6.0.y, it fails by | throwing NullPointerException. Tomcat 4.1 had a lot of ... let's say wiggle-room when it comes to either violating the Servlet Specification. Later versions are much more strict when it comes to following the rules. You probably want to audit your tag library to see if it is compatible (if it is a 3rd-party library) or review your own code (if this was an in-house tag library) to see if you have done something potentially dangerous. | It works perfectly fine, when we replace JASPER libraries from Tomcat | v4.2 (from apache-tomcat\common\lib folder). Don't do that. It will cause you nothing but trouble. Jasper wasn't designed (I don't think) to be moved between versions of Tomcat. You are likely to have more problems down the road if you attempt to run the Jasper from TC 4.1 on TC 5.5 or 6.0. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAke6+JQACgkQ9CaO5/Lv0PDUAwCbBMuq+y23gW9Len+1LW8YhAtE o+IAn2R+gLdr5T+PgpwkHFTn+HUmDK7c =k0hH -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JASPER libraries incompatibilities
Hi, Is there any backward incompatibility in JASPER libraries in Tomcat (v4.x.y, 5.x.y 6.x.y)? If 'YES', could you please share appropriate URL about it. Thanks, -Hitesh
RE: JASPER libraries incompatibilities
Hi, I've web-app developed to run with Tomcat 4.2. It used to work perfectly fine with Tomcat 4.2. When same web-app is deployed on Tomcat v5.5.x or v6.0.y, it fails by throwing NullPointerException. It works perfectly fine, when we replace JASPER libraries from Tomcat v4.2 (from apache-tomcat\common\lib folder). === type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.NullPointerException org.apache.jasper.runtime.TagHandlerPool.reuse(TagHandlerPool.java:132) vrts.mgmt.sample.jsp.layouts.mainLayout_jsp._jspService(mainLayout_jsp.j ava:87) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.jav a:1069) org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProc essor.java:274) org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(Til esRequestProcessor.java:254) org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(Tiles RequestProcessor.java:309) org.apache.struts.action.RequestProcessor.process(RequestProcessor.java: 279) org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) javax.servlet.http.HttpServlet.service(HttpServlet.java:690) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java :686) org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:6 56) vrts.mgmt.sample.jsp.index_jsp._jspService(index_jsp.java:42) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) com.veritas.qe.authentication.AuthenticationFilter.doFilter(Authenticati onFilter.java:210) vrts.tomcat.admin.SecurePortRedirector.doFilter(SecurePortRedirector.jav a:217) vrts.tomcat.admin.SecurePortRedirector.doFilter(SecurePortRedirector.jav a:217) vrts.tomcat.admin.HTTPMethodBlocker.doFilter(HTTPMethodBlocker.java:160) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.26 logs. === Please let me know in case any other details are needed. Thanks, -Hitesh -Original Message- From: Hitesh Raghav [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 7:21 PM To: users@tomcat.apache.org Subject: JASPER libraries incompatibilities Hi, Is there any backward incompatibility in JASPER libraries in Tomcat (v4.x.y, 5.x.y 6.x.y)? If 'YES', could you please share appropriate URL about it. Thanks, -Hitesh - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]