Skip to main content

Understanding Domain Classes

  • Chapter
The Definitive Guide to Grails
  • 351 Accesses

Abstract

Object-oriented (OO) applications almost always involve a domain model representing the business entities that the application deals with. Our gTunes application will include a number of domain classes including Artist, Album, and Song. Each of these domain classes has properties associated with it, and you must map those properties to a database in order to persist instances of those classes.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 46.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Scott W. Ambler,“The Object-Relational Impedance Mismatch,” http://www.agiledata.org/essays/ impedanceMismatch.html, 2006.

    Google Scholar 

  2. Wikipedia,“Optimistic concurrency control,” http://en.wikipedia.org/wiki/ Optimistic_concurrency_control.

    Google Scholar 

Download references

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2009 Graeme Rocher, Jeff Brown

About this chapter

Cite this chapter

Rocher, G., Brown, J. (2009). Understanding Domain Classes. In: The Definitive Guide to Grails. Apress. https://doi.org/10.1007/978-1-4302-0871-6_3

Download citation

Publish with us

Policies and ethics