Bogdan Ghidireac wrote: > <webwork:action name="'com.blacksign.emerio.view.LocalServiceBean'" > id="localServiceBean"> > <webwork:param name="'serviceId'" > value="@orderBean/simpleOrder/service/id"/> > </webwork:action> > > <webwork:iterator value="@localServiceBean/directService/items"> > .... > </webwork:iterator> > > > OrderBean.getSimpleOrder() interogates a session bean to get the data so it > is possible to have system/application/communication exceptions. I looked > into the WebWork code and it seems that the exceptions are ignored and null > is returned (ValueStack:370). > > If my actual design is wrong, what is the recomanded way to display data and > to handle the exceptions ?
If you have actions that can result in an error state, then it is advisable that you use the Model-2 approach and not Model-1. I.e. do not use the action tag, but instead do an include of the action. That way you can delegate to an error page if an exception occurs. /Rickard -- Rickard �berg _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
