Hei This sort of functionality is very complex, especially when you start to move into authentication for data. My take on this, is that this warrants a project of its own - preferably on ASF. That way we could get input from other ASF projects that might need something like this also and we all benefit. I don not think that we should attempt to solve this completely within the Shale realm.
Hermod -----Opprinnelig melding----- Fra: Niall Pemberton [mailto:[EMAIL PROTECTED] Sendt: 4. mars 2006 03:17 Til: Struts Users Mailing List Emne: Re: Shale & Container Managed Security On 3/4/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On 3/3/06, Niall Pemberton <[EMAIL PROTECTED]> wrote: > > > > If something like this is developed then it shouldn't be tied to > > container managed security (i.e. request.isUserInRole()) and should be > > easy to plug in custom implementations which could cater for other > > scenarios/criteria, such as the above. > > Just logged an RFE[1] to capture this idea. Feel free to add any and all > details about requirements (I just used one of the motivating examples) ... > and/or volunteer to do any or all of the implementation work :-). Thanks I added a comment. If it waits for me, it might be a while - but then again commits count for more than opinions, so maybe I should pull my finger out... Niall > Sorry, just wanted to put in my 2cents, in case someone actually does > > something about this - that way when I move to Shale.... :-) > > Resistance is futile ... :-). > > Niall > > > Craig > > [1] http://issues.apache.org/bugzilla/show_bug.cgi?id=38849 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
