I think that going forward with servlet filters is probably the best
way. I still would like to have a Principal implementation so that we
can adhere to the JavaEE spec in some regards, but I agree that doing
the entire auth-constraint would not be worth it at this point.
/dan
On 6/30/05, Timur Vafin <ti...@e-...> wrote:
> Hello,
>=20
> Now I prepare for the project actively using studs.
> There was enough of abstract classes model, action and service which si=
mply enough extend for comfortable work.
>=20
> Shortly I shall try to bring them for discussion as an example of
> the application.
>=20
> As it would be desirable to mention a question of authorization and ses=
sions in discussion.
> What correct way?
>=20
> --
> Send plain text only to timurv at e-kazan dot ru
> PGP key: http://wwwkeys.us.pgp.net:11371/pks/lookup?op=3Dget&search=3D0x=
425B9F0F
> --
> Timur Vafin
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> studs-devel mailing list
> stu...@li...
> https://lists.sourceforge.net/lists/listinfo/studs-devel
>=20
--=20
Open Source Advocacy
http://www.mojavelinux.com
|
