With spring you can externalize values like this in a properties file. You
can then use classpath loading of the properties file in your spring xml
which allows you to have a properties file in your jar that provides sane
defaults, and a properties file in the WEB-INF/classes folder that
overrides
hi,
its good to have privately modularized context for plugins, but how do we
inject the required variables from the component context after building the
jars in 4.3 ?
in 4.2 i used to inject the required params for my plugin from the
componentcontext.xml after building the jars. so that params va
Hey Matt,
Your correct in seeing that some improvements were made in 4.3 to
support more modularized plugins. This wiki page and its two child
pages should help you get started:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Modularize+Spring
You no longer NEED to put your commands in the
In version 4.2 and below to get a plugin to work, I was adding a dependency in
the pom.xml of the Client project and modifying applicationContext.xml.inand
commands.properties.in. 4.3 appears to have introduces discoverable plugins.
What needs to be done differently in order to take advantage of
