While it does not only apply to security..... For one it breaks the idea that your actions are components. You cannot pull them into other apps without being bound to behavior of the parent.
I may want to expose the same action under "/demo" (no or different security) without recompiling it/things. Matt -----Original Message----- From: Adam Zimowski [mailto:[EMAIL PROTECTED] Sent: Friday, April 14, 2006 3:19 PM To: Tapestry users Subject: Re: tapestry for a webwork developer Just curious.... What is in your optionion wrong with inheritance-based security model ? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message, including any attachments, is intended only for the recipient(s) named above. It may contain confidential and privileged information. If you have received this communication in error, please notify the sender immediately and destroy or delete the original message. Also, please be aware that if you are not the intended recipient, any review, disclosure, copying, distribution or any action or reliance based on this message is prohibited by law. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
