You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/04/10 11:26:12 UTC
[jira] Closed: (PLUTO-551) Remove class loader from filter manager
interface
[ https://issues.apache.org/jira/browse/PLUTO-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed PLUTO-551.
----------------------------------
Resolution: Fixed
Removed the class loader from the interface in revision 763893.
> Remove class loader from filter manager interface
> -------------------------------------------------
>
> Key: PLUTO-551
> URL: https://issues.apache.org/jira/browse/PLUTO-551
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container
> Affects Versions: 2.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: 2.0.0
>
>
> Currently all methods of the FilterManager require a class loader
> instance for actually loading the filters.
> However this is an implementation detail and a portal might decide to
> already create the filters when the portlet webapp is started (and cache
> the filters). If the filter manager requires a class loader this should
> be handled like it is done in other services, the class loader should be
> passed into the implementation. The interface should not require a
> classloader.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.