[RIVER-313] Provide mechanism to swap in alternatives to Java DSL for service configuration

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: River_3.0.0

Environment

All

• Assignee: Unassigned
• Reporter: Tom Hobbs
• Created: 15/Jul/09 16:50
• Updated: 05/Dec/15 11:15
• Resolved: 05/Dec/15 11:15

Description

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/[e-mail]%3e