Allow for extension blacklists
------------------------------
Key: GEOS-3691
URL: http://jira.codehaus.org/browse/GEOS-3691
Project: GeoServer
Issue Type: Improvement
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 2.0.1
From the mailing list:
Current we have, in various parts of the codebase, code
that looks up for specific extension point implementors
by using GeoServerExtensions.xxx
The mechanism makes it easy to add another extension
implementor, just declare it in the Spring context,
drop in a new jar, voilà.
But what if someone wants to disable an extension point
instead, say, disable a core output format or a core
store?
At the moment there is no way. We need an extension
point to break other extension points! Ha!
What about:
ExtensionFilter {
boolean accept(String beanId, Object extension);
}
This should allow to plug into the Spring context
filters either filters that know about the bean id
the need to mask, something like:
{code:xml}
<bean id="hideCSV" class="org.geoserver.platform.ExtensionHider">
<property name="beanId" value="CSVOutputFormat">
</bean>
{code}
that could be also provided as (both are useful):
{code:xml}
<bean id="hideCSV" class="org.geoserver.platform.ExtensionHider">
<property name="beanClass"
value="org.geoserver.wfs.response.CSVOutputFormat">
</bean>
{code}
But then again someone could also implement a filter that is
configuration aware and that can be used to hide extension
points that the administrator explicitly disabled from the
GUI (think of a panel allows to configure what output formats you want).
Opinions?
Cheers
Andrea
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira