webMethods and Intelligent Business Operations 10.2 | Designing and Implementing Composite Applications | webMethods CAF and OpenCAF Development Help | Composite Application Framework Concepts | About Managed Beans
 
About Managed Beans
 
Setting the Managed Bean Expiration Policy
A managed bean is a Java class that represents a portlet resource, including a description of its attributes, operations, notifications, its unique name within a portlet application, a bean type, and a scope. The scope determines how long the bean exists within the application.
Managed beans are found in the Bindings view. By default, the Bindings view displays only managed beans associated with the page bean currently displayed on the design canvas. You can optionally display all managed beans in the Bindings view. For more information, see Enabling the Show All Managed Beans Toolbar Button.
The table below describes the managed bean scope values and their definitions.
Scope
Description
Application
Facilitates portlet-to-portlet communication. The managed bean is started once and does not expire until the server shuts down or the portlet application is re-published to the server.
Session
Default. Limits the life of the managed bean to the user session. Portlets using this scope cannot share data with other portlets. The managed bean expires when the user session ends.
Request
Expires when the response to the request is sent back to the client. The managed bean life span is that of a single request.
None
Creates the bean every time it is requested.

Copyright © 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release