Package org.beanlet.web

Adds web specific beanlet scopes.

See:
          Description

Interface Summary
WebContext Provides access to the web runtime context of the beanlet instance.
 

Class Summary
ServletContextListener Add the following configuration to the web application's web.xml file to support the Request and Session beanlet scopes.
 

Annotation Types Summary
Request Request beanlets do not provide direct access to the underlying objects.
Session Session beanlets do not provide direct access to the underlying objects.
WebFilter The annotation used to declare a Servlet Filter.
WebListener The annotation used to declare a listener for various types of event, in a given web application context.
WebServlet This annotation is used to declare the configuration of an Servlet.
 

Package org.beanlet.web Description

Adds web specific beanlet scopes.

Beanlet Scopes

The Beanlet web package comes with two object scopes:

Static versus Non-Static

Beanlets are created in either a static or a non-static context. Static, in this context, means that beanlets are created independently from the current state of the container or application. Static beanlets are created at the container's discretion and therefore do not allow applications to pass any state to this component while it is being created. Non-static beanlets are only created upon application request. Applications can pass objects - or state if you will - by using wiring BY_INFO dependency injection. Use the BeanletMetaData interface to find out whether a beanlet is static, or not.

The static property of a beanlet is derived from the selected beanlet scope, i.e., singleton vanilla beanlets are static, where non-singleton vanilla beanlets are non-static. The following table shows the static property for all web beanlet scopes.


singletonreentrantstatic
RequestN/AN/Afalse
SessionN/Atrue/falsefalse



Copyright © 2006-2012. All Rights Reserved.