Hi Craig, Thanks very much for helps!
We used an earlier version of Pluto, if we modify PortletRequestImpl.getAttributeNames suitably (taking care decoding logic) but nothing else, is there any side effect (roughly)? Best regards, Lisheng -----Original Message----- From: Craig Doremus [mailto:[EMAIL PROTECTED] Sent: Thursday, August 02, 2007 2:48 PM To: [email protected] Subject: Re: Behavior of getAttributeNames() ? This was fixed in PLUTO-369, which is part of the 1.1.4 release. /Craig Zhang, Lisheng wrote: > Hi, > > I have been using pluto for some time, JSR168 spec PLT 16.3.2 > required when PortletRequestDispatcher dispatches to a servlet, > the included servlet or JSP must have > > javax.portlet.config javax.portlet.PortletConfig > > when calling HttpServletRequest.getAttribute, this indeed work, but > client complained that > > HttpServletRequest.getAttributeNames() > > did not have "javax.portlet.config" and other javax.portlet.*, looking > at pluto source code (PortletRequestImpl.java), this looks like a > delibrate decision. > > My question is: does pluto decide HttpServletRequest.getAttributeNames() > NOT to return "javax.portlet.config" and others although getAttribute > method can indeed fetch them? Is there any change in this decision > between different versions of pluto? > > Thanks very much for helps and best regards, > > Lisheng Zhang > Software developer, BroadVision Inc. > > > > >
