Hi Joe, Thanks for the tip, this definately works. Looking at the way the request processor functions, I don't think there is a situation where it will cause a problem that a true is ignored. The reason for this is that all the conditions which result in a failure situation will throw an exception.
Side note: I did find an alternate way of accomplishing this without setting the lookup to ignore the return value. The exception processor catalog has the very same view commands as the normal "process-view" catalog. If I was to throw an exception in the AuthorizeAction (like the Struts class does) I could deal with it later on in the exception processing catalog. Personally I think the way you helped me with is more efficient, because it eliminates the overhead of the exception handling. Thanks again! Aaron > >Intuitively, I expected the same behavior you expected, but that's not how >the commons-chain package was first implemented. This should do it, unless >you sometimes want the lookup to return Command.PROCESSING_COMPLETE (that >is, true) When using "ignoreExecuteResult," LookupCommand always returns >Command.CONTINUE_PROCESSING (false). > >Joe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
