On 8/30/06, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
Michael Jouravlev ha scritto:
> Hi Antonio,
>
> I looked through your code, it is quite clear, so I started pulling
> needed stuff from your library and sticking it into Struts. I also
> want this scope to be available for ActionForms in action mapping
> definition, and for errors/messages.
One of the reasons for which I built Scopes was the possible use in
every layer of the web application, even in the Model, e.g. imagine the
use of Conversation Scope with Spring scopes.
For most uses and purposes Click/Conversation scope is just the
request scope with a little quirk of its content surviving after *one*
roundtrip that follows the scope creation. That is all. No more, no
less.
So for the moment you are doing the right thing pulling the code
directly, but now I am guessing if it is the case of incubating Scopes,
or probably putting it in the sandbox under the Struts umbrella, if it
raises attention by this community.
I personally want to implement just one little feature tightly coupled
with Struts and solving one specific problem, I am not interested in
other scopes. This Click/Conversation scope will be a Struts feature.
Seeing that people already start to misinterpret its purpose, I might
even rename it to "Request Survivor Scope" or just Survivor ;-) I
don't want to start a whole incubating process for the sake of one
simple change.
Michael.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
