Beans from a servlet
Hi all, I've got an index servlet the handles the initial request to my web app. This servlet creates a session and a bean; this bean is then stored in the session scope. Once this is done, I use a request dispatcher to forward the request to a JSP page. The problem is that when I try to use the bean I created in the servlet (using jsp:useBean), I get an internal servlet error 500. To try to narrow down the problem I removed the bean instantiation from the servlet and created it in the JSP page, this works as it should. Any ideas ??? Thanks in advance for you help !!! Regards Tarwinder Dhak [EMAIL PROTECTED] Transact Group Development Legal Disclaimer: Internet email communications are not secure and therefore the NetInvest Group does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of the NetInvest Group unless otherwise specifically stated. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Problems with the session time
You can set it in your web.xml for your application. Or you can set it in your web.xml in the tomcat/config directory for all your apps. Tarwinder Dhak -Original Message- From: José Juan Rodríguez [mailto:[EMAIL PROTECTED]] Sent: Monday, September 10, 2001 10:00 AM To: [EMAIL PROTECTED] Subject: Problems with the session time Hi!! I want to modify the time of the session expiration in my Tomcat 3.2.1, but I can't find any information about it. I think that you can modify this parameter. Where can I get any information?? Can you help me?? Thanks.
Tomcat 321 won't parse other than .jsp files
Hi, I'm writing a web application that uses some javascript (in an external file menu.js) that displays some dynamic menus. Each of these menu options then goes to a specific URL. What I want to do is insert some JSP elements into the menu.js file so that when the client requests the file, all URLs go through the request.encodeURL() method to append any session data to the URLs. The problem is that Tomcat only seems to want to compile files with a .jsp extension. I've got Tomcat running through APJ13 with apache (mod_jk.so), and have used the jkmount directive in the mod_jk config file to forward all *.js requests to Tomcat, but tomcat won't compile it. It just sends me the raw text instead. Basically, what I would like to know is how to get tomcat to compile files that have JSP elements in them, but do not have the .jsp extension. Thanks in advance for your help. Regards Tarwinder Dhak [EMAIL PROTECTED] Transact Group Development Legal Disclaimer: Internet email communications are not secure and therefore the NetInvest Group does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of the NetInvest Group unless otherwise specifically stated.
RE: Tomcat 321 won't parse other than .jsp files
That would be the simple answer, but I would like to keep the .js extension keep to the standard for javascript files. There must be a way for tomcat to compile files that don't end in a .jsp extension. Thanks. Tarwinder Dhak -Original Message- From: Burkard Endres [mailto:[EMAIL PROTECTED]] Sent: Monday, September 03, 2001 10:55 AM To: [EMAIL PROTECTED] Subject: AW: Tomcat 321 won't parse other than .jsp files simply rename your .js file to .jsp? -Ursprüngliche Nachricht- Von: Tarwinder Dhak [mailto:[EMAIL PROTECTED]] Bereitgestellt: Montag, 3. September 2001 11:33 Bereitgestellt in: tomcat-user Unterhaltung: Tomcat 321 won't parse other than .jsp files Betreff: Tomcat 321 won't parse other than .jsp files Hi, I'm writing a web application that uses some javascript (in an external file menu.js) that displays some dynamic menus. Each of these menu options then goes to a specific URL. What I want to do is insert some JSP elements into the menu.js file so that when the client requests the file, all URLs go through the request.encodeURL() method to append any session data to the URLs. The problem is that Tomcat only seems to want to compile files with a .jsp extension. I've got Tomcat running through APJ13 with apache (mod_jk.so), and have used the jkmount directive in the mod_jk config file to forward all *.js requests to Tomcat, but tomcat won't compile it. It just sends me the raw text instead. Basically, what I would like to know is how to get tomcat to compile files that have JSP elements in them, but do not have the .jsp extension. Thanks in advance for your help. Regards Tarwinder Dhak [EMAIL PROTECTED] Transact Group Development Legal Disclaimer: Internet email communications are not secure and therefore the NetInvest Group does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of the NetInvest Group unless otherwise specifically stated. winmail.dat
Apache and Tomcat integration
Hi all, I'm trying to get apache and Tomcat 3.2.1 to talk to each other using mod_jk.so (downloaded from the internet, not compiled) with the ajp13 protocol (on Mandrake 7.2). I've got Tomcat running as a stand alone web server executing servlets and jsp files. I've also got Apache loading the mod_jk.so module while using mod_jk.conf-auto file generated by tomcat. The problem I've got is that apache doesn't seem to be relaying any servlet or jsp requests to tomcat on port 8009. Instead it just tries to serve the pages as normal (I've been using the examples supplied by tomcat). I think tomcat is definitely listening on port 8009 because if I telnet or http request that port it does actually connect (using the netstat -l command). This is starting to drive me around the twist!! Any help would be gratefully appreciated. Regards Tarwinder Dhak [EMAIL PROTECTED] Transact Group Development Legal Disclaimer: Internet email communications are not secure and therefore the NetInvest Group does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of the NetInvest Group unless otherwise specifically stated.
