DO NOT REPLY [Bug 7456] - Improving the Velocity Context interface

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7456>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7456

Improving the Velocity Context interface

geirm@optonline.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From geirm@optonline.net  2002-04-27 17:44 -------
First, I agree with you that smaller is better when it comes to contexts, as 
adding the responsibility to support the additional methods is a pain for 
people.

But it's not clear that you could remove things like put() w/o causing great 
stress.  For example, since the implementation of Context is left to the 
user, any framework code (including our VelocityServlet base) that has 
methods where Context is a parameter can be problematic, as it means
that there can't be some kind of factory creating contexts, letting the 
overloaded methods fill the context with data :

  public void populate(Context ctx )
  {
     ctx.put("mylist", nameList);
 }


So I'll mark this as 'wont fix' - we really can't change the context this late in 
the game (backwards compatibillity) and at least with common patterns 
used by Velocity developers, being able to allow framework code modify 
the context is essential.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>