Maybe I'm missing something, but it still seems to me that your problem is easily handled by context variables and view mappings. I assume you are using a standard MVC architecture?
You are not limited to just "failure" and "success" outcomes... and the event that is fired (the method invocation) is only very loosely tied to the outcome. True, you can probably create custom view handlers to resolve the views after the InvokeApplication phase, but I don't think that's necessary in your case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912489#3912489 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912489 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
