cvs commit: jakarta-velocity/whiteboard/geir_context_20001228 AbstractContext.java

[ge...@locus.apache.org]

geirm       00/12/29 14:19:05

  Modified:    whiteboard/geir_context_20001228 AbstractContext.java
  Log:
  A comment to make clear what I was thinking about with the loadTool() methods.
  
  Revision  Changes    Path
  1.2       +22 -0     jakarta-velocity/whiteboard/geir_context_20001228/AbstractContext.java
  
  Index: AbstractContext.java
  ===================================================================
  RCS file: /home/cvs/jakarta-velocity/whiteboard/geir_context_20001228/AbstractContext.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- AbstractContext.java	2000/12/29 19:21:28	1.1
  +++ AbstractContext.java	2000/12/29 22:19:05	1.2
  @@ -70,7 +70,7 @@
    * abstract routines that access your preferred storage method.
    *
    * @author <a href="mailto:geirm@optonline.net">Geir Magnusson Jr.</a>
  - * @version $Id: AbstractContext.java,v 1.1 2000/12/29 19:21:28 geirm Exp $
  + * @version $Id: AbstractContext.java,v 1.2 2000/12/29 22:19:05 geirm Exp $
    */
   
   public abstract class AbstractContext implements Context, Serializable
  @@ -149,6 +149,28 @@
            *  call the global toolsmith :)  and get the toolset
            *  comprised of globals if request, as well as locals
            *  if specified
  +         */
  +
  +        /*
  +         *  NOTE : just to make it clear what I mean here - if we decide to implement
  +         *  tool management via the velocity.props file (for global tools), then that 
  +         *  tool management code should be used for both the global tools as well
  +         *  as dealing with tool sets the app wants to specify via the loadTool() method.
  +         *
  +         *  so an app can :
  +         *
  +         *  call loadTools() with props/filenam = null and doGlobal = true
  +         *    to get the global toolset into this context
  +         *
  +         *  call loadTools() with a valid props/filename and doGlobal = true
  +         *    to get the global toolset PLUS the toolset in the props/propsfile
  +         *    loaded into this context (by the toolmanager)
  +         *
  +         *  call loadTools() w/ valid props/filename and doGlobal = false
  +         *    to get the toolset in the props/propsfile loaded into this context
  +         *
  +         *  The following line is just to let it compile, until we resolve (maybe) how
  +         *  the global 'toolsmith' will work.
            */
   
           Hashtable h = new Hashtable(); // Runtime.toolsmith( props, doGlobal );