Looks like it was the 'username'. The username is being initialised in the taglib handler implementation but the behaviour differs between JRun and Tomcat.
In the layout template jsp for the admin console, we use a taglib that checks if a user is logged in or not. The following snippet works on JRun. <users:login loginpage="login.jsp" /> Now this can also accept other attributes (if the expected request param names were different). I updated it for Tomcat like this: <users:login loginpage="login.jsp" logout="logout" username="username" password="password" /> While 'username', 'password' and 'logout' are initialised to the default values in the taglib handler implementation, the setter method for these attributes still gets called when they are not specified in the JSP, and NULL values are assumed for them. That's the only explanation I can think of :-) What is the correct behaviour? Any ideas. Cheers, Rahul On 4/11/07, Robert Harper <[EMAIL PROTECTED]> wrote:
Try username. I'm surprised the compiler doesn't complain that username is being used without being initialized. If it didn't, the compiler probably set username to be null. You need to pass a valid string to the method getParameter(); Try something more like: String username = null; Username = pageContext().getRequest().getParameter( "username" ); Robert S. Harper Senior Engineer Information Access Technology, Inc. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
