openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Closed: (OPENJPA-1749) Throw exception if using datacache / synchronize mappings and specifying datasource name at EM creation.
Date Wed, 28 Jul 2010 22:09:17 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Dick closed OPENJPA-1749.
---------------------------------

    Resolution: Fixed

> Throw exception if using datacache / synchronize mappings and specifying datasource name
at EM creation.
> --------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1749
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1749
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>             Fix For: 2.0.1, 2.1.0
>
>
> Some configuration options are misleading and dangerous if the datasource JNDI location
is provided at EntityManager creation time. For example the L2 cache can not be reliably used
if each EntityManager may be communicating with a different schema / database instance. 
> In order to prevent confusion down the road we should throw an exception when these conditions
are detected. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message