David H. DeWolf ha scritto:
Antonio,
I'm not sure I understand why we need to support both the context and
a map of defaults for retrieving config info for factories. It seems
redundant and thus confusing.
If we want to use a map, shouldn't we just remove the context all
together and have the client push all of the init parameters into the
map prior to invocation?
I made that change (the use of "custom" defaults) because some container
"creators" (such as the TilesPlugin for Struts 1) need to have default
classes when they are not specified explicitly.
In particular, in the TilesPlugin I am wrapping the plugin context and
the ServletContext as a unique ServletContext (giving precedence to the
plugin context init params).
Now, if the Struts application is configured to use modules, it will use
the "keyed" container as a default, otherwise it will use
BasicTilesContainer (this is what I have in mind, there is no code
currently in the Struts-Tiles2 plugin).
So I decided to use a custom "defaults" map. I thought also to provide a
"default" class inside the ServletContext provided by TilesPlugin, but
the code could become a bit messy.
This was I was thinking when I made those changes, anyway if you have a
better idea let me know.
Thank you
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
