What I do is that I create an "input" map to the input method on the same action class for which validation is failing. That method is empty (from ActionSupport), and forwards to the page that will show the data. On this page I use the normal tags backed by the action. If multiple tags call the same method then I "cache" the results on the action. I think your problem can easily be solved by making "input" go thru an action, instead of forwarding to the page straight. (but you already knew this :) ) <redundant-email />
regards musachy On Dec 31, 2007 11:41 AM, Adam Hardy <[EMAIL PROTECTED]> wrote: > Happy New Year everybody. > > > This issue is mostly due to the validation failure mechanism which passes flow > direct to the 'input' result without giving a chance to code the data > retrieval > needed to get data for dropdowns, associated lists, etc etc which the view/JSP > will need. > > Currently the assorted solutions to this all seem to be forcing round pegs > into > square holes. For instance, I could make the 'input' result an action chain to > go onto another action which does the data reading. Or I could fetch the data > via an <s:action> or a taglib. > > The S2 documentation says in various places things like: > > "First, we need to change or query the application's state, and then we need > to > present an updated view of the application. The Action class manages the > application's state, and the Result Type manages the view." > > Three or four years ago, this issue with the view was discussed alot. There > was > talk of mechanisms termed 'view-controllers' and concepts such as 'view > logic'. > > I'd love to see this accommodated for in S2. > > There is a certain amount of coding I can do to achieve my goals in the > Results, > but it may not be the best place for it - the name 'Result' implies more of a > link between the Action and the View, rather than a place for coding data > retrieval. > > Essentially I think there is a strong call for a Class or chain of classes > that > can be tied to each particular View, whether Tile, JSP, velocity or whatever. > > This is obviously not what Results were designed for. I can do it currently > but > the S2 config allows only one class per ResultType - so effectively I'd need > one > ResultType per JSP, or some pattern for it. > > The sort of operations I'm thinking of: > > - retrieving lists, sometimes parameterized (e.g. a list of items allowed in a > particular category - requires the categoryId) > > - caching lists (countries in ApplicationScope, personalized data in session > for example) > > - localization of dropdown beans (i.e. country names) > > > Regards > Adam > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
