I did an webBase ERP and in this context the window scope make sense.
One session, 3 windows, 1 Request and 1 page scope. And I do want to
change the implementation because this way I can use all the Struts
taglib without a change!
You are correct, but what if you are going to use JSTL tags? Do you
have to change that codebase too?
The big problem with scoping is that the servlet specification support
only the 4 famous scopes (application, session, request, page). Other
frameworks are on the path of expanding the number of scopes
(Tapestry, Spring, JBoss Seam), though I don't know if they support
window scope.
Even I am going to publish a library for managing scopes (I am only
waiting for review from Sourceforge team) independently from the
framework (it can be used even with bare servlets).
I think that scoping cannot be solved with a change like that, but
there should be some substantial change.
Agree that it`s a big issue. I use JSTL tags too but it appear that it
didn`t cause me problem with the window scope. Probably that I
manipulate over bean that are put in the request scope...
Maybe I need to open a BUG to propose the enhancement?
Is that make sense?
If you changed Struts code and it worked, then file a bug ticket for
the enhancement, I think that many other can benefit from this change.
I will :-)
Thanks!
Best Regards
/David
Ciao
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
