[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2095) Document Multiple DataSources in same with example

[Pete Muir (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?

> Document Multiple DataSources in same with example
> --------------------------------------------------
>
>                 Key: JBSEAM-2095
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2095
>             Project: JBoss Seam
>          Issue Type: Patch
>          Components: Core
>    Affects Versions: 2.0.0.CR1
>         Environment: EAR deployment, POJO beans setup by Seam-Gen. OS not relevant; tried JDK1.6 and 1.7EA. DB is PostgreSQL 8.
>            Reporter: Ian Darwin
>         Attachments: multiple_datasources.xml
>
>
> 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.

-- 
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