Explanation | This is an error message. The portal system cannot handle this condition without failing. |
Action | Correction of the condition is required. |
Explanation | The portlet container has not been prepared to be called. Therefore the portlet container context is unavailable. |
Action | Please verify that the portlet container is only accessed by valid APIs/SPIs. |
Explanation | This is an error message. The portal system cannot handle this condition without failing. |
Action | Correction of the condition is required. |
Explanation | This is an error message. The portal system cannot handle this condition without failing. |
Action | Correction of the condition is required. |
Explanation | An Exception was received when trying to invoke the portlet. |
Action | Please check the stack trace for the cause of the error. |
Explanation | The RequestDispatcher cannot be found. |
Action | Please contact your System Administrator. |
Explanation | An UnavailableException was received when trying to invoke the portlet. |
Action | Please check the stack trace for the cause of the error. |
Explanation | An UnavailableException was received when trying to invoke the portlet. |
Action | Please check the stack trace for the cause of the error. |
Explanation | An error message was received while processing the portlet. |
Action | Correction of the condition is required. |
Explanation | The ServletContext {0} cannot be found. |
Action | Please contact your System Administrator. |
Explanation | The factory with name {0} cannot be found. |
Action | Please contact your System Administrator. |
Explanation | The factory implementation with name {0} cannot be found. |
Action | Please contact your System Administrator. |
Explanation | The factory implementation with name {0} is not a factory of the required type. |
Action | Please contact your System Administrator. |
Explanation | The factory implementation with name {0} cannot be instantiated. |
Action | Please contact your System Administrator. |
Explanation | An unidentified error occurred. |
Action | Please contact your System Administrator. |
Explanation | A factory couldn't be destroyed. |
Action | Please contact your System Administrator. |
Explanation | User request HTTP POST data is of type application/x-www-form-urlencoded. This data has already been processed by the portal/portletcontainer and is available as request parameters. |
Action | Retrieve user request HTTP POST data as request parameters instead. |
Explanation | It is not allowed to invoke setWindowState after sendRedirect has been called. |
Action | Please verify that setWindowState is allowed when it is called. |
Explanation | New WindowState {0} is not allowed by the portal framework. |
Action | Please check that the WindowState {0} is allowed for the portal framework used. |
Explanation | It is not allowed to invoke setPortletMode after sendRedirect has been called. |
Action | Please verify that setPortletMode is allowed when it is called. |
Explanation | New PortletMode {0} is not allowed by the portal framework. |
Action | Please check that the PortletMode {0} is allowed for the portal framework used. |
Explanation | It is not allowed to invoke sendRedirect after certain methods have been called. |
Action | Please verify that sendRedirect is allowed when it is called. |
Explanation | It is not allowed to invoke setRenderParameters after sendRedirect has been called. |
Action | Please verify that setRenderParameters is allowed when it is called. |
Explanation | Render parameters must not be null. |
Action | Please verify that the render parameters are valid. |
Explanation | Render parameter key must not be null and of type java.lang.String. |
Action | Please verify that the render parameters are valid. |
Explanation | Render parameter value must not be null and of type java.lang.String[]. |
Action | Please verify that the render parameters are valid. |
Explanation | It is not allowed to invoke setRenderParameter after sendRedirect has been called. |
Action | Please verify that setRenderParameter is allowed when it is called. |
Explanation | Render parameter key and value must not be null |
Action | Please verify that the render parameter is valid. |
Explanation | Render parameter key and value must not be null and parameter values must not be an empty array. |
Action | Please verify that the render parameter is valid. |
Explanation | A MalformedURLException was received when trying to get a resource from the PortletContext. |
Action | Please verify that the path for getResource is valid. |
Explanation | Attribute name must not be null. |
Action | Please verify that the attribute name is valid. |
Explanation | Parameter name must not be null. |
Action | Please verify that the parameter name is valid. |
Explanation | Property key must not be null. |
Action | Please verify that the property key is valid. |
Explanation | Preference key must not be null. |
Action | Please verify that the portlet preference key is valid. |
Explanation | Preference with key {0} may not be modified |
Action | Please verify that the portlet preference is not read-only. |
Explanation | This method must not be called after the HTTP-Body was accessed |
Action | Please verify that setCharacterEncoding is allowed when it is called. |
Explanation | Store portlet preferences is only allowed inside a processAction call. |
Action | Please verify that store is allowed when it is called. |
Explanation | An exception was received when trying to include within a portlet. |
Action | Please check the stack trace for the cause of the exception. |
Explanation | Only absolute URLs or full path URIs are allowed for URL encoding. |
Action | Please verify that the given URL is valid and allowed. |
Explanation | getPortletOutputStream cannot be used after getWriter was invoked |
Action | Please verify that getPortletOutputStream is allowed when it is called. |
Explanation | getWriter cannot be used after getOutputStream was invoked |
Action | Please verify that getWriter is allowed when it is called. |
Explanation | Content type provided is either null or not allowed. |
Action | Please verify that the content type is valid. |
Explanation | The current portal implementation does not support security. |
Action | Please do not use security in an unsecure environment. |
Explanation | The class {0} specified as preferences validator must be an implementation of javax.portlet.PreferencesValidator |
Action | Please verify that the specified preferences validator {0} implements javax.portlet.PreferencesValidator |
Explanation | An error was received while loading the preference validator. |
Action | Please analyze the log files for the cause of the error. |
Explanation | WindowState must not be null. |
Action | Please verify that the window state is valid. |
Explanation | PortletMode must not be null. |
Action | Please verify that the portlet mode is valid. |
Explanation | Session attribute {0} with type {1} is not serializable. |
Action | Please use serializable objects as session attributes only. |
Explanation | Session attribute {0} with type {1} is serializable but cannot be serialized. |
Action | Please use serializable objects as session attributes only. |
Explanation | The url provided is either null or not allowed. |
Action | Please verify that the given url is valid for redirection. |
Explanation | An Error was received loading preferences via the PersistenceProvider. |
Action | Please analyze the log files for the cause of the error. |
Explanation | The PreferenceSet returned by the PersistenceProvider is null for the portlet identifier {0}. A default PreferenceSetAdapter is returned instead. |
Action | The PreferenceSet returned for the portlet identifier {0} is not valid. |
Explanation | The PreferenceAccessMode returned by the PersistenceProvider is null for the portlet identifier {0}. |
Action | The PreferenceAccessMode returned for the portlet identifier {0} is not valid. |
Explanation | The operation {0} is not supported. |
Action | Please verify that only supported operations are used. |
Explanation | Only a certain set of interfaces is supported. |
Action | Please verify the implementation of the collaborator - see JavaDoc for more information. |
Explanation | Error while instanciating the collaborator. |
Action | Please check the stack trace and make sure that the correct implementation is defined in the portlet-container-collaborator.xml file. |
Explanation | One of the portlet-container-collaborator.xml files does not specify the collaborators correctly. |
Action | Please check the portlet-container-collaborator.xml that the collaborators are defined correctly. |
Explanation | One of the portlet-container-collaborator.xml files does not specify the collaborators correctly. |
Action | Please check the portlet-container-collaborator.xml that the collaborators are defined correctly. |
Explanation | The tag cannot have a body. |
Action | Modify the tag and remove its body. |
Explanation | Insert and State tags must be nested within the Init tag. |
Action | Modify the tag so that it is nested within the Init tag. |
Explanation | Urlparam tag must be nested within the State tag. |
Action | Modify the tag so that it is nested within the State tag. |
Explanation | Only one Init tag allowed per page. |
Action | Modify the page so that there is only one Init tag. |
Explanation | This tag must have a body. |
Action | Modify the tag so that it contains a body. |