You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Peter Firmstone (JIRA)" <ji...@apache.org> on 2015/12/05 12:16:11 UTC
[jira] [Resolved] (RIVER-313) Provide mechanism to swap in
alternatives to Java DSL for service configuration
[ https://issues.apache.org/jira/browse/RIVER-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone resolved RIVER-313.
-----------------------------------
Resolution: Fixed
Fix Version/s: River_3.0.0
Groovy configuration has been integrated by Dennis.
> Provide mechanism to swap in alternatives to Java DSL for service configuration
> -------------------------------------------------------------------------------
>
> Key: RIVER-313
> URL: https://issues.apache.org/jira/browse/RIVER-313
> Project: River
> Issue Type: New Feature
> Environment: All
> Reporter: Tom Hobbs
> Fix For: River_3.0.0
>
> Attachments: Component.java, GroovyConfig.groovy
>
>
> There has been some talk on the dev mailing list about providing alternative or additional methods of describing service configurations, rather than the stock Java DSL currently in use. This might include;
> - XML descriptions
> - Groovy classes
> - Scala classes
> - Other
> The Configuration mechanism could be extended to allow services to accept any kind of configuration (as identified above) and used in conjunction with any other type of configuration.
> See message at following link for the pointer to the thread;
> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200907.mbox/%3cE099BB07-376A-4357-9920-7D2C77F57927@gmail.com%3e
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)