[jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1967) Editing the layout of a portal page not possible if the list of associated portlet instances contains an instance of a remote portlet consumed via WSRP.
Andreas Chlupacek (JIRA)
jira-events at lists.jboss.org
Fri Mar 28 09:57:41 EDT 2008
[ http://jira.jboss.com/jira/browse/JBPORTAL-1967?page=all ]
Andreas Chlupacek updated JBPORTAL-1967:
----------------------------------------
Description:
Two server instances (1 Producer, 1 Consumer) running on the same machine (launched from within Eclipse IDE/JBoss Tools, from two separate launch configurations). Server configurations were provided in distinct directories under JBOSS_HOME/server, the first named "default", the second named "second". In order to avoid port conflicts, service bindings for configuration "second" were altered in JBOSS_HOME/server/second/conf/jboss-service.xml so that the second server loads its bindings from the "ports-01" configuration specified in JBOSS_HOME/docs/examples/binding-manager/sample-bindings.xml.
Steps to reproduce:
===================
The server instance running in "default" configuration is used as consumer, the one running in "second" configuration as producer.
In the WSRP configuration portlet, create a new WSRP consumer named "WSRPTest" on the "default" instance with the following attributes:
Producer id: WSRPTest
Cache expiration: 60
Endpoint configuration not using WSDL
Service Description URL: http://localhost:8180/portal-wsrp/ServiceDescriptionService
Markup URL: http://localhost:8180/portal-wsrp/MarkupService
Registration URL: http://localhost:8180/portal-wsrp/RegistrationService
Portlet Management URL: http://localhost:8180/portal-wsrp/PortletManagementService
On the same server ("default"), navigate to the "Portlet definitions" tab in the management portlet and create an instance of the remotely provided portlet (give it an arbitrary instance name and display name).
Then navigate to the "Portal objects" tab, choose the default portal and try to modify the layout of one of its pages.
Observed behaviour:
===================
The left section ("Content definition") of the Page layout definition screen is missing the content selection box where all the portlet instances are listed. The console shows that a JasperException caused by a NullPointerException is thrown while rendering the PortletContentEditorPortlet. The NPE originates from portal-core.war's /WEB-INF/jsp/content/portlet_editor.jsp, in line 123 => portletMetaInfo.getMetaValue(MetaInfo.DISPLAY_NAME).getDefaultString().
Deleting the WSRP-consumed portlet instance makes the page layout definition screen behave normally again. The list of portlets is shown and it is possible to add a portlet instance to the page.
was:
Two server instances (1 Producer, 1 Consumer) running on the same machine (launched from within Eclipse IDE/JBoss Tools, from two separate launch configurations). Server configurations were provided in distinct directories under JBOSS_HOME/server, the first named "default", the second named "second". In order to avoid port conflicts, service bindings for configuration "second" were altered in JBOSS_HOME/server/second/conf/jboss-service.xml so that the second server loads its bindings from the "ports-02" configuration specified in JBOSS_HOME/docs/examples/binding-manager/sample-bindings.xml.
Steps to reproduce:
===================
The server instance running in "default" configuration is used as consumer, the one running in "second" configuration as producer.
In the WSRP configuration portlet, create a new WSRP consumer named "WSRPTest" on the "default" instance with the following attributes:
Producer id: WSRPTest
Cache expiration: 60
Endpoint configuration not using WSDL
Service Description URL: http://localhost:8180/portal-wsrp/ServiceDescriptionService
Markup URL: http://localhost:8180/portal-wsrp/MarkupService
Registration URL: http://localhost:8180/portal-wsrp/RegistrationService
Portlet Management URL: http://localhost:8180/portal-wsrp/PortletManagementService
On the same server ("default"), navigate to the "Portlet definitions" tab in the management portlet and create an instance of the remotely provided portlet (give it an arbitrary instance name and display name).
Then navigate to the "Portal objects" tab, choose the default portal and try to modify the layout of one of its pages.
Observed behaviour:
===================
The left section ("Content definition") of the Page layout definition screen is missing the content selection box where all the portlet instances are listed. The console shows that a JasperException caused by a NullPointerException is thrown while rendering the PortletContentEditorPortlet. The NPE originates from portal-core.war's /WEB-INF/jsp/content/portlet_editor.jsp, in line 123 => portletMetaInfo.getMetaValue(MetaInfo.DISPLAY_NAME).getDefaultString().
Deleting the WSRP-consumed portlet instance makes the page layout definition screen behave normally again. The list of portlets is shown and it is possible to add a portlet instance to the page.
> Editing the layout of a portal page not possible if the list of associated portlet instances contains an instance of a remote portlet consumed via WSRP.
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBPORTAL-1967
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-1967
> Project: JBoss Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Portal Core Admin
> Affects Versions: 2.6.4 Final
> Environment: JBoss Portal 2.6.4 / JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
> Java version: 1.5.0_11,Sun Microsystems Inc.
> Java VM: Java HotSpot(TM) Client VM 1.5.0_11-b03,Sun Microsystems Inc.
> OS-System: Windows 2000 5.0,x86
> Reporter: Andreas Chlupacek
>
> Two server instances (1 Producer, 1 Consumer) running on the same machine (launched from within Eclipse IDE/JBoss Tools, from two separate launch configurations). Server configurations were provided in distinct directories under JBOSS_HOME/server, the first named "default", the second named "second". In order to avoid port conflicts, service bindings for configuration "second" were altered in JBOSS_HOME/server/second/conf/jboss-service.xml so that the second server loads its bindings from the "ports-01" configuration specified in JBOSS_HOME/docs/examples/binding-manager/sample-bindings.xml.
> Steps to reproduce:
> ===================
> The server instance running in "default" configuration is used as consumer, the one running in "second" configuration as producer.
> In the WSRP configuration portlet, create a new WSRP consumer named "WSRPTest" on the "default" instance with the following attributes:
> Producer id: WSRPTest
> Cache expiration: 60
> Endpoint configuration not using WSDL
> Service Description URL: http://localhost:8180/portal-wsrp/ServiceDescriptionService
> Markup URL: http://localhost:8180/portal-wsrp/MarkupService
> Registration URL: http://localhost:8180/portal-wsrp/RegistrationService
> Portlet Management URL: http://localhost:8180/portal-wsrp/PortletManagementService
> On the same server ("default"), navigate to the "Portlet definitions" tab in the management portlet and create an instance of the remotely provided portlet (give it an arbitrary instance name and display name).
> Then navigate to the "Portal objects" tab, choose the default portal and try to modify the layout of one of its pages.
> Observed behaviour:
> ===================
> The left section ("Content definition") of the Page layout definition screen is missing the content selection box where all the portlet instances are listed. The console shows that a JasperException caused by a NullPointerException is thrown while rendering the PortletContentEditorPortlet. The NPE originates from portal-core.war's /WEB-INF/jsp/content/portlet_editor.jsp, in line 123 => portletMetaInfo.getMetaValue(MetaInfo.DISPLAY_NAME).getDefaultString().
> Deleting the WSRP-consumed portlet instance makes the page layout definition screen behave normally again. The list of portlets is shown and it is possible to add a portlet instance to the page.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list