Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

A Groovy world: why framework configuration APIs matter

DZone's Guide to

A Groovy world: why framework configuration APIs matter

· Java Zone
Free Resource

Build vs Buy a Data Quality Solution: Which is Best for You? Gain insights on a hybrid approach. Download white paper now!

Somebody is writing the next big framework as you're reading. It could be a new OR mapper, a new web framework, a build system or a dependency injection container.

Regardless of what this framework is designed for one thing will determine the level of integration it will get with Groovy and/or Grails: its configuration API.

Here's a list of frameworks that made it into the Groovy and/or Grails and rocked our world, thanks to their configuration APIs. People wrote builders for them or otherwise have integrated them in ways that could not have been foreseen nor were intended by their creators.

They are:

Some notable frameworks that only have a limited integration with Grails simply because their creators did not provide a convenient, reusable configuration API:

Just imagine the power of being able to construct a view in Grails with just a few lines of Groovy code.

If you're working on this next generation frameworks, think of us Groovy developers and please abstract your configuration so that we can reuse your work.

Thanks and happy coding!

Build vs Buy a Data Quality Solution: Which is Best for You? Maintaining high quality data is essential for operational efficiency, meaningful analytics and good long-term customer relationships. But, when dealing with multiple sources of data, data quality becomes complex, so you need to know when you should build a custom data quality tools effort over canned solutions. Download our whitepaper for more insights into a hybrid approach.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}