Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The same reason you'd use JNDI for anything, I'd say - moving the configuration out of the application, into the deployment environment.</p> <p>With JNDI, you basically say "this application needs a <code>SessionFactory</code>; and its name shall be X" and you're happy as long as the application server has a <code>SessionFactory</code> called X configured. This kind of externalization has several appealing benefits: </p> <ol> <li><p>You can use wildly different configurations on different machines (production and QA use Oracle, developers use HSQL, ...).</p></li> <li><p>You don't need to make your build process aware of configurations (no more <code>ant war_for_qa</code> or screwing around with Maven profiles).</p></li> <li><p>You're not tempted to check configurations into version control, and so your live database password won't be known to every temp, intern, consultant or ex-employee who's ever had (or will have!) access to the repository.</p></li> <li><p>Your installation/configuration instructions won't include items like "to configure the database login, edit the file foo.properties in the WAR file" which will inevitably result in configurations being overwritten on the production server at the worst possible moment because a sysadmin who's been working all weekend happened to deploy a non-edited WAR because the coffee ran out on Sunday afternoon.</p></li> </ol> <p>JNDI just happens to be the "standard" way of doing this externalization in Java, which means that new devs/admins won't need two days of training to learn the quirks of your own, home-brewn configuration system which really is quite clever but has this weird bug no one wants to delve into because it's <em>really</em> weird and anywho it has a pretty simple workaround, &amp;c.</p> <p><strong>Related:</strong> <a href="https://stackoverflow.com/questions/1350816/what-is-the-purpose-of-jndi">What is the purpose of JNDI?</a></p>
    singulars
    1. This table or related slice is empty.
    1. POWhy bind hibernate SessionFactory to a JNDI resource?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USgustafc
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy bind hibernate SessionFactory to a JNDI resource?
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@gustafc That was what I figured. I was just not sure if I was missing something else. We are using JNDI for our connection pool, so I guess I was wondering if there was an added benefit to moving the SessionFactory to the appserver as well. In our case I do not think there would be, since the configuration for it is exactly the same across all our servers. By the way, your answer is probably the best answer I have seen in a while as far as being very clear and informative.
      singulars
      1. PO
      1. USJacob Schoen
    2. COAm I right that the main purpose is to make it available across multiple applications deployed on the same server? If this is the case a big advantage is the shared 2nd level cache of the SF. Our SF resides within a `@Singleton` `@Startup` `@EJB` since we have only a single application deployed.
      singulars
      1. PO
      1. USdjmj
    3. CO@djmj, sounds feasible but I honestly don't know how app servers handle this, since I've never run into an app using an externally defined Hibernate/JPA setup - most apps seem to be deployed the way you describe. I can imagine it having implications on stability, security etc and therefore *not* use a shared 2nd level cache.
      singulars
      1. PO
      1. USgustafc
 

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