> > > THIS IS NOT A TOMCAT OR STRUTS ISSUE. THIS IS THE WAY THE > SPEC SAYS TO DO IT. > > Thank you for your time.
Don't think I tried implied otherwise. Just that I've only seen how this works on Tomcat and that I wasn't speaking to other containers. But given that it's a spec thing I'm not sure why Struts dude is concerned about it not being portable from container to container then though... > > Basically, using this method, it's just not possible to allow > > the user to > > log in before trying to grab a protected resource. He has to > > try it first > > and ONLY THEN, will he get a login prompt. > > Yes, per the spec NOT tomcat. Yes, so you've said. :-) > AND, you can do all this with a servlet and container managed > security. See appfuse code for details. I'm sure there are alot of ways to skin that particular cat. What's the advantage of doing it that way over a filter?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
