Hi, Sorry, I saw your question the first time and when I went to answer it I couldn't find your email anymore.
This is a known issue. It's a long story. The short answer is, use application.log() instead of log(). The long answer is, prior to JRun 3.1 we were making generated JSP Servlets extend the wrong class, so we made the Servlet API log() method available when we shouldn't have. JRun 3.1 fixes a bug in 3.0 by making its generated JSP superclass extend HttpJSPPage instead of GenericServlet. According to the JSP spec 3.2.4 this is how it should be done. The log method is part of GenericServlet and that's why it worked in 3.0. In 3.1 you have to use the log function of the application object. Hope this helps, Scott Stirling > -----Original Message----- > From: Gayathri Shaikh [mailto:[EMAIL PROTECTED]] > > Hi > > I just switched over to JRun 3.1 from JRun 3.0 sp2. I have > web applications > that contain JSPs that call the log method available as part > of HttpServlet. > These used to work with JRun 3.0 sp2 but dont work anymore > with JRun 3.1 as > somehow in JRun 3.1, JSPs when compiled to Java classes, I > can see that they > are converted into servlets that extend from allaire's > allaire.jrun.jsp.HttpJSPServlet which probably doesnt support the log > method. Searching through the properties files, I can see that > global.properties has some timing properties which refer to > this class. Can > anyone tell me how to change the properties so that my web apps work. > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
