[ http://jira.jboss.com/jira/browse/JBSEAM-2095?page=all ] Ian Darwin reopened JBSEAM-2095: -------------------------------- Changing to a Documentation Request, and attaching the documentation I previously promised to write. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2095?page=all ] Ian Darwin updated JBSEAM-2095: ------------------------------- Summary: Document Multiple DataSources in same with example (was: Multiple DataSources in same EAR, hib2ddl and import.sql run on all) Issue Type: Patch (was: Feature Request) Description: When using multiple DataSources in an EJB3 EAR, as suggested by Gavin the the URL referenced below, using Hibernate as the underlying persistence, it appears that the "schema export" and the /import.sql get applied to both. The workaround is to be sure you only use hbm2ddl auto on one of the datasources. The attachment gives an example. was: When using multiple DataSources in an EJB3 EAR, as suggested by Gavin the the URL referenced below, using Hibernate as the underlying persistence, it appears that the "schema export" and the /import.sql get applied to both. It would be nice if there could be a more fine-grained mechanism for associating import.sql and hbm2ddl with particular entities. I have two Datasources, call them "all" and "bugs" (the idea being that the bugs database will be shared by all developers and should be permanent, whereas the "all" database should be dropped and recreated/imported each tim). 16:07:55,345 INFO [SchemaExport] Running hbm2ddl schema export 16:07:55,345 INFO [SchemaExport] exporting generated schema to database 16:07:55,504 INFO [SchemaExport] Executing import script: /import.sql 16:07:55,568 INFO [SchemaExport] schema export complete ... 16:07:55,710 INFO [SchemaExport] Running hbm2ddl schema export 16:07:55,711 INFO [SchemaExport] exporting generated schema to database 16:07:55,857 INFO [SchemaExport] Executing import script: /import.sql 16:07:55,911 INFO [SchemaExport] schema export complete It would be most convenient if one could specify more precisely which entities go in which Schema. I have added the @PersistenceContext annotation on the BugsHome class' EntityManager: @PersistenceUnit(name="tcpseambug") @In EntityManager bugEntityManager; public EntityManager getEntityManager() { return bugEntityManager; } Note that if I disable the hbm2ddl export on the "bugs" database, then schema setup quits when one of the tables in the "all" database shows up missing. N.B. Will be happy to write up a complete example for the Reference Manual once this is working :-), as there are several related questions on the Forums. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2095?page=comments#action_12382301 ] Pete Muir commented on JBSEAM-2095: ----------------------------------- Thanks for the docs, but anything of this type needs to go into Hibernate docs NOT Seam docs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2095?page=comments#action_12382502 ] Pete Muir commented on JBSEAM-2095: ----------------------------------- N.B. everything except the last two paragraphs are non-Seam specific and in fact are JPA (persistence.xml) and JBoss AS (-ds.xml) specific. Putting @PersistenceContext @In EntityManager entityManager is almost certainly invalid and non-portable. I actively think it should not go in the docs: the content is incorrect, its not a patch, its not written in a consistent style with the rest of the docs, and its a corner case. Hence I rejected the issue. Why not write a tutorial on a blog linked off the Seam wiki? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2095?page=all ] Norman Richards updated JBSEAM-2095: ------------------------------------ Attachment: (was: multiple_datasources.xml) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira