Class DialogSessionApplicationContextFactoryBase

java.lang.Object
org.eclnt.ccee.spring.v2.context.util.DialogSessionApplicationContextFactoryBase
Direct Known Subclasses:
DialogSessionAnnotationApplicationContextFactory, DialogSessionXMLApplicationContextFactory

public class DialogSessionApplicationContextFactoryBase extends Object
CaptainCasa' server processing is always within a scope of a dialog session. This might be a real http session (if using URL-jssesionid-rewriting) or if might be some session-mechanism below the http session (if using COOKIE based URL-session-tracking).

For each dialog session there is an own DialogSessionApplicationContext which is available during the request/response processing on server side.

The application context itself is picked from the web-application-context, where it is defined with name: .
  • Constructor Details

    • DialogSessionApplicationContextFactoryBase

      public DialogSessionApplicationContextFactoryBase()
  • Method Details

    • checkIfAbstractApplicationContextIsRegistered

      protected boolean checkIfAbstractApplicationContextIsRegistered(org.eclnt.jsfserver.util.ISessionAbstraction dialogSession)
    • readApplicationContextFromDialogSession

      protected org.springframework.context.support.AbstractApplicationContext readApplicationContextFromDialogSession(org.eclnt.jsfserver.util.ISessionAbstraction dialogSession)
    • registerContextInDialogSession

      protected void registerContextInDialogSession(org.eclnt.jsfserver.util.ISessionAbstraction dialogSession, org.springframework.context.support.AbstractApplicationContext applicationContext)