Bug 109963 - Unable to create an instance of the ContentItemPortlet
Unable to create an instance of the ContentItemPortlet
Status: CLOSED RAWHIDE
Product: Red Hat Enterprise CMS
Classification: Retired
Component: other (Show other bugs)
nightly
All Linux
medium Severity medium
: ---
: ---
Assigned To: Richard Li
Jon Orris
:
Depends On:
Blocks: 106481
  Show dependency treegraph
 
Reported: 2003-11-13 09:42 EST by Daniel Berrange
Modified: 2007-04-18 12:59 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-01-26 16:34:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Daniel Berrange 2003-11-13 09:42:39 EST
Description of problem:
When trying to add a 'Content Item' to a portal, an NPE is thrown when
submitting the form. If i remove the '/ccm' prefix on the path to the
item, the NPE goes away, but it simply says 'cannot find contnet item'
instead.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create an item 'foo' in /content/
2. Publsh the item
3. Add a content item portlet, entering /ccm/content/foo.en as the
item url
  
Actual results:
NPE

Expected results:
The portlet is added.

Additional info:
Comment 1 Jon Orris 2003-11-25 16:53:47 EST
Relevant stack trace:
java.lang.NullPointerException
	at
com.arsdigita.cms.dispatcher.SimpleItemResolver.getItem(SimpleItemResolver.java:105)
	at
com.arsdigita.cms.ui.portlet.ContentItemPortletEditor$1.initialValue(ContentItemPortletEditor.java:73)

Looks like the underlying impl of ContentSection.getSectionFromNode
has changed, and no longer throws a DataObjectNotFoundException;
instead the section is returned null, leading to the NPE.

Comment 2 Richard Li 2004-01-07 14:58:44 EST
I implemented a partial fix @39176. All this does is check if the
dispatcher prefix exists, and, if so, removes it.

The other issue that needs to be resolved is support for multilingual
content items/URLs -- I just noticed your example above, and that case
isn't handled right now.
Comment 3 Richard Li 2004-01-07 15:08:16 EST
@39177 switches to using the MultilingualItemResolver.

Dan, does this fix the problems?
Comment 4 Daniel Berrange 2004-01-08 04:54:51 EST
In the short term yes. Ideally we should be calling
ContentSection#getItemResolver IIRC to return the currently configured
item resolver for the section.

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