- Forget about OO, DSLs, encapsulation, think in structs. Try to as frictionless as possible export/generate the JPA-entities from the existing database. It works perfectly with Netbeans (context menu -> new entity classes from database), or Eclipse Dali.
- Implement a very thin facade / transaction boundary. Currently the simplest possible way is a @Stateless Bean (EJB 3).
- Write rudimentary integration tests with e.g. Junit. Purpose: JPA mapping verification.
- Execute the "Unit" tests after every change.
- Implement and perform load / stress tests.
- If your database will remain the "master", go to 1 on every DB schema change. If it is worth to invest in real objects, then:
- Rename the classes into some more meaningful. The attribute, class names are in general everything but not fluent. Goto 4. This change will break the JPA queries.
- Rename the getters / setters - even better get rid of them (this should not break the queries, unless you are working with property based access which is not recommended). Goto 4.
- Goto 5.
- If the JPA entities still do not look right, try to apply some JPA tricks like mapping a JPA-entity to several tables, or even map JPA-entities to DB-views, to improve the situation. Goto 4.
- Goto 5. Compare the results with 9.
- Remember everything what you forgot in 1 again. Now your domain objects are semi-objectoriented. You could even start with OO-modelling.
Disclaimer: The gotos are actually gosubs (for ZX Spectrum / C64 geeks :-))
[Rich and anemic domain objects are discussed in-depth in the "Real World Java EE Patterns" book. See e.g. page 83 and 259]
Cloudy Jakarta EE and MicroProfile: Microservices, Clouds and Beyond Jakarta EE / MicroProfile airhacks workshops at MUC airport, Winter Edition
airhacks.fm the podcast:
Stay in touch: airhacks.news.