Yup, GenericDispatcher was specifically designed for this situation (well,I'll have a proper look at this tonight, but it seems that the only way that I can currently get data into an Action is using "params" that is used to set the parameters. How do I deal with the case where I store some data in the Session? At a quick glance through the code, it only deals with actions that are/were ParameterAware (if you see what I mean) Time to extend the AbstractActionTest with all the bits that are "missing" :)
and others).
Although this feels a bit "heavier" than the solution offered by XAwareActionFactoryProxy, I'll try writing tests using both methods and see which I prefer. It's probably just a case of Not Invented Here *shrugs* The only other thing that comes to mind is that by implementing *Aware interfaces an Action makes obvious and explicit what it's expecting, and where, which might be handy if anyone else but myself has to look at this code (esp. given my commenting habits) I'll have a scan of the archives for why they've been deprecated.
Regards,
Simon
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
