Michael Jouravlev ha scritto:
I need just one scope, so I don't think that bringing in a whole
library just for one scope makes sense.
I agree...
Also, your library depends on
Java5, while Struts 1 is built on Java 1.4.
I could branch the code for Java 1.4 anyway. For some strange reasons I
decided to use Java 5, though I really needed only Generics.
I have another suggestion: storing data right in the request object
instead of having a dedicated scope object. Then, on redirection,
pushing appropriate items to the session, using item's names. Thus,
the Click scope control object would store names instead of storing
objects themselves. This way we would not have to do anything to
update the search chain page->request->session->app for Struts tags
and JSTL tags. For the tags, Click scope would be just a regular
request scope.
Good point, I will code it ASAP. Thank you for the suggestion :-)
I would also prefer zero configuration, thus better integration with
Struts. Therefore it would be great if you wrote a separate version
specifically for Struts with full integration, or I can do it myself,
taking your code as the basis.
Currently I am going to write a bit of integrations. At the moment I
only wrote integration with Spring 2.0 IoC (even the new Spring has
scopes :-) )
Just a note (I don't know if it will be of interest for you): Scopes has
been released with ASL 2.0, but "window" scope depends on "HTML Parser",
released with LGPL, though the code of "window" scope itself is released
with ASL.
Ciao
Antonio
P.S. Michael, congratulations for your "state management" wiki, i really
liked it :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
