psdi.webclient.beans.workman

Class AMPriPrefsBean

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


    public class AMPriPrefsBean
    extends DataBean
    • Constructor Detail

      • AMPriPrefsBean

        public AMPriPrefsBean()
    • Method Detail

      • getPriCalcBean

        public DataBean getPriCalcBean()
                                throws MXException,
                                       java.rmi.RemoteException
        Returns the bean on the PriCalc ("Work Priority Calculation") table so its ID need not be hard-coded elsewhere.
        Throws:
        MXException
        java.rmi.RemoteException
      • getWorkPriorityBean

        public DataBean getWorkPriorityBean()
                                     throws MXException,
                                            java.rmi.RemoteException
        Returns the bean on the WorkPriority ("Work Priority Response Time") table so its ID need not be hard-coded elsewhere.
        Throws:
        MXException
        java.rmi.RemoteException
      • getMboSetRemote

        protected MboSetRemote getMboSetRemote()
                                        throws MXException,
                                               java.rmi.RemoteException
        The points to be made here are: 1) This method is not intended to affect the MboSet on the current bean, AMPriPrefsBean. Rather, it's a way of accessing the databeans on the two tables before display time without having to create named classes for them. Conventional methods don't work here: the default value of the site varies with the user, so it can't be hard-coded in the XML; there's no relationship between the tables and this bean nor between the tables and the main page. Note that the act of calling getMboSet() on each of the table beans insures that the mboSet on each bean will be instantiated at this time, if it wasn't already. Given that, the QBE can be set in the usual way. 2) The current bean has no MboSet attached to it. In such cases, the getMboSetRemote method of DataBean will return null. Rather than simply return null here, the DataBean method has been called, because someday this bean may acquire a MboSet. The desired result is for this method to return exactly what the overridden DataBean method would have returned.
        Overrides:
        getMboSetRemote in class DataBean
        Throws:
        MXException
        java.rmi.RemoteException
      • execute

        public int execute()
                    throws MXException,
                           java.rmi.RemoteException
        The action of the OK button, which is to save both tables on this dialog. Since there's no connection between the tables and the dialog, the table beans are fetched using their IDs and saved directly. Neither the dialog bean nor the parent bean (the AppBean in this case) are to be saved -- the former has no mboSet and the latter is associated with the WMAssignment view, which is never saved in a standard way.
        Overrides:
        execute in class DataBean
        Throws:
        MXException
        java.rmi.RemoteException