BIRT 3.7
Written by: Michael Williams
Featured Refcardz: Top Refcardz:
  1. Scrum
  2. Apache Maven 2
  3. Essential MySQL
  4. Node.js
  5. Groovy
  1. jQuery Selectors
  2. Ajax
  3. Java
  4. Spring Config.
  5. Java Concurrency

Link Details

Link 379881 thumbnail
User 452305 avatar

By fifthposition
via fbflex.wordpress.com
Published: Mar 16 2010 / 06:43

One of the biggest challenges in developing web applications is the ability to alter the behaviour of your program once the application has been deployed. If you are building a highly extensible application like a content management system or an e-commerce engine, you don’t necessarily want to restart or redeploy every time a change has been made. You also want the ability to define business rules, add custom scripts, and turn functionality on and off. In this post, I [Tomás Lin] will show you how to externalize application functionality using closures, the Groovy configSlurper and the pluggable behaviour pattern.
  • 12
  • 0
  • 2199
  • 1

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.