[
https://issues.apache.org/jira/browse/PLUTO-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Doremus closed PLUTO-424.
-------------------------------
Resolution: Fixed
This has been completed.
> Support for CCPPProfileService (with DummyImplementation)
> ---------------------------------------------------------
>
> Key: PLUTO-424
> URL: https://issues.apache.org/jira/browse/PLUTO-424
> Project: Pluto
> Issue Type: New Feature
> Components: portlet container
> Affects Versions: 2.0.0, 1.1-286-COMPATIBILITY
> Reporter: Christian Raschka
> Priority: Minor
> Fix For: 2.0.0, 1.1-286-COMPATIBILITY
>
> Attachments: dummyccppprofileservice.280807.patch
>
>
> See PLT.11.1.3.2 The CC/PP Request Attribute:
> The portlet can access a Composite Capability/Preference Profile (CC/PP, W3C:
> Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies
> http://www.w3.org/TR/2001/WD-CCPP-struct-vocab-20010315/) javax.ccpp.profile
> via
> the request attribute PortletRequest.CCPP_PROFILE.
> The PortletRequest.CCPP_PROFILE request attribute must return a
> javax.ccpp.Profile
> based on the current portlet request. c It may contain additional CC/PP
> information set by
> the portal / portlet container. (See JSR 188 (CC/PP Processing,
> http://jcp.org/en/jsr/detail?id=188) for more details on CC/PP profile
> processing).
> Note that once the CC/PP profile API provides a factory method taking the
> PortletRequest / PortletResponse as parameters this attribute may become
> deprecated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
