Bug 809526 - EPP-SP: UIDefaultSearchResult throws "NullPointerException: No null parameter name"
Summary: EPP-SP: UIDefaultSearchResult throws "NullPointerException: No null parameter...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Site Publisher
Version: 5.2.0.GA,5.2.0.SP.GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-03 15:15 UTC by Martin Weiler
Modified: 2025-02-10 03:19 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:19:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
EXO WCM JIRA ECMS-3501 0 None None None Never
EXO WCM JIRA SPREDHAT-133 0 None None None Never

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.


Note You need to log in before you can comment on or make changes to this bug.