com.ibm.tivoli.maximo.mfmail.util

Class MfMailCfg

  • java.lang.Object
    • Constructor Detail

      • MfMailCfg

        public MfMailCfg(MboSet ms)
                  throws java.rmi.RemoteException
        Instantiates a new MfMailCfg object.
        Parameters:
        ms - MboSet
        Throws:
        java.rmi.RemoteException - RemoteException
    • Method Detail

      • canDelete

        public void canDelete()
                       throws MXException,
                              java.rmi.RemoteException
        Description copied from class: Mbo
        Can the object be deleted ? This is object specific and should be overridden.
        Overrides:
        canDelete in class Mbo
        Throws:
        MXException
        java.rmi.RemoteException
      • delete

        public void delete(long accessModifier)
                    throws MXException,
                           java.rmi.RemoteException
        Description copied from class: Mbo
        Mark the object to be deleted depending on the access modifier. This will usually be overridden in the subclass of Mbo as there may be application specific rules as to if and when an object can be deleted. Object is not actually deleted in the database until save() is called. This method will also mark all associated Long Description and Translation Mbos for deletion.
        Specified by:
        delete in interface MboRemote
        Overrides:
        delete in class Mbo
        Parameters:
        accessModifier - The bitwise flag specified to determine if certain normal security checks are to be bypassed for this delete request. For example: if the accessModifer is NOACCESSCHECK, then the check for the object's NODELETE flag and the call to the object's canDelete() method will not be performed. If the accessModifer is NONE, then all the access checks are performed before this object is marked delete.
        Throws:
        MXException
        java.rmi.RemoteException
        See Also:
        Mbo.delete(long)
      • hasConfigChildren

        public boolean hasConfigChildren()
                                  throws MXException,
                                         java.rmi.RemoteException
        Throws:
        MXException
        java.rmi.RemoteException
      • init

        public void init()
                  throws MXException
        Description copied from class: Mbo
        Called by the framework when the Mbo has been constructed and the MboValues have been initialized. This can be overridden by the programmer to provide any custom initialization they would like to do.
        Overrides:
        init in class Mbo
        Throws:
        MXException
      • add

        public void add()
                 throws java.rmi.RemoteException,
                        MXException
        Description copied from class: Mbo
        This is called when a new Mbo is added to the Mboset collection. It is called AFTER user defaults have been set from the data dictionary. Programmer should usually override this to set some defaults. Default behavior is to do nothing.
        Specified by:
        add in interface MboRemote
        Overrides:
        add in class Mbo
        Throws:
        java.rmi.RemoteException
        MXException
      • injectController

        protected void injectController()
                                 throws java.rmi.RemoteException,
                                        MXException
        Inject a controller.
        Throws:
        java.rmi.RemoteException - the remote exception
        MXException - the mX exception
      • isStatusChangeSupported

        public boolean isStatusChangeSupported()
                                        throws MXException,
                                               java.rmi.RemoteException
        Description copied from interface: MfMailCfgRemote
        Checks if is status change supported.
        Specified by:
        isStatusChangeSupported in interface MfMailCfgRemote
        Returns:
        true, if status change scenario supported
        Throws:
        MXException - MXException
        java.rmi.RemoteException - RemoteException
      • isWorkflowSupported

        public boolean isWorkflowSupported()
                                    throws MXException,
                                           java.rmi.RemoteException
        Description copied from interface: MfMailCfgRemote
        Checks if is workflow supported.
        Specified by:
        isWorkflowSupported in interface MfMailCfgRemote
        Returns:
        true, if is workflow scenario supported
        Throws:
        MXException - MXException
        java.rmi.RemoteException - RemoteException
      • save

        protected void save()
                     throws MXException,
                            java.rmi.RemoteException
        Description copied from class: Mbo
        Save the object and other linked objects. Subclasses can code their save() logic to include any appropriate updates to other linked objects and call super.save().
        Overrides:
        save in class Mbo
        Throws:
        MXException
        java.rmi.RemoteException
      • validateCfg

        public void validateCfg(boolean isDuringActivation)
                         throws MXException,
                                java.rmi.RemoteException
        Description copied from interface: MfMailCfgRemote
        Validate the whole configuration.
        Specified by:
        validateCfg in interface MfMailCfgRemote
        Parameters:
        isDuringActivation - the is during activation
        Throws:
        MXException - the mX exception
        java.rmi.RemoteException - the remote exception
      • initFieldFlagsOnMbo

        public void initFieldFlagsOnMbo(java.lang.String attrName)
                                 throws MXException
        Description copied from class: Mbo
        The logic of setting the readonly and required field flags to the mbo. Any setting of the field flags that require expensive operation, such as database query should be moved from init() to this method. However, those which don't require steps such as fetching Mbos can be left in init(). You can group the logic for a few attributes together if logic of deciding their flag is the same, or in other words, can be handled at once.
        Overrides:
        initFieldFlagsOnMbo in class Mbo
        Throws:
        MXException
      • setFieldFlags

        public void setFieldFlags(java.lang.String type)
                           throws MXException,
                                  java.rmi.RemoteException
        Method to set readonly flags for fields based on the type of action.
        Parameters:
        type - Type of the action.
        Throws:
        MXException
        java.rmi.RemoteException