On 7/24/06, David Evans <[EMAIL PROTECTED]> wrote:
I understand the security concerns, but the flexibility is far more important to me. If a user wants to protect themselves, they can make methods they don't want run by xwork private. Or maybe have an explicit list of <param name="excludeMethods">this,that,theOther</param>.
The framework is as flexible as ever. Action alaises are still supported. The only difference is that you can only declare the alias in an action mapping, or use wildcards. Instead of MyDispatchAction!delete We define an action mapping <action name="delete" class="example.CrudAction" method="delete"> and call the delete acton directly, or simulate the same with wildcards. The URL aliases weren't more "flexible". Just lazy and unsecure. For the configuration-free crowd, I expect alias annotations are (or will be) supported too. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
