I'm moderately interested as I'm presently defining that part of the architecture for a new development that is just getting underway.
Jim > -----Original Message----- > From: Andy Noble [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 11, 2001 1:31 PM > To: Struts Developers List > Subject: Re: role based actions > > > I'm using Nic Hobb's extension, although I rewrote his > ActionSecurity class > to support application managed security instead of container > managed. I also > created my own security tag to replace the <html:present > roles=".."> tag > > If anyone's interested in the code, let me know. > > Andy > ----- Original Message ----- > From: Ted Husted <[EMAIL PROTECTED]> > To: Struts Developers List <[EMAIL PROTECTED]> > Sent: Tuesday, December 11, 2001 6:44 PM > Subject: Re: role based actions > > > > Craig, have you looked at Nic Hobb's extension? > > > > http://husted.com/struts/resources/struts-security.htm > > > > There's a place on my agenda where I was going to try it myself, but > > still haven't gotten there. > > > > -Ted. > > > > "Craig R. McClanahan" wrote: > > > Adding this (and a few of the other recent enhancements) > to Struts 1.1 > is > > > definitely on *my* list. I will have some time to do so between > Christmas > > > and New Years. > > > > > > Craig McClanahan > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > <font size="1">Confidentiality Warning: This e-mail contains information intended only for the use of the individual or entity named above. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, any dissemination, publication or copying of this e-mail is strictly prohibited. The sender does not accept any responsibility for any loss, disruption or damage to your data or computer system that may occur while using data contained in, or transmitted with, this e-mail. If you have received this e-mail in error, please immediately notify us by return e-mail. Thank you.
