sateesh_chand...@harvardpilgrim.org wrote:
Here is the use case.
It is for a small bi reports triggering application. On the screen 1, user
makes a selection of what reports they want to run. Screen 2 will display
the filters (could be text box, list box or a multi select list box)
applicable to the reports selected in the screen 1. Mapping between report
and filters is maintained in a database. We are fine until retrieving the
filter configuration from the database and render appropriate input
controls on Screen 2. The issue is when user keys-in the input in those
filters and submits. In the corresponding action class, the submitted
values should be retrieved from request, validated and then forwarded to
underlying BI system. As I do not have the details about these parameters
at design time, I thought RequestAware is perfect solution because I get
everything in a map. However this does not seems to be working when the
result type configured in the action is tiles.
You may be confusing attributes with parameters: RequestAware is a map
of request *attributes*.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
