struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lorenzo Bernacchioni (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WW-4410) Custom configuration providers accessing servlet-context
Date Fri, 03 Oct 2014 09:18:34 GMT

    [ https://issues.apache.org/jira/browse/WW-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157821#comment-14157821
] 

Lorenzo Bernacchioni commented on WW-4410:
------------------------------------------

I agree, the {{try...catch}} solution was just a hack, the new interface sounds good!
I didn't find clear references to the use of custom configuration providers, as far as I understand
they can be added via web.xml (described in my first comment, it should be mentioned [here|http://struts.apache.org/development/2.x/docs/webxml.html])
and programmatically via DispatcherListener (mentioned [here|http://struts.apache.org/release/2.1.x/docs/configuration-provider-configuration.html])



> Custom configuration providers accessing servlet-context
> --------------------------------------------------------
>
>                 Key: WW-4410
>                 URL: https://issues.apache.org/jira/browse/WW-4410
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Dispatch Filter
>    Affects Versions: 2.3.16.3
>            Reporter: Lorenzo Bernacchioni
>            Priority: Minor
>              Labels: configuration, custom, provider, servlet-context
>             Fix For: 2.3.x
>
>
> I'm using custom configuration providers following the suggestion of [this post|http://cppoon.wordpress.com/2013/11/11/change-apache-struts2-configuration-programmatically/comment-page-1/#comment-157].
> I figured out that my custom configuration provider needed access to the servlet-context
so I patched the code in the Dispatcher class to let, in case the constructor is available,
instantiate a ConfigurationProvider with the servlet-context as argument
> {code}
> private void init_CustomConfigurationProviders() {
> 	String configProvs = initParams.get("configProviders");
> 	if (configProvs != null) {
> 		String[] classes = configProvs.split("\\s*[,]\\s*");
> 		for (String cname : classes) {
> 			try {
> 				Class cls = ClassLoaderUtil.loadClass(cname, this.getClass());
> 				
> 				ConfigurationProvider prov;
> 				try {
> 					Constructor constructor = cls.getConstructor(ServletContext.class);
> 					prov = (ConfigurationProvider)constructor.newInstance(servletContext);
> 				} catch (Exception e) {
> 					prov = (ConfigurationProvider)cls.newInstance();	
> 				}
> 				configurationManager.addContainerProvider(prov);
> 			} catch (InstantiationException e) {
> 				throw new ConfigurationException("Unable to instantiate provider: "+cname, e);
> 			} catch (IllegalAccessException e) {
> 				throw new ConfigurationException("Unable to access provider: "+cname, e);
> 			} catch (ClassNotFoundException e) {
> 				throw new ConfigurationException("Unable to locate provider class: "+cname, e);
> 			}
> 		}
> 	}
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message