jvanzyl     01/07/13 21:12:53

  Modified:    src/java/org/apache/turbine/modules/screens
                        TemplateScreen.java
  Log:
  - removing redirect because screens will no longer be referenced
    because there will be no such thing as a screen as there was
    in 2.1. this is a move toward a single module type.
  
  Revision  Changes    Path
  1.16      +1 -56     
jakarta-turbine/src/java/org/apache/turbine/modules/screens/TemplateScreen.java
  
  Index: TemplateScreen.java
  ===================================================================
  RCS file: 
/home/cvs/jakarta-turbine/src/java/org/apache/turbine/modules/screens/TemplateScreen.java,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- TemplateScreen.java       2001/07/13 02:20:13     1.15
  +++ TemplateScreen.java       2001/07/14 04:12:53     1.16
  @@ -73,7 +73,7 @@
    * going on there (it is quite simple really).
    *
    * @author <a href="mailto:[EMAIL PROTECTED]";>Dave Bryson</a>
  - * @version $Id: TemplateScreen.java,v 1.15 2001/07/13 02:20:13 jvanzyl Exp $
  + * @version $Id: TemplateScreen.java,v 1.16 2001/07/14 04:12:53 jvanzyl Exp $
    */
   public class TemplateScreen 
       extends Module
  @@ -166,7 +166,6 @@
        */
       public static void setTemplate(RunData data, String template)
       {
  -        //!! need to know what the target template type is.
           setTarget(data,template);
       }
   
  @@ -174,60 +173,6 @@
       {
           data.setTarget(template);
       }        
  -
  -    /**
  -     * You can call this within a Screen to cause an internal redirect
  -     * to happen.  It essentially allows you to stop execution in one
  -     * Screen and instantly execute another Screen.  Don't worry, this
  -     * does not do a HTTP redirect and also if you have anything added
  -     * in the Context, it will get carried over.
  -     *
  -     * <p>
  -     *
  -     * This class is useful if you have a Screen that submits to
  -     * another Screen and you want it to do error validation before
  -     * executing the other Screen.  If there is an error, you can
  -     * doRedirect() back to the original Screen.
  -     *
  -     * @param data Turbine information.
  -     * @param screen Name of screen to redirect to.
  -     * @param template Name of template.
  -     * @exception Exception, a generic exception.
  -     */
  -    public void doRedirect(RunData data, String screen, String template )
  -        throws Exception
  -    {
  -        //!! need more generic way to do a redirect.
  -        //setTemplate(data, template);
  -
  -        Turbine.getModuleLoader().getModule(
  -            Turbine.SCREENS, screen).execute(data);
  -    }
  -
  -    /**
  -     * You can call this within a Screen to cause an internal redirect
  -     * to happen.  It essentially allows you to stop execution in one
  -     * Screen and instantly execute another Screen.  Don't worry, this
  -     * does not do a HTTP redirect and also if you have anything added
  -     * in the Context, it will get carried over.
  -     *
  -     * <p>
  -     *
  -     * This class is useful if you have a Screen that submits to
  -     * another Screen and you want it to do error validation before
  -     * executing the other Screen.  If there is an error, you can
  -     * doRedirect() back to the original Screen.
  -     *
  -     * @param data Turbine information.
  -     * @param template Name of template.
  -     * @exception Exception, a generic exception.
  -     */
  -     public void doRedirect(RunData data, String template)
  -        throws Exception
  -    {
  -        //!! use the resolver for this.
  -        //doRedirect (data, TurbineTemplate.getScreenModule(template), template );
  -    }
   
       public org.apache.turbine.TemplateContext getTemplateContext(RunData data)
       {
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to