Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2F7139A64 for ; Mon, 8 Dec 2014 21:18:54 +0000 (UTC) Received: (qmail 62886 invoked by uid 500); 8 Dec 2014 21:18:51 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 62816 invoked by uid 500); 8 Dec 2014 21:18:50 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 62805 invoked by uid 99); 8 Dec 2014 21:18:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 21:18:50 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dckerber@verizon.net designates 206.46.173.17 as permitted sender) Received: from [206.46.173.17] (HELO vms173017pub.verizon.net) (206.46.173.17) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 21:18:23 +0000 Received: from [172.17.47.42] ([65.199.184.146]) by vms173017.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NGA002PX8HYDL81@vms173017.mailsrvcs.net> for users@tomcat.apache.org; Mon, 08 Dec 2014 15:17:59 -0600 (CST) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=AKpDk7pY c=1 sm=1 tr=0 a=ghRDmrgUihQ+t5fp33utJQ==:117 a=DgqbUt__V68A:10 a=N659UExz7-8A:10 a=o1OHuDzbAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=A92cGCtB03wA:10 a=mV9VRH-2AAAA:8 a=uRvxxCdHw41iYtD48EkA:9 a=pILNOxqGKmIA:10 Message-id: <54861586.9050304@verizon.net> Date: Mon, 08 Dec 2014 16:17:58 -0500 From: David kerber User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-version: 1.0 To: Tomcat Users List Subject: Re: My problem: I cannot successfully get or set a session attribute from a JSP file. References: <548372CE.5050501@centurylink.net> <54860EF5.3020205@centurylink.net> <54860FF5.8020906@verizon.net> <54861264.3020309@centurylink.net> In-reply-to: <54861264.3020309@centurylink.net> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 12/8/2014 4:04 PM, Jim Anderson wrote: > > David, > > I have to question your response. In the past, I have made errors in the > serverside JSP file and the console has identified errors for me to the > point were I have become dependent this feedback. > > I understand the separation of the client side vs the server side, > (and I must confess that sometimes in the middle of debugging, I forget > that it is there), > but my assumption has been that when the JSP code is compiled by the > tomcat environment, it gets sent errors back through the Firefox API > that allows the errors to be displayed in the console. > > I don't know the Firefox API, but I can believe it has hooks in the > brower code that allows an application such as Tomcat to post > information into the console. If fact, I would expect the browser > console to have that kind of hook. Hmm, I've never seen anything like that. The only time I see server errors in the browser is when the server sends them as part of its HTTP response. If the error output is swallowed on the server end and never makes it to the browser, the browser does not display anything. I could certainly be missing something here, though... > > Jim > > > On 12/08/2014 03:54 PM, David kerber wrote: >> On 12/8/2014 3:49 PM, Jim Anderson wrote: >>> >>> Resolved! >>> >>> I apologize to everyone for taking a while to respond. It was a busy >>> weekend and I was not at >>> the computer. Thank you all for the responses. >>> >>> I read your emails about a half hour ago and ran my application to get >>> fresh log files and to >>> check them all. Sure enough in the log file, 'localhost.2014-12-08.log', >>> I found an error message >>> about the java code in my 's.jsp' file. I fixed the error and all is >>> well now. I thought that I looked >>> at this file the other day before sending in my question to the mailing >>> list and I did not see the error messages then. I am going to guess that >>> I am in error and the I did not actually look at the file, although I >>> know I looked at most of the log files in the tomcat/logs directory. >>> >>> I was curious why the error did not show up in my firefox browser >>> console, so I removed my fix and re-ran my application with the error in >>> it. Sure enough, the error did not show up on the console. >> >> The reason it doesn't show up in your browser is that it's happening >> on the server, not the client. So the browser never knows that there >> is an error. >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org >> For additional commands, e-mail: users-help@tomcat.apache.org >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org