Class Lifecycle<E extends UIComponent>

java.lang.Object
org.exoplatform.webui.core.lifecycle.Lifecycle<E>
Direct Known Subclasses:
UIApplicationLifecycle, UIComponentDecorator.UIComponentDecoratorLifecycle, UIContainerLifecycle, UIFormLifecycle, UIPageLifecycle, UIPortalApplicationLifecycle, UIPortalLifecycle, UIPortletLifecycle

public class Lifecycle<E extends UIComponent> extends Object
Created by The eXo Platform SAS May 7, 2006
  • Field Details

    • log

      protected static org.exoplatform.services.log.Log log
  • Constructor Details

    • Lifecycle

      public Lifecycle()
  • Method Details

    • processDecode

      public void processDecode(E uicomponent, WebuiRequestContext context) throws Exception
      Throws:
      Exception
    • processAction

      public void processAction(E uicomponent, WebuiRequestContext context) throws Exception
      Throws:
      Exception
    • processRender

      public void processRender(E uicomponent, WebuiRequestContext context) throws Exception
      That method is the most generic one for every UIComponent that is bound to this Lifecycle object and the class that extends it without overriding the method. The template associated to the specified UIComponent is rendered using renderTemplate(). A WebuiBindingContext context object provides the template with all the necessary objects to render. (WebuiBindingContext extends the Map class)
      Throws:
      Exception
    • renderTemplate

      protected void renderTemplate(String template, WebuiBindingContext bcontext) throws Exception
      The method allows to use Groovy templates to render the portal components.
      1. Add a decorator object into the context
      2. Get a reference to the TemplateService
      3. If the system property "exo.product.developing" is set to true, the templates are not cached
      4. If the writer used to render the output is of type HtmlValidator, which is the case in the Portal environment, then it is also possible to validate the generated HTML (for debugging purposes)
      5. The template and the context are then merged to generate the HTML fragment
      Throws:
      Exception