You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by je...@jakarta.apache.org on 2004/07/07 01:36:54 UTC
[jira] Resolved: (JS2-70) Support Service definitions in Jetspeed extended portlet descriptor
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: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Resolved: (JS2-70) Support Service definitions in Jetspeed extended portlet descriptor
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Jul 8, 2004, at 10:30 AM, Scott T. Weaver wrote:
> Correct MVC would say that would not need access to the service in the
> JSP. However, you still might want to access the service from within
> a servlet that has been delegated from the render() method.
>
Guys go ahead and re-open the issue, and enhance it per your needs
Im not going to have time to work on this feature, but I have no issues
with your proposals
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Resolved: (JS2-70) Support Service definitions in Jetspeed
extended portlet descriptor
Posted by "Scott T. Weaver" <sc...@binary-designs.net>.
Correct MVC would say that would not need access to the service in the
JSP. However, you still might want to access the service from within a
servlet that has been delegated from the render() method.
David Sean Taylor wrote:
>
> On Jul 8, 2004, at 10:18 AM, David Le Strat wrote:
>
>>
>>> Yes, I see your point, although it leaves me
>>> wondering if the EG
>>> screwed up here.
>>> We don't have a well-defined way to get to the
>>> PortletContext from a
>>> JSP.
>>> A solution something like:
>>>
>>> renderRequest.getAttribute("cps:ServiceName");
>>
>>
>> This is the way the JSR exposes user attributes to the
>> JSP:
>> renderRequest.getAttribute(PortletRequest.USER_INFO)
>>
> Yes, Im aware of that ;-)
>
> Just wondering, why do we need the service in the JSP 'view' ?
> Are we correctly separating MVC here?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
--
******************************************
* Scott T. Weaver *
* <we...@apache.org> *
* <http://www.einnovation.com> *
* -------------------------------------- *
* Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container *
* *
* OpenEditPro, Website Content Mangement *
* <http://www.openeditpro.com> *
******************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Resolved: (JS2-70) Support Service definitions in Jetspeed extended portlet descriptor
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Jul 8, 2004, at 10:18 AM, David Le Strat wrote:
>
>> Yes, I see your point, although it leaves me
>> wondering if the EG
>> screwed up here.
>> We don't have a well-defined way to get to the
>> PortletContext from a
>> JSP.
>> A solution something like:
>>
>> renderRequest.getAttribute("cps:ServiceName");
>
> This is the way the JSR exposes user attributes to the
> JSP:
> renderRequest.getAttribute(PortletRequest.USER_INFO)
>
Yes, Im aware of that ;-)
Just wondering, why do we need the service in the JSP 'view' ?
Are we correctly separating MVC here?
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Resolved: (JS2-70) Support Service definitions in Jetspeed extended portlet descriptor
Posted by David Le Strat <dl...@yahoo.com>.
> Yes, I see your point, although it leaves me
> wondering if the EG
> screwed up here.
> We don't have a well-defined way to get to the
> PortletContext from a
> JSP.
> A solution something like:
>
> renderRequest.getAttribute("cps:ServiceName");
This is the way the JSR exposes user attributes to the
JSP:
renderRequest.getAttribute(PortletRequest.USER_INFO)
>
> I really preferred having it in the context, but I
> don't see a way to
> get to the context via the Portlet API in a JSP
>
> --
> David Sean Taylor
> Bluesunrise Software
> david@bluesunrise.com
> [office] +01 707 773-4646
> [mobile] +01 707 529 9194
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@jakarta.apache.org
>
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Resolved: (JS2-70) Support Service definitions in Jetspeed extended portlet descriptor
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Jul 8, 2004, at 4:44 AM, David Le Strat wrote:
> David,
>
> Thanks for the note. I started playing with this. I
> was just wondering. Struts and JSF do not have access
> to the PortletContext which requires an extra step in
> passing the service to let's say a Struts action.
> Would it make sense to make the service available from
> the request instead of the portlet context?
>
Yes, I see your point, although it leaves me wondering if the EG
screwed up here.
We don't have a well-defined way to get to the PortletContext from a
JSP.
A solution something like:
renderRequest.getAttribute("cps:ServiceName");
I really preferred having it in the context, but I don't see a way to
get to the context via the Portlet API in a JSP
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Resolved: (JS2-70) Support Service definitions in Jetspeed extended portlet descriptor
Posted by David Le Strat <dl...@yahoo.com>.
> I would also like to see us make the use of
> JetspeedPortletServices
> "portable" to other portals somehow. That way
> portlet applications
> using them aren't stuck in Jetspeed 2 and are fully
> JSR-168 compliant.
> I could see running the J2 engine with just the
> portlet services running
> and then use a servlet filter to add the services to
> the context (or
> whatever).
That would be nice indeed.
>
> David Le Strat wrote:
>
> >David,
> >
> >Thanks for the note. I started playing with this. I
> >was just wondering. Struts and JSF do not have
> access
> >to the PortletContext which requires an extra step
> in
> >passing the service to let's say a Struts action.
> >Would it make sense to make the service available
> from
> >the request instead of the portlet context?
> >
> >Regards,
> >
> >David.
> >
> >--- jetspeed-dev@jakarta.apache.org wrote:
> >
> >
> >>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:
> >>jetspeed-dev-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail:
> >>jetspeed-dev-help@jakarta.apache.org
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> >
> >__________________________________
> >Do you Yahoo!?
> >New and Improved Yahoo! Mail - 100MB free storage!
> >http://promotions.yahoo.com/new_mail
> >
>
>---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail:
> jetspeed-dev-help@jakarta.apache.org
> >
> >
> >
> >
>
>
> --
> ******************************************
> * Scott T. Weaver *
> * <we...@apache.org> *
> * <http://www.einnovation.com> *
> * -------------------------------------- *
> * Apache Jetspeed Enterprise Portal *
> * Apache Pluto Portlet Container *
> * *
> * OpenEditPro, Website Content Mangement *
> * <http://www.openeditpro.com> *
>
=== message truncated ===
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Resolved: (JS2-70) Support Service definitions in Jetspeed
extended portlet descriptor
Posted by "Scott T. Weaver" <sc...@binary-designs.net>.
I would also like to see us make the use of JetspeedPortletServices
"portable" to other portals somehow. That way portlet applications
using them aren't stuck in Jetspeed 2 and are fully JSR-168 compliant.
I could see running the J2 engine with just the portlet services running
and then use a servlet filter to add the services to the context (or
whatever).
David Le Strat wrote:
>David,
>
>Thanks for the note. I started playing with this. I
>was just wondering. Struts and JSF do not have access
>to the PortletContext which requires an extra step in
>passing the service to let's say a Struts action.
>Would it make sense to make the service available from
>the request instead of the portlet context?
>
>Regards,
>
>David.
>
>--- jetspeed-dev@jakarta.apache.org wrote:
>
>
>>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:
>>jetspeed-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail:
>>jetspeed-dev-help@jakarta.apache.org
>>
>>
>>
>>
>
>
>
>
>
>__________________________________
>Do you Yahoo!?
>New and Improved Yahoo! Mail - 100MB free storage!
>http://promotions.yahoo.com/new_mail
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
>
>
--
******************************************
* Scott T. Weaver *
* <we...@apache.org> *
* <http://www.einnovation.com> *
* -------------------------------------- *
* Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container *
* *
* OpenEditPro, Website Content Mangement *
* <http://www.openeditpro.com> *
******************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Resolved: (JS2-70) Support Service definitions in Jetspeed extended portlet descriptor
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Jul 8, 2004, at 6:02 AM, Scott T. Weaver wrote:
> How about the through the ServletContext instead?
>
Its a good possibility. Opens up services to working in servlets as
well as portlets
We have had the need for that now and then
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Resolved: (JS2-70) Support Service definitions in Jetspeed
extended portlet descriptor
Posted by "Scott T. Weaver" <sc...@binary-designs.net>.
How about the through the ServletContext instead?
Regards
--
******************************************
* Scott T. Weaver *
* <we...@apache.org> *
* <http://www.einnovation.com> *
* -------------------------------------- *
* Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container *
* *
* OpenEditPro, Website Content Mangement *
* <http://www.openeditpro.com> *
******************************************
David Le Strat wrote:
>David,
>
>Thanks for the note. I started playing with this. I
>was just wondering. Struts and JSF do not have access
>to the PortletContext which requires an extra step in
>passing the service to let's say a Struts action.
>Would it make sense to make the service available from
>the request instead of the portlet context?
>
>Regards,
>
>David.
>
>--- jetspeed-dev@jakarta.apache.org wrote:
>
>
>>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:
>>jetspeed-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail:
>>jetspeed-dev-help@jakarta.apache.org
>>
>>
>>
>>
>
>
>
>
>
>__________________________________
>Do you Yahoo!?
>New and Improved Yahoo! Mail - 100MB free storage!
>http://promotions.yahoo.com/new_mail
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [jira] Resolved: (JS2-70) Support Service definitions in Jetspeed extended portlet descriptor
Posted by David Le Strat <dl...@yahoo.com>.
David,
Thanks for the note. I started playing with this. I
was just wondering. Struts and JSF do not have access
to the PortletContext which requires an extra step in
passing the service to let's say a Struts action.
Would it make sense to make the service available from
the request instead of the portlet context?
Regards,
David.
--- jetspeed-dev@jakarta.apache.org wrote:
> 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:
> jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@jakarta.apache.org
>
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org