RE: JIRA Permissions (was Re: [jira] Created: (PLUTO-80) request attributescannot be share d between actionRequest and renderRequest)

[Carsten Ziegeler <cz...@apache.org>]

Hi, sure :)
 
you currently seem to have two accounts in Jira: nicklothian and nlothian.
Which one should I add?

Carsten

> -----Original Message-----
> From: Nick Lothian [mailto:nick.lothian@essential.com.au] 
> Sent: Friday, October 29, 2004 2:27 AM
> To: 'pluto-dev@portals.apache.org'
> Subject: RE: JIRA Permissions (was Re: [jira] Created: 
> (PLUTO-80) request attributescannot be share d between 
> actionRequest and renderRequest)
> 
> Carsten, can you fix this for me?
> 
> Nick
> 
> > -----Original Message-----
> > From: David H. DeWolf [mailto:ddewolf@apache.org]
> > Sent: Friday, 29 October 2004 9:20 AM
> > To: pluto-dev@portals.apache.org
> > Subject: JIRA Permissions (was Re: [jira] Created: 
> (PLUTO-80) request 
> > attributescannot be share d between actionRequest and renderRequest)
> > Importance: Low
> > 
> > 
> > Nick,
> > 
> > I had to request permissions when I first started working 
> tickets, so 
> > my guess is that you're just not setup yet.  Carsten was 
> the one that 
> > was able to hook me up. It looks like he and I are 
> currently the only 
> > ones setup in JIRA as Pluto Developers.
> > 
> > I've dug around and don't think that I have access to add 
> you to the 
> > project, though I do have access to administer other aspects of the 
> > project (components, versions, etc. . .).
> > 
> > David
> > 
> > 
> > 
> > Nick Lothian wrote:
> > > I've commented this and I'd like to close it.
> > > 
> > > Do I need special rights to be able to change the status of
> > this issue? If
> > > someone knows how to assign them, can "nicklothian" please
> > get the required
> > > permissions.
> > > 
> > > Thanks
> > >  Nick
> > > 
> > > 
> > >>-----Original Message-----
> > >>From: Bogdan Onoiu (JIRA) [mailto:pluto-dev@jakarta.apache.org]
> > >>Sent: Wednesday, 27 October 2004 12:30 AM
> > >>To: pluto-dev@jakarta.apache.org
> > >>Subject: [jira] Created: (PLUTO-80) request attributes cannot be 
> > >>shared between actionRequest and renderRequest
> > >>Importance: Low
> > >>
> > >>
> > >>request attributes cannot be shared between actionRequest and 
> > >>renderRequest
> > >>--------------------------------------------------------------
> > >>-------------
> > >>
> > >>         Key: PLUTO-80
> > >>         URL: http://issues.apache.org/jira/browse/PLUTO-80
> > >>     Project: Pluto
> > >>        Type: Bug
> > >>  Components: portlet container  
> > >>    Versions: Current CVS    
> > >> Environment: Windows 2000 / Tomcat 4.1.30 / JDK 1.3.1_02-b02
> > >>    Reporter: Bogdan Onoiu
> > >>
> > >>
> > >>The specs say:
> > >>"Request attributes are objects associated with a portlet 
> during a 
> > >>single portlet request.
> > >>Request attributes may be set by the portlet or the portlet 
> > >>container to express information that otherwise could not be 
> > >>expressed via the API. Request attributes can be used to share 
> > >>information with a servlet or JSP being included via the 
> > >>PortletRequestDispatcher."
> > >>
> > >>Does this mean that we cannot share objects between action and 
> > >>render via set/getAttribute methods?
> > >>To reproduce the issue I describe check that in the testsuite the 
> > >>TestPortlet class sets:
> > >>request.setAttribute("portletaction","action1") in the end of the 
> > >>processAction(). If you try to get the value of "portletaction" 
> > >>attribute in the following render() method you get null.
> > >>
> > >>This is due to the fact that the pluto container is 
> always issuing a 
> > >>client side redirect after finishing the
> > >>processAction() therefor the original request response 
> objects are 
> > >>lost and new ones are created for render() processing.
> > >>in PortletContainerImpl
> > >>
> > >>try{
> > >>redirect(location, portletWindow, servletRequest, 
> servletResponse, 
> > >>_actionResponse); } finally{
> > >>PortletInvokerAccess.releasePortletInvoker(invoker);          
> > >>                  
> > >>PortletContainerServices.release();
> > >>}
> > >>generates a status 302 in the end.
> > >>
> > >>Can you specify if this is an implementation issue? If the object 
> > >>sharing is not ensured by the specs the whole design of a portlet 
> > >>application gets very complicated only to address this minor 
> > >>problem. The whole point of having the "processAction" 
> > >>specialization becomes cumbersome to be used when it 
> could actually 
> > >>be straight forward.
> > >>Ideally the specs would have allowed setting attibutes to request 
> > >>object in the same way as to the session object, eg:
> > >>allowing portlet scope and application scope.
> > >>
> > >>Cheers,
> > >>Bogdan
> > >>
> > >>--
> > >>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
> > >>
> > > 
> > > 
> > 
>