StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POJPA (Hibernate) + Tomcat + two different databases
primarykey
Id
14761706
data
AcceptedAnswerId
14781600
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-07T21:52:35.587
FavoriteCount
0
LastActivityDate
2013-02-12T20:30:54.713
LastEditDate
2013-02-09T16:03:55.217
LastEditorUserId
1483447
OwnerUserId
1483447
ParentId
0
PostTypeId
1
Score
0
ViewCount
955
LastEditorDisplayName
text
Body
I have a webapp using JPA provided by Hibernate and Tomcat. I have no DI framework, no Spring, no Guice, no full Java EE app server. I need JPA to connect to two different databases. I connect to the first database like this: <pre><code>EntityManagerFactory emf = Persistence.createEntityManagerFactory("mydb"); [...] EntityManager em = emf.createEntityManager(); </code></pre> and I have the "mydb" persistence unit declared in persistence.xml and linked through JNDI to its resource declared in context.xml. Till here everithing works. Now I need to connect to another database. I've added it to persistence.xml and context.xml and named the persistence unit "mydb2". Now I assume I can use it like this: <pre><code>EntityManagerFactory emf2 = Persistence.createEntityManagerFactory("mydb2"); EntityManager em2 = emf2.createEntityManager(); </code></pre> Hibernate is configured to validate classes and tables on both databases with <pre><code><property name="hibernate.archive.autodetection" value="class, hbm"/> <property name="hibernate.hbm2ddl.auto" value="validate"/> </code></pre> in persistence.xml. However when I run/debug the webapp, Hibernate tries to validate @Entity classes that belong to mydb2 on mydb, and it obviously fails. Now the fun part is that if I set the Hibernate validation property to "none", my application does work correctly and connects to the correct db as needed... Is there a way to have Hibernate validate only the classes/tables belonging to their respective database? EDIT: While it's possible to specify a catalog name in @Table annotations, in my case it's not a good solution, because I have more than one instance of this webapp in production and each instance connects to a different pair of databases. Being forced to touch the source code just before going into production is bad.
Tags
<hibernate><java-ee><tomcat><hbm2ddl>
Title
JPA (Hibernate) + Tomcat + two different databases
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USLucio Crusca
UserOwnerUserId
1. USLucio Crusca
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
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.