Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 809526

Summary:	EPP-SP: UIDefaultSearchResult throws "NullPointerException: No null parameter name"
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	Martin Weiler <mweiler>
Component:	Site Publisher	Assignee:	Nobody <nobody>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.2.0.GA, 5.2.0.SP.GA	CC:	epp-bugs, pjha
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Using the Advanced Search Portlet after migrating from EPP-SP 5.1.x to 5.2.0 did not return any results for some search terms, and instead an exception could be seen in the log file. The reason for this exception was a missing portlet preference in the migration data. This has been fixed in the current release.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:19:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Weiler 2012-04-03 15:15:59 UTC

Description of problem:
UIDefaultSearchResult throws "NullPointerException: No null parameter name"


Steps to Reproduce:
1. create a new EPP 5.2 installation
2. start it
3. login as root
4. register WCM Advanced Search Portlet
5. add it to a new page
6. search for 'a'
=> exception:
ERROR [PortletApplicationController] Error while rendering the porlet
org.exoplatform.groovyscript.TemplateRuntimeException: Groovy template exception at DataText[pos=Position[col=1,line=100],data=       itemUrl = uicomponent.getURL(viewNode);] for template /exo:ecm/views/templates/WCM Advance Search/search-result/UIDefaultSearchResult.gtmpl
	at org.exoplatform.groovyscript.GroovyScript.buildRuntimeException(GroovyScript.java:178).
  

Additional info:
This problem was fixed and will be integrated in wcm2.3.6.
The fix provided in : https://jira.exoplatform.org/browse/ECMS-3501


As workaround for this problem, you would add the 'detailParameterName' preference to portlet.xml of WCMAdvanceSearchPortlet
apps/portlet-search/src/main/webapp/WEB-INF/portlet.xml
===================================================================
--- apps/portlet-search/src/main/webapp/WEB-INF/portlet.xml	(revision 80146)
+++ apps/portlet-search/src/main/webapp/WEB-INF/portlet.xml	(working copy)
@@ -76,6 +76,11 @@
         <value>detail</value>
         <read-only>false</read-only>
       </preference>
+      <preference>
+        <name>detailParameterName</name>
+        <value>content-id</value>
+        <read-only>false</read-only>
+      </preference>
     </portlet-preferences>

Comment 2 Martin Weiler 2012-04-11 10:30:21 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Using the Advanced Search Portlet after migrating from EPP-SP 5.1.x to 5.2.0 did not return any results for some search terms, and instead an exception could be seen in the log file. The reason for this exception was a missing portlet preference in the migration data. This has been fixed in the current release.

Comment 3 prabhat jha 2012-04-12 15:33:02 UTC

Change to Verified on behalf of Tomas K.

Comment 5 Red Hat Bugzilla 2025-02-10 03:19:29 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.