Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>because I came from Spring, I believe DAO still has its value, so I decided to add a DAO layer.</p> </blockquote> <p>I don't really see what Spring has to do with this. And I don't agree <a href="https://stackoverflow.com/questions/2100115/i-found-jpa-or-alike-dont-encourage-dao-pattern/2100319#2100319">as I wrote in a previous answer</a>. To me, JPA is a DAL (data access layer), and I don't see the point of putting a data access layer on top of another data access layer. At least not systematically. But let's not discuss this.</p> <blockquote> <p>This is a JPA-implemented DAO , I hope the EE container or the test container able to inject the EntityManager (just like Spring does).</p> </blockquote> <p>If your DAO is a managed component like a CDI managed bean, then the Java EE container should be able to inject an <code>EntityManager</code> in it. </p> <p>For <strong>unit testing</strong> of container-managed objects, you don't need any kind of container. For <strong>integration testing</strong>, you will need some kind of container, just like you do for Spring beans, Hibernate/JPA entities, session beans, CDI managed beans or any other kind of container-managed object. You could <a href="http://www.adam-bien.com/roller/abien/entry/embedding_ejb_3_1_container" rel="nofollow noreferrer">use the EJB3.1 embeddable API in your tests</a>. Also have a look at <a href="http://community.jboss.org/docs/DOC-14376?uniqueTitle=false" rel="nofollow noreferrer">Arquillian</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to test a DAO with JPA implementation?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPascal Thivent
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to test a DAO with JPA implementation?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COAs to whether JPA has killed the DAO, it depends. At some points you would like to refactor the JPA code somewhere so that you can reuse it someplace else. What is then a better place than a DAO?
      singulars
      1. PO
      1. USBalusC
    2. CO@BalusC I don't agree with "use DAO systematically", I agree with "it depends" though... but not exactly for the reason you gave (I'm not saying you're wrong but I'd like to see a concrete illustration of your example, I have some difficulties at visualizing it).
      singulars
      1. PO
      1. USPascal Thivent
    3. CONone yet, I haven't used JPA in real world projects yet, just hobbying it. But I can imagine that whenever you need to repeat the same bunch of JPA code lines, you'd like to refactor that away if it grows over 3~5 lines of code or so, and I yet can't imagine the "right" place to put those lines in. Is it a DAO class?
      singulars
      1. PO
      1. USBalusC
 

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