David H. DeWolf ha scritto:
1) TilesContext is refactored into two different contexts -
TilesContext and TilesRequestContext. Only one instance of the
TilesContext should exist within the application and it will be used
to provide application scoped functions (e.g. getResource() or
getInitParameters()) . The TilesRequestContext will provide
request/response specific operations (e.g. include() or getParameters()).
It seems like a good idea, anyway I would like to know from Greg if it
is ok for him.
2) The TilesContext is instantiated by a configured instance of the
TilesContextFactory at startup (indirectly by the TilesServlet,
TilesFilter, TilesListener or any other initialization feature the
client decides to implement).
For configuration, I would like something like the configuration of
DefinitionsReader, take a look at UrlDefinitionsFactory for that.
3) In the servlet/portlet environment the TilesContext will be saved
as a ServletContext attribute and will be retrieved from here by the
tags and other dependent objects. (Other environments will need their
own mechanism and will be handled in their initialization)
4) The TilesRequestContext will be created by a method on the
TilesContext (createRequestContext(request, response).
I think that a utility class could be, err..., useful :-)
Great work David! I really liked your ideas. It's a pity that it is
ruined by your patch, come on, clean it up! :-)
Ciao
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
