On Wed, 2002-10-30 at 10:38, Andrus Adamchik wrote: > Andrus Adamchik writes: > > > Greg Turner writes: > > > >> You are talking about the programatic model. Better to use the > >> declarative model as outlined in J2EE spec, where you put security info > >> in the web.xml and ejb-jar.xml files. > > > > Note that with Tapestry this is going to be an all or nothing solution, > > since it is a single servlet - and therefore a single resource from J2EE > > point of view. > > Actually I am probably wrong about this one - after all security constraints > in web.xml are URL based, so pages can be organized into logical groups by > URL prefix. The other limitations are still an issue though
And do you really want security which depends on the URLs in your application? Tom ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
