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.
Regards Sateesh Dave Newton <newton.d...@yahoo.com> 04/14/2009 12:43 PM Please respond to "Struts Users Mailing List" <user@struts.apache.org> To Struts Users Mailing List <user@struts.apache.org> cc Subject Re: Issue with RequestAware sateesh_chand...@harvardpilgrim.org wrote: > Update. RequestAware seems to be working fine with regular dispatcher. We > are seeing the issue when the result type is tiles. I'd wonder if there's another request being made from Tiles to get the tile contents. It's a pretty rare occasion I need to access request attributes (or use RequestAware)--what's the usecase? > Any thoughts? I like potatoes. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org ------------------------------------------------------------------ The information contained in this email message and any attachments may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any review, disclosure, reproduction, distribution or other use of this communication is strictly prohibited. If you received this email in error, please notify the sender by reply and delete the message without saving, copying or disclosing it. Thank you.
