Hi again Mark, Just as a follow-up, you may have missed my message asking for the updated version of your conversation scope interceptor. Moreover, any news about the issue you entered in JIRA concerning this implementation? < http://issues.apache.org/struts/browse/WW-1514 >
Thanks, alexis On 11/04/07, Alexis Pigeon <[EMAIL PROTECTED]> wrote:
On 10/04/07, Mark Menard <[EMAIL PROTECTED]> wrote:
[...]
> You could also take a > look at a simple interceptor I created for this purpose. > (http://www.vitarara.org/cms/node/84) I have since updated that method to > simply be an extension of ModelDriven, if you're interested in the most > recent version let me know. The concept of conversation scope is exactly what I was looking for. The most common situation where I would need it is when having a select input which content depends on the item chosen from another one (for example, a set of two selects representing countries and cities, the content of the latter representing the cities of the chosen country only). In my case, the generation of the "subselect" can be quite time-consuming, thus the need to keep it in some higher scope than the request. As for the Interceptor you wrote, I would be most interested in the most recent version. Thanks for the help, alexis
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
