Message:

   The following issue has been resolved as FIXED.

   Resolver: David Sean Taylor
       Date: Tue, 6 Jul 2004 4:36 PM

This completes my work on this features.
Note to DLS:
 Although you can get the portlet context at any time, I believe that the proper 
sequence for getting a Jetspeed Portlet Service is to get it in the init() and then to 
throw an exception to the portal if you cannot find the dependent service

        context = getPortletContext();                
        registry = 
(PortletRegistryComponent)context.getAttribute(PortletApplicationResources.CPS_REGISTRY_COMPONENT);
        if (null == registry)
        {
            throw new PortletException("Failed to find the Portlet Registry on portlet 
initialization");
        }

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-70

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-70
    Summary: Support Service definitions in Jetspeed extended portlet descriptor
       Type: New Feature

     Status: Resolved
   Priority: Major
 Resolution: FIXED

    Project: Jetspeed 2
 Components: 
             Deployment
   Fix Fors:
             2.0-dev/cvs
   Versions:
             2.0-dev/cvs

   Assignee: David Sean Taylor
   Reporter: David Sean Taylor

    Created: Fri, 4 Jun 2004 1:59 PM
    Updated: Tue, 6 Jul 2004 4:36 PM

Description:
1. Support Service definitions in Jetspeed extended portlet descriptor.
Portlets can define which CPS services they requires as follows:

<services>
    <service name='PortletRegistryComponent'>
    <service name='PortletEntityAccessComponent'>
</service>

These services will then be available as PortletContext attribute.

2. Enhance the PA to validate service declarations above

3. implement PortlteContext.getAttribute("cps:ComponentName")


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to