[JBoss JIRA] Created: (GTNPORTAL-2107) Can't register a consumer if an error occurs during the intial registration
by Matt Wringe (JIRA)
Can't register a consumer if an error occurs during the intial registration
----------------------------------------------------------------------------
Key: GTNPORTAL-2107
URL: https://issues.jboss.org/browse/GTNPORTAL-2107
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: WSRP integration
Reporter: Matt Wringe
Assignee: Chris Laprun
If an error occurs during the registration (for example, a class not found exception, or something similar) then the registration gets placed in an invalid state.
When the server is restarted with the error corrected, the consumer can't be re-registered since it thinks the registration has already taken place, but the original registration never completed due to an error.
Caused by: org.oasis.wsrp.v2.OperationFailed: Could not register consumer named 'localhost.localdomain WSRP v2 version' Cause: Consumer named 'localhost.localdomain WSRP v2 version' has already been registered with the same set of registration properties. Registration rejected!
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (GTNPORTAL-2406) Fully scope the Portlet Container Engine to the RootContainer
by Nicolas Filotto (JIRA)
Nicolas Filotto created GTNPORTAL-2406:
------------------------------------------
Summary: Fully scope the Portlet Container Engine to the RootContainer
Key: GTNPORTAL-2406
URL: https://issues.jboss.org/browse/GTNPORTAL-2406
Project: GateIn Portal
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: PC integration
Affects Versions: 3.2.0-GA
Reporter: Nicolas Filotto
Assignee: Matt Wringe
The current integration of the PC is incorrect as we have one half scoped to the RootContainer (the FederatingPortletInvoker) and the rest to the PortalContainers. The goal of this task is to see if the integration can be reviewed to scope everything to the RootContainer, this way we will also have only one PC engine for all the portal containers.
See below one way to do it:
# Remove any references of the TopContainer and the ResourceBundleService from ExoKernelIntegration
# Remove the configuration file portal/WEB-INF/conf/common/portlet-container-configuration.xml (or at least its content)
# Configure the component ExoKernelIntegration in conf/configuration.xml that will be internal to exo.portal.component.pc
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years