The Rocoto use cases are short and sweet... easy configuration via @Named
injections and system properties. We use this to great effect building a
plugin system for vendor integrations. Something like this:
public class MyVendorModule extends PrivateModule {
@Override
protected void configure() {
* install(new ConfigurationModule()*
* .addConfigurationReader(new PropertiesReader(getProperties())));*
Multibinder.newSetBinder(binder(),
VendorHandler.class).addBinding().to(MyIntegration.class);
}
@Override
protected Properties getProperties() {
Properties props = super.getProperties();
* props.setProperty("my-integration.handler.url.resolved",*
* "${my-integration.handler.url|http://my.integration.com
<http://my.integration.com>}");*
return props;
}
}
public class MyIntegration extends VendorHandler {
private static final String HANDLER_URL_SUFFIX = ".handler.url.resolved";
@Inject
* public Doer(@Named("my-integration" + HANDLER_URL_SUFFIX) String url) {*
// ...
}
}
On Mon, Aug 18, 2014 at 9:58 AM, nino martinez wael <
nino.martinez.w...@gmail.com> wrote:
> Hey im going to apache conf this year and thought it was a great place to
> give a talk.. however it was not accepted. Instead the opportunity of a
> lightning talk remains. I'm thinking that the talk should be like a desert
> short and sweet. So give them a short overview. And some of the sweet
> simple stuff, like how simple it is scheduling or some of the life cycle or
> [insert your suggestions here].. I'll take a look at all the projects, and
> grab what's simple..
>
> Any feedback ideas are very welcome..
>
> Any other going ?
>
> Regards Nino
>
--
Cody A. Ray, LEED AP
cody.a....@gmail.com
215.501.7891
