[ http://issues.apache.org/jira/browse/PB-46?page=all ]
Ate Douma resolved PB-46.
-------------------------
Resolution: Fixed
As reported by Scott the fixes solved his issues.
> FilterPortlet cannot be used with ServletContextProvider because it doesn't
> extend GenericPortlet
> -------------------------------------------------------------------------------------------------
>
> Key: PB-46
> URL: http://issues.apache.org/jira/browse/PB-46
> Project: Portals Bridges
> Issue Type: Bug
> Components: portletfilter
> Affects Versions: 1.0
> Reporter: Ate Douma
> Assigned To: Ate Douma
> Fix For: 1.0.1
>
>
> Scott Anderson reported the following on the bridges-user mailing list:
> <quote>
> I was hoping to use the ServletContextProvider interface for obtaining the
> ServletContext, ServletRequest, & ServletResponse given a FilterPortlet
> implementation. Unfortunately, the ServletContextProvider requires that it be
> provided a GenericPortlet which FilterPortlet is not. I am going to go ahead
> and roll my own FilterPortlet that is a subclass of GenericPortlet but I
> thought I'd note this inconsistency so that this problem can hopefully be
> resolved in a subsequent release of Portals Bridges.
> Scott
> </quote>
> After checking the current implementation of FilterPortlet which only
> implements the Portlet and PortletConfig interfaces (just as GenericPortlet),
> I think simply extending GenericPortlet will do the trick and should have no
> unexpected side-effects.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
