conflict with ServletContextProvider & FilterPortlet

[Scott Anderson <po...@gmail.com>]

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

Re: conflict with ServletContextProvider & FilterPortlet

[Shinsuke SUGAYA <sh...@yahoo.co.jp>]

Scott Anderson wrote:
> 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.

As you may know if you checked FilterPortlet, it's JSR 168 compliant and
a very simple API! Therefore, IMO, FilterPortlet should keep simplicity
(actually, I do not want additonal dependencies..). So, to support it in
Portlet Filter project, I think that it's better to add extended FilterPortlet
to Portlet Filter release.

Thanks,
  shinsuke

> 
> Scott
> 

--------------------------------------
[10th Anniversary] special auction campaign now!
http://pr.mail.yahoo.co.jp/auction/

---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-user-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-user-help@portals.apache.org