webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  ExpireWithPageFlow property usage for managed beans

    Posted Mon December 06, 2010 10:27 AM

    hi All,

    Can anybody please explain the use of expireWithPageFlow managed bean property and when should it be set to true / false?

    Kind regards,
    Raja sekhar Kintali


    #webMethods-BPMS
    #webMethods
    #MWS-CAF-Task-Engine


  • 2.  RE: ExpireWithPageFlow property usage for managed beans



  • 3.  RE: ExpireWithPageFlow property usage for managed beans

    Posted Wed December 08, 2010 10:34 AM

    hi Herve,

    Thanks for the reply. It helped me to understand the use of this property and debug one issue in my project :slight_smile: .

    Kind regards,
    Raja sekhar Kintali


    #MWS-CAF-Task-Engine
    #webMethods-BPMS
    #webMethods


  • 4.  RE: ExpireWithPageFlow property usage for managed beans

    Posted Thu June 23, 2016 03:11 AM

    Dear Raja

    Could you please let me know where to do this configuration.

    regards
    Manoj


    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS


  • 5.  RE: ExpireWithPageFlow property usage for managed beans

    Posted Sun June 26, 2016 11:40 PM

    Hi,

    You can set this property for any managed bean in the config file ‘faces-config.xml’.

    It can be found in /webContent/WEB-INF/faces-config.xml.

    Sample managed bean -

    SimpleTableDataProvider com.webmethods.caf.faces.data.object.ListTableContentProvider session Specifies whether the session bean expires when the pageflow is out of scope Expire With Page Flow expireWithPageFlow java.lang.Boolean true .
    #webMethods
    #webMethods-BPMS
    #MWS-CAF-Task-Engine


  • 6.  RE: ExpireWithPageFlow property usage for managed beans

    Posted Mon June 27, 2016 02:26 PM

    In the last few versions of CAF, it is preferred to declare the managed beans via annotations on the java class instead of in the faces-config.xml file. So if are using that mode of operation, then the presence of the @ExpireWithPageFlow annotation on the java class enables the expire behavior.

    For example:

    @ManagedBean(name = "TestDefaultviewView")
    @SessionScoped
    @ExpireWithPageFlow
    @DTManagedBean(displayName = "Test/default", beanType = BeanType.PAGE)
    public class TestDefaultviewView  extends   com.webmethods.caf.faces.bean.BasePageBean {
    ...

    #webMethods
    #webMethods-BPMS
    #MWS-CAF-Task-Engine