The feature that your describing is the standard J2EE security model. This is a part of any servlet container. Tomcat by itself, without struts or turbine, offers you the same container managed authentication features.
Tim --- Joel Rees <[EMAIL PROTECTED]> wrote: > Oki DZ commented: > > > On 04/23 12:25 Joel Rees wrote: > > > So, do you have a container-managed solution? > > > Somebody does... > > Take a look at http://jakarta.apache.org/turbine/ > > Turbine would be the ultimate servlet container > that will take charge in > > running all your other servlets, so that handling > users that are > authenticated > > or not yet authenticated becomes a piece of cake. > Of course, there's a > > learning curve to climb, but I believe that it > would be worth it. (eg: if > your > > client entered > "http://yourhost.com/some/path/to/a/plain.html"; in > his/her > > browser and yet he/she was not logged in, the > request would be redirected > to a > > login form you had designated.) > > So, how do you think Turbine compares to Struts? > I've been looking at both, > but my colleagues prefer the designated standard > track. > > Joel Rees > Alps Giken Kansai Systems Develoment > Suita, Osaka > > > > > -- > To unsubscribe: > <mailto:[EMAIL PROTECTED]> > For additional commands: > <mailto:[EMAIL PROTECTED]> > Troubles with the list: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
