-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rahul,
Rahul Thakur wrote: > Looks like it was the 'username'. The username is being initialised in > the taglib handler implementation but the behaviour differs between > JRun and Tomcat. That should not be the case. The servlet spec is quite clear about the order of execution of the various init/begin/body/end taglib calls. Are you sure you haven't changed anything? > 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" /> Why would it have to change for Tomcat? > 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 :-) Sounds like it might happen that way. If you have a default value for "username" (and friends), why not set those defaults in the setUsername(String) method and use the default when NULL is passed? Also, why is a setter being called on the tag handler when there is no attribute value specified? Something sounds fishy. Does adding 'username="username"' fix the problem when running under Tomcat? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGHQvw9CaO5/Lv0PARAr/ZAJ9q1tAU9JihfSpO1vkvpIpZzqRxHACdGu6V qYgJxerB+azi5kQfeGNKPqM= =WUa5 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
