We enable URL rewriting by response.encodeUrl(url), and it works fine for
https URL's. But there is no longer any session tracking when we shift to
https. I guess this because the Java URL class treats a https URL as
malformed URL.
On the other hand, I've heard that wise people use the SSL
To: [EMAIL PROTECTED]
[EMAIL PROTECTED] cc: (bcc: Raymond Pau/adc)
Sent by: Subject: JSP Session
Hi,
Does it must use JavaBeans in order to use session among several jsp
files? Is there any simpler solution?
I want to maintain a persistent database connection in all jsp files.
For example:
Create a database object in first jsp file and retrieve it in other jsp
files
Regards,
Mauricio
If the connection (or other object) is to be shared by the entire
application, use the application scope. As always, you must be aware of
threading issues because any JSP or servlet can access these objects at any
time.
Eric
At 08:11 AM 5/24/2002, you wrote:
Hi,
Does it must use JavaBeans
Putting a database connection into each session is a very bad idea.
If you get 10 users with open sessions, this means you'll have 10 open, idle
database connections most of the time. If you have 20 sessions...I'll put
it this way -- I have an application that has been running for months with
Does anyone knows how to get a reference to the jsp bean (ie jsp:useBean
scope='session') inside the Filter code?
Kar Yeow
System Architect
APIR Systems Pty Ltd
Ph: 61 2 6260 6035 Fax: 61 2 6260 6037
Email: [EMAIL PROTECTED]
--
To unsubscribe: mailto:[EMAIL PROTECTED]
For additional
On Mon, 11 Feb 2002, Kar YEOW wrote:
Date: Mon, 11 Feb 2002 08:06:08 +1100
From: Kar YEOW [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Subject: How to get hold of the JSP session scope bean from within a
Filter?
Does anyone
Hi, when I use
session.invalidate() and on the same page located
jsp:useBean id="xpeo" scope="session", after invalidation,I've got
the error:
getAttribute() IllegalStateException- session
invalidated.That't true but it's OK and code in JSP must assume that xpeo=null,
I mean:
//generated
Hi,
I have a question about the failover capabilities of Tomcat.
We want to setup an environment running multiple Tomcat-Servers.
I've heart that there's a way in Tomcat to ensure that the JSP-sessions keep
alive in case the a tomcat server falls down.
Does anyone know how to setup such an
Hi,
I am using TOMCAT 3.2 (I guiess 3.2 means 3.2.1).
When a servlet forwards a request to a JSP
using
ServletContext sc = getServletContext();
RequestDispatcher rd = sc.getRequestDispatcher("/common/index.jsp");
rd.forward(req,resp);
always this exception arrives:
I've tried using request scope instaed, but the
request.getAttribute("test") produces a null bean object - why?
bean objects are not in the HttpServletRequest. They are simply
shorthand for instantiation of a Object... i.e. instead of:
SessionDoohicky doohicky = new SessionDoohicky(param1);
I write a jsp program makes use of a session bean to keep session info and
test it with IE5.5. The result is it's able to keep session info but it
behaves different from running in other web server, e.g. weblogic, iPlanet.
The difference is two openned browsers are treated as two different
12 matches
Mail list logo
