You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2004/03/15 09:29:18 UTC
DO NOT REPLY [Bug 27658] New: -
[portal] missing PropertyManagerService implementation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27658>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27658
[portal] missing PropertyManagerService implementation
Summary: [portal] missing PropertyManagerService implementation
Product: Cocoon 2
Version: Current CVS 2.1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: blocks
AssignedTo: dev@cocoon.apache.org
ReportedBy: durdina@asset.sk
Pluto container embedded in Cocoon Portal requires several services (SPI) to be
implemented by portal. PropertyManagerService service is used for setting and
getting vendor specific information by portlets via PortletResponse.setProperty
(), but this service is not implemented by Cocoon Portal. That would be ok
because this service is optional but cocoon throws
CascadingRuntimeException "Unable to lookup service
org.apache.pluto.services.property.PropertyManagerService key" which prevent
the portlet to be started.
There are two possibilities of how this problem could be solved.
1. To implement dummy PropertyManagerServiceImpl which I submit as a patch.
2. Not to throw any exceptions but return null in the
PortletContainerEnvironmentImpl.getContainerService(). This way is pluto portal
going.