org.exoplatform.web
Class WebAppController

java.lang.Object
  extended by org.exoplatform.web.WebAppController

public class WebAppController
extends java.lang.Object

Created by The eXo Platform SAS Mar 21, 2007 The WebAppController is the entry point of the eXo web framework It also stores WebRequestHandlers, Attributes and deployed Applications


Field Summary
protected static org.apache.commons.logging.Log log
           
 
Constructor Summary
WebAppController()
          The WebAppControler along with the PortalRequestHandler defined in the init() method of the PortalController servlet (controller.register(new PortalRequestHandler())) also add the CommandHandler object that will listen for the incoming /command path in the URL
 
Method Summary
 void addApplication(Application app)
           
<T extends Application>
T
getApplication(java.lang.String appId)
           
 java.util.List<Application> getApplicationByType(java.lang.String type)
           
 java.lang.Object getAttribute(java.lang.String name, java.lang.Object value)
           
 void register(WebRequestHandler handler)
           
 void removeApplication(java.lang.String appId)
           
 void service(javax.servlet.http.HttpServletRequest req, javax.servlet.http.HttpServletResponse res)
          This is the first method - in the eXo web framework - reached by incoming HTTP request, it acts like a servlet service() method According to the servlet path used the correct handler is selected and then executed.
 void unregister(java.lang.String[] paths)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

log

protected static org.apache.commons.logging.Log log
Constructor Detail

WebAppController

public WebAppController()
                 throws java.lang.Exception
The WebAppControler along with the PortalRequestHandler defined in the init() method of the PortalController servlet (controller.register(new PortalRequestHandler())) also add the CommandHandler object that will listen for the incoming /command path in the URL

Throws:
java.lang.Exception
Method Detail

getAttribute

public java.lang.Object getAttribute(java.lang.String name,
                                     java.lang.Object value)

getApplication

public <T extends Application> T getApplication(java.lang.String appId)

getApplicationByType

public java.util.List<Application> getApplicationByType(java.lang.String type)

removeApplication

public void removeApplication(java.lang.String appId)

addApplication

public void addApplication(Application app)

register

public void register(WebRequestHandler handler)
              throws java.lang.Exception
Throws:
java.lang.Exception

unregister

public void unregister(java.lang.String[] paths)

service

public void service(javax.servlet.http.HttpServletRequest req,
                    javax.servlet.http.HttpServletResponse res)
             throws java.lang.Exception
This is the first method - in the eXo web framework - reached by incoming HTTP request, it acts like a servlet service() method According to the servlet path used the correct handler is selected and then executed. The event "exo.application.portal.start-http-request" and "exo.application.portal.end-http-request" are also sent through the ListenerService and several listeners may listen to it. Finally a WindowsInfosContainer object using a ThreadLocal (from the portlet-container product) is created

Throws:
java.lang.Exception


Copyright © 2010 eXo Platform SAS. All Rights Reserved.