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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
******************************************
* Scott T. Weaver *
* <[EMAIL PROTECTED]> *
* <http://www.einnovation.com> *
* -------------------------------------- *
* Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container *
* *
* OpenEditPro, Website Content Mangement *
* <http://www.openeditpro.com> *
******************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
