On Thu, Oct 2, 2008 at 12:02 PM, Scott O'Bryan <[EMAIL PROTECTED]> wrote:
> Hey Leonardo, it looks like the JSR-301 is going to moving this to be a > PortletContext object instead of a PortletConfig. It's a pretty trivial > change to the spec so I'm expecting it to happen before the final vote. > > Just FYI.. > Ok, thanks. I'll keep tuned. > > Scott > > > Leonardo Uribe (JIRA) wrote: > >> [ >> https://issues.apache.org/jira/browse/TOMAHAWK-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] >> >> Leonardo Uribe resolved TOMAHAWK-896. >> ------------------------------------- >> >> Resolution: Fixed >> Fix Version/s: 1.1.8-SNAPSHOT >> Assignee: Leonardo Uribe >> >> this was fixed as part of TOMAHAWK-33 >> >> >> >>> Casts to HttpServletRequest in Portlets >>> --------------------------------------- >>> >>> Key: TOMAHAWK-896 >>> URL: https://issues.apache.org/jira/browse/TOMAHAWK-896 >>> Project: MyFaces Tomahawk >>> Issue Type: Improvement >>> Components: Portlet_Support >>> Affects Versions: 1.1.5-SNAPSHOT >>> Environment: JSR-168 Portlets >>> Reporter: Stephan Strittmatter >>> Assignee: Leonardo Uribe >>> Fix For: 1.1.8-SNAPSHOT >>> >>> >>> In many sources are casts to HttpServletRequest-Objects, which are not >>> available in Portal-Environments. >>> These should be replaced to be more JSR-168 conform. >>> I think there should also be a check for this issue by Checkstyle e.g. >>> for this to prevent more errors like this. >>> One example is in: >>> org.apache.myfaces.custom.dojo.DojoUtils.isInlineScriptSet() >>> >>> >> >> >> > >
