Getting Started with Grails
Jason Rudolph discusses Java/Grails integration, Grails plugins, creating a Grails sample application, Grails app structure, data querying and persistence, validation, controllers and tag libraries.
- Java,
Tracking change and innovation in the enterprise software development community
Posted by Jay Fields on May 08, 2008 06:44 PM
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
IBM Agile Development eKit: Free Articles, Expert Q&A, Educational Resources
Info 2.0: IBM's vision for the world of Web 2.0 and enterprise mashups (Webcast)
Fighter Jets and Agile Development at Lockheed Martin (Case study)
I enjoyed the presentation. Thanks!
Two related questions:
1. If I understand correctly, the system is not forcing the user to type syntactically-well formed string in some controlled grammar. Instead, the regexes do the magic under the hood. If so, does/could it happen that the business user naively uses a novel language construct (and instead of or, or a meaningful "not" or "could" instead of "does") which the BNL designer did not anticipate, but which get swept up in general regexes, and the meaning is harmed in some subtle way that may be hard for a business user to defend against using the testing tools available?
2. Given the narrowly targeted domain specificity of the language, a similarly targeted UI might work as well. for example:
Do you have insights as to which circumstances favor a UI vs BNL?
Thanks again!
compensate $ [number] per [enum: $1M-profit, deal] if
[enum: gross, recent_deals, all_deals] exceeds [number]
(where the stuff in square brackets is shorthand for the appropriate HTML form-tags)
Michael Niv.
Hi Michael,
Like almost everything in software: it depends. There are so many ways to translate external DSLs to executable code that it will depend on which solution you go with. If you have a strong security (or just general) concern you can use something such as TreeTop to create an entirely external DSL and pretty much entirely mitigate the risk. On the other hand, if you do something as simple as replace spaces with dots, then you are allowing for potential issues. Of course, those issues might be acceptable given timelines, trust, etc.
Using form elements instead of a DSL is a commonly discussed option. I think it generally depends on how dynamic the language is. For example, I always thought trying to create SQL statements with forms was dreadfully painful. I would go with forms when possible, but if things are dynamic, I would quickly start considering a language.
For example, my current project allows you to specify the following conditions:
Date Range is 5/10/99
Date Range is from 4/10/99 to 5/10/99
Profit is greater than X
Profit is less than X
Profit is X
Cost is greater than X
Cost is less than X
Cost is X
And, so on, for many different conditions. This is something dynamic enough that it's painful to do in forms.
I hope that's helpful, please shoot me another question if you want more info.
Cheers, Jay
Jason Rudolph discusses Java/Grails integration, Grails plugins, creating a Grails sample application, Grails app structure, data querying and persistence, validation, controllers and tag libraries.
The Scrum Product Owner role is powerful, valuable and challenging to implement. It brings healthier relationships between customers and developers, and competitive advantage - if you do it right.
Effective Java, Second Edition by Joshua Bloch is an updated version of the classic first edition, which won a 2001 Jolt Award. InfoQ asked Bloch questions about the areas that the new edition covers.
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
In this interview, Burton Group consultant Pete Lacey talks to Stefan Tilkov about his disillusionment with SOAP, his opinion on REST, and addresses some of the perceived shortcomings REST vs. WS-*.
Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.
Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar.
Deborah Hartmann interviewed Segundo Velasquez about his experience as customer with an Agile team during the initial phase of software design of a product.
2 comments
Reply