|
Hello group, I just realized that the ExecuteWhen.AfterRendering phase of a filter is not executed if no view is rendered using a view engine. That is, if - CancelView is called -or- - RenderText is used no filters that listen to ExecuteWhen.AfterRendering are executed. If this is intentional behaviour I think it should be documented. One might be tempted to e.g. open a transaction in AfterAction and close it in AfterRendering, which can cause strange effects if no view is rendered. Maybe we could add an extra ExecuteWhen phase that is invoked at the end of the request, regardless of a view being rendered or not. What do you think? Kind regards , Andre --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~--- |
- ExecuteWhen.AfterRendering Andre Loker
- Re: ExecuteWhen.AfterRendering Ken Egozi
- Re: ExecuteWhen.AfterRendering Andre Loker
- Re: ExecuteWhen.AfterRendering Ken Egozi
- Re: ExecuteWhen.AfterRendering Andre Loker
- Re: ExecuteWhen.AfterRendering Ken Egozi
- Re: ExecuteWhen.AfterRendering Rafael Teixeira
- Re: ExecuteWhen.AfterRendering Andre Loker
