Re: Reserved parameter names?

2001-02-02 Thread William Brogden



Chris Janicki wrote:
> 
> I've discovered (after some frustration) than certain variable names used
> in an HTML form won't be passed to my bean via the "jsp:setProperty" tag.
>  For example, using "page" as a name doesn't work.  I *can* explicitly
> set it via:
> 
> myBean.setPage(request.getProperty("page"));
> 
> But this name won't get set automatically, while other names do, all in
> the same form.
> 
> Are there "reserved" names that I need to avoid when making forms to be
> handled by Tomcat?  Is there a list of them?
> 
> Thanks,
> Chris
> 

That is because of the "Implicit Objects" in the JSP standard:
request, response, pageContext,session, application, out, config, page
and exception

There is a really useful 2 page summary you can download from
java.sun.com
named something like "Javaserver Pages Technology Syntax" that includes
this list.

-- 
WBB - [EMAIL PROTECTED]
Java Cert mock exams http://www.lanw.com/java/javacert/
Author of Java Developer's Guide to Servlets and JSP 
ISBN 0-7821-2809-2

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Reserved parameter names?

2001-02-02 Thread Chris Janicki

I've discovered (after some frustration) than certain variable names used 
in an HTML form won't be passed to my bean via the "jsp:setProperty" tag. 
 For example, using "page" as a name doesn't work.  I *can* explicitly 
set it via:

myBean.setPage(request.getProperty("page"));

But this name won't get set automatically, while other names do, all in 
the same form.

Are there "reserved" names that I need to avoid when making forms to be 
handled by Tomcat?  Is there a list of them?

Thanks,
Chris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]