[ http://nagoya.apache.org/jira/browse/JELLY-167?page=comments#action_55940 ] Hans Gilde commented on JELLY-167: ----------------------------------
newJellyContext exists so that you can override it. The idea is that a subclass Of JellyContext might want to implement certain behavior when creating a "child" context or a context to run in another thread. I'm not in favor of adding this method to JellyContext because it's not used by the core Jelly API. If you want to copy a context in a particular way, why not just create a new static method for yourself (outside of the Jelly API): public static JellyContext cloneContext(JellyContext cloneMe) > add 'public JellyContext newEmptyJellyContext()' to JellyContext > ---------------------------------------------------------------- > > Key: JELLY-167 > URL: http://nagoya.apache.org/jira/browse/JELLY-167 > Project: jelly > Type: Wish > Components: core / taglib.core > Versions: 1.0-beta-5 > Reporter: Marc DeXeT > > method 'public JellyContext newJellyContext()' uses 'public > JellyContext(JellyContext parent)'. > This constructor copies parent properties AND parent variables. > To create variables quenched context, you have to clear variables or to set > inherit to false. > I wish to have a new method 'public JellyContext newEmptyJellyContext()' > which copies all root context properties (as tag caching) but DOESN'T copy > variables map. > Even if you could do the same with inherit or variable map clearing or other > methods, it would be more meaningful to use a assigned method -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
