Databases
StackOverflow2013
Postsdbo
POJava EE 6 - The Persistent Domain Objects pattern - any successes?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJava EE 6 - The Persistent Domain Objects pattern - any successes?
    primarykey
    data
    text
    <p>I have a moderately complex application using POJOs, and now come to migrated it to EJB3.1 so it can be deployed online, accessed through REST services and benefit from the container environment (persistence being the most major, but transactions would be useful too).</p> <p>I have been away from Java EE since the J2EE days, and am struggling to get my head around the "loss" of entity beans. It took me a while to realise that Entities in EJB3.1 are not actually Beans in the old sense... :) I have read a number of EJB3 books including the O'Reilly Enterprise JavaBeans 3.1 "manual", all of which explain the concepts and components of EJB3 but not the implementation pattern options.</p> <p>In my research and investigation looking for Java EE 6 patterns I'm rather taken by Adam Bien's approach - particularly the "Persistent Domain Objects" (PDO) pattern (in his book but summarised here too: <a href="http://download.java.net/general/podcasts/real_world_java_ee_patterns.pdf" rel="noreferrer">http://download.java.net/general/podcasts/real_world_java_ee_patterns.pdf</a>), which appears to offer the least complexity and most synergy with my current POJO app. PDO also closely-aligns with the traditional Object Oriented philosophies and approach, and really appeals to me.</p> <p>Rather than resparking a debate over PDO, I'm interested to hear from people that have implemented it and what worked vs. where you had difficulties. In particular I'd like to find out how you made calls <strong>from</strong> JPA entities out into other services in the container (like calls to stateless session beans etc).</p> <p>I'd also love to know if there are alternatives to the PDO pattern that allow me to maintain the application structure (using polymorphism etc) without having to create a session bean and a JPA entity for every class in my model. (I don't want to do that partly because of the massive exercise required to refactor all of the unit and integration tests, and partly because - as far as I can see - I'll end up trying to replicate my 1toMany etc object relationship across my session beans too which seems crazy). </p> <p>Does anyone have any experiences to share - or if you'd like to point out I'm an idiot and have missed something fundamental in Java EE 6 that would be "welcome" too :)</p> <p>TIA</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USuser1180316
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJava EE 6 - The Persistent Domain Objects pattern - any successes?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJava EE 6 - The Persistent Domain Objects pattern - any successes?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POJava EE 6 - The Persistent Domain Objects pattern - any successes?
      1. USChristopher Poile
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload