| java.lang.Object
 com.sun.portal.community.mc.impl.am.DSAMEMultiPortalConstants
| MP_ATTR_COMMUNITY_HOME_CONTAINER_NAME | | public String MP_ATTR_COMMUNITY_HOME_CONTAINER_NAME(Code) | | |
| MP_ATTR_COMMUNITY_PARENT_CONTAINER_URL_PARAMETER | | public String MP_ATTR_COMMUNITY_PARENT_CONTAINER_URL_PARAMETER(Code) | | |
| MP_ATTR_DEFAULTCHANNELNAME | | public String MP_ATTR_DEFAULTCHANNELNAME(Code) | | |
| MP_ATTR_DESKTOP_TYPE | | public String MP_ATTR_DESKTOP_TYPE(Code) | | |
| MP_ATTR_DP_DOCUMENT_USER | | public String MP_ATTR_DP_DOCUMENT_USER(Code) | | |
| MP_ATTR_DP_LAST_MODIFIED_USER | | public String MP_ATTR_DP_LAST_MODIFIED_USER(Code) | | |
| MP_ATTR_EDITPROVIDERCONTAINERNAME | | public String MP_ATTR_EDITPROVIDERCONTAINERNAME(Code) | | |
| MP_ATTR_PREFIX | | public String MP_ATTR_PREFIX(Code) | | The prefix MP indicates MULTI_PORTAL
Conventionally, the identifiers should be lower case as they are not
being set in the static initilizers. But practically these are
constants for a portal server instance, hence the capitalization.
|
| MP_SUN_DESKTOP_OBJECT_CLASS | | public String MP_SUN_DESKTOP_OBJECT_CLASS(Code) | | |
| MP_SUN_DESKTOP_SERVICE | | public String MP_SUN_DESKTOP_SERVICE(Code) | | |
| createInstance | | public static synchronized void createInstance(String id)(Code) | | |
| getInstance | | public static DSAMEMultiPortalConstants getInstance()(Code) | | For the desktop code, there is always only one instance of this class
since each portal runs in its own JVM. This method returns such
instance which has been created using createInstance. It throws a
ContextError if no instance exists or if more than one instances
exist. So ideally, there will be only one instance in existance
if this class is being properly used in the desktop code.
|
| getInstance | | public static DSAMEMultiPortalConstants getInstance(String id)(Code) | | The desktop code executes in VM in which there is only one
portal. Thus there is a single instance of this
class which gets initialized at the servlet init time.
Once initialized, this never changes during the lifetime of that VM.
But in case of admin mbeans, the situation is different. Different
mbeans belonging to different portals run in the same JVM of the cacao
server. Each mbean knows which portal it belongs to and hence can
request an instance of this class initialized for a specific portal.
So this method is used by the mbeans to get a specific instance. The rule
to use this method still remains same, that is, one MUST first create
an instance before trying to get it, otherwise a ContextError is
thrown.
|
|
|