Esempio n. 1
0
 /// <summary>
 /// <p>
 /// Set the an ApplicationAttribue, which is an Object
 /// set by the application which is accessable from
 /// any component of the system that gets a RuntimeServices.
 /// This allows communication between the application
 /// environment and custom pluggable components of the
 /// Velocity engine, such as loaders and loggers.
 /// </p>
 /// <p>
 /// Note that there is no enfocement or rules for the key
 /// used - it is up to the application developer.  However, to
 /// help make the intermixing of components possible, using
 /// the target Class name (e.g.  com.foo.bar ) as the key
 /// might help avoid collision.
 /// </p>
 /// </summary>
 /// <param name="key">object 'name' under which the object is stored</param>
 /// <param name="value">object to store under this key</param>
 public virtual void SetApplicationAttribute(System.Object key, System.Object value_Renamed)
 {
     ri.setApplicationAttribute(key, value_Renamed);
 }
Esempio n. 2
0
 /// <summary>
 /// <p>
 /// Set the an ApplicationAttribue, which is an Object
 /// set by the application which is accessable from
 /// any component of the system that gets a RuntimeServices.
 /// This allows communication between the application
 /// environment and custom pluggable components of the
 /// Velocity engine, such as loaders and loggers.
 /// </p>
 /// <p>
 /// Note that there is no enfocement or rules for the key
 /// used - it is up to the application developer.  However, to
 /// help make the intermixing of components possible, using
 /// the target Class name (e.g.  com.foo.bar ) as the key
 /// might help avoid collision.
 /// </p>
 /// </summary>
 /// <param name="key">object 'name' under which the object is stored</param>
 /// <param name="value">object to store under this key</param>
 public void SetApplicationAttribute(Object key, Object value_)
 {
     ri.setApplicationAttribute(key, value_);
 }