Package org.eclnt.ccee.spring.v2.context.annotationbased

Class DialogSessionAnnotationApplicationContextFactory

java.lang.Object
org.eclnt.ccee.spring.v2.context.util.DialogSessionApplicationContextFactoryBase
org.eclnt.ccee.spring.v2.context.annotationbased.DialogSessionAnnotationApplicationContextFactory
public class DialogSessionAnnotationApplicationContextFactory extends DialogSessionApplicationContextFactoryBase
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

    • DialogSessionAnnotationApplicationContextFactory

      public DialogSessionAnnotationApplicationContextFactory()

  • Method Details

    • findCreateContext

      public org.springframework.context.support.AbstractApplicationContext findCreateContext(org.eclnt.jsfserver.util.ISessionAbstraction dialogSession, String[] basePackages)
      If NOT being inside a request/response processing then the dialog session needs to be explicitly passed. (e.g. if running in some thread that runs in parallel to request/response processing).
      Returns: