Hello,
I'm hoping that someone knows more about Request-Time Attribute Expressions,
a feature of JSP 1.1 that allows an expression inside an attribute value
without the XML-unfriendly %=...% syntax. As described int the JSP 1.1
spec below, I understand that you can use something like the
I wrote a simple JSP page with a form in it. This form had a couple of
text elements and a submit button and I want the submit from
this form to
be
handled by a servlet. However, when I set the method of the form to
"POST",
my servlet does not get the parameters (neither the text
One issue that has caused me a lot of trouble, though, is
that I often want to be
able to have buttons on the same form send the user to
different pages. Of course, a
form can have only one target URL, so I am stuck there.
Instead of using input
type="submit" tags for my buttons, I could
From: Mike Engelhart [mailto:[EMAIL PROTECTED]]
How do you figure that using sessions doesn't allow a site to
scale up? I
mean, I can easily see needing SMP, 1GB of RAM and 5 machines for load
balancing but where are you getting that information from? As
for sessions
timing out, that's a
From: Mike Engelhart [mailto:[EMAIL PROTECTED]]
I'm pretty sure any memory overhead per client session will
dramatically
effect scalability. That's why EJB SessionBeans have the ability to
"passivate themselves" to free up memory during heavy load
conditions.
That's what I mean
Perfect! Thanks Craig and Mike for your replies on this.
mark
-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 26, 1999 9:00 AM
To: [EMAIL PROTECTED]
Subject: Re: Which Architecture..?
Mike Engelhart wrote:
Mark Hayes wrote
One big advantage of JSP over ASP for me is that JSP can be represented as
well-formed XML, so I can use XML generation tools (such as XSL) to create
the JSP page.
--
mark
-Original Message-
From: Steve Nguyen [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 27, 1999 10:11 AM
To:
Maybe the trick is to use JSP in moderation. My opinion is that if you put
lots of Java code into your JSP file, you'll have maintenance and structural
problems. It is better to only use small snippets of embedded Java. It is
even better to use beans or directives, and in some cases better yet
To clear up any confusion I may have created by sending this message:
This only applies if you are using NAS, not NES.
I misspelled NTV as NTF - it is NTV.
mark
From: Mark Hayes [mailto:[EMAIL PROTECTED]]
If you're using NAS, make sure the CacheTimeOut is set to
zero in your NTF
file
Ty van den Akker wrote:
The servlet I post to becooomes the new URL in my browser. This is
logical, but it also means that the URL for my MainMenu is
/servlet/Login because the Login servlet handles the login.
Aside from
URL redirection which provides a slow solution, or having
my
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
[snip]
Servlets are great for logic (model manipulations as well as
flow-of-control
management), and can be coerced into creating presentation
(although writing
out.println() statements with embedded HTML is really
tiresome). JSPs are
If you're using NAS, make sure the CacheTimeOut is set to zero in your NTF
file:
YourServlet {
"CacheTimeOut" Int "0",
Otherwise, the last results of the servlet will be cached.
mark
-Original Message-
From: Abhijit Tannu [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 24, 1999
From: Jia-yu Sun [mailto:[EMAIL PROTECTED]]
When I start Apache web server, I got "class not
found: org.apache.jserv.JServ" in error.log. The
setting in jserv.properties looks correct:
wrapper.bin=c:\program files\javasoft\jre\1.1\bin\jre.exe
wrapper.classpath=c:\program
13 matches
Mail list logo
