com.ibm.tivoli.maximo.mfmail.beans.mfmailcfg

Class MfMailCfgAppBean

  • All Implemented Interfaces:
    java.util.EventListener, javax.servlet.http.HttpSessionBindingListener, DataBeanListener


    public class MfMailCfgAppBean
    extends AppBean
    The Class MfMailCfgAppBean.
    • Field Detail

      • logger

        protected final MXLogger logger
        The logger.
    • Constructor Detail

      • MfMailCfgAppBean

        public MfMailCfgAppBean()
    • Method Detail

      • ACTIVATE

        public int ACTIVATE()
                     throws MXException,
                            java.rmi.RemoteException
        Do activation and deactivation.
        Returns:
        Event status
        Throws:
        MXException
        java.rmi.RemoteException
      • afterSetValue

        protected void afterSetValue(java.lang.String attribute)
                              throws java.rmi.RemoteException,
                                     MXException
        Description copied from class: DataBean
        This method is called right after a setValue on a mbo is performed. The setValue can occur in a number of methods so this method does the necessary refreshing and nofitication that the setValue happened.
        Overrides:
        afterSetValue in class DataBean
        Throws:
        java.rmi.RemoteException
        MXException
      • VALIDATE

        public int VALIDATE()
                     throws MXException,
                            java.rmi.RemoteException
        Validate.
        Returns:
        the int
        Throws:
        MXException
        java.rmi.RemoteException
      • initializeApp

        public void initializeApp()
                           throws MXException,
                                  java.rmi.RemoteException
        Description copied from class: AppBean
        This method is called when the presentations "main" page is initalized and before the page is rendered. It can be called multiple times to "reinitialize" the applicaiton, for example when the existing query is reset.

        Only on the first initialize the method also checks for these mutually exclusiive special conditions:

      • if there is a particular record the app needs to jump to (using uniqueid from the loadapp or gotoapp event) the result set is restricted to that record only
      • if there is a startup query sent through the launch in context as a startup where clause it is set as a user where clause
      • if there is an additional ecent "insert" a new record is inserted

        A subsequent call to initializeApp() will not check for these conditions, causing the default reset to happen

Overrides:
initializeApp in class AppBean
Throws:
MXException
java.rmi.RemoteException
  • switchComponentsVisible

    public void switchComponentsVisible()
    Switch components visible.
  • switchComponentsVisible

    public void switchComponentsVisible(MfMailCfgRemote mbo)
    Switch components to visible.
  • renderSections

    public boolean renderSections(boolean isSCRender,
                                  boolean isWFRender)
    Render two sections, SC and WF in E-mail Config app.
    Parameters:
    isSCRender - Render SC section
    isWFRender - Render WF section
    Returns:
    true, if successful
  • processPostRender

    protected void processPostRender()
  • switchVisibility

    public boolean switchVisibility(java.lang.String controlId,
                                    boolean visible)
    Switch visibility.
    Parameters:
    controlId - the id
    visible - the visible
  • getParentTableId

    protected ControlInstance getParentTableId(java.lang.String type,
                                               BaseInstance bi)
    Gets table instance id from the parent by BaseInstance's getParentInstance recursively.
    Parameters:
    bi - BaseInstance
    Returns:
    the parent id