You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2007/07/06 20:07:04 UTC

[jira] Created: (OPENJPA-279) Missing lookup for non-jta-data-source in JDBCConfigurationImpl.

Missing lookup for non-jta-data-source in JDBCConfigurationImpl.
----------------------------------------------------------------

                 Key: OPENJPA-279
                 URL: https://issues.apache.org/jira/browse/OPENJPA-279
             Project: OpenJPA
          Issue Type: Sub-task
    Affects Versions: 0.9.7
            Reporter: Michael Dick
            Assignee: Michael Dick
             Fix For: 1.0.0


This looks similar to the problem reported in OPENJPA-144, but since that has been resolved I'm opening a new sub-task.

When JDBCConfigurationImpl obtains a second connection (often used to get sequence values) it only checks the Connection2 properties. It doesn't lookup a non-jta-data-source if one is specified in persistence.xml. 

The lookup is done for jta-datasources but not for their non-jta counterparts. 



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

[jira] Closed: (OPENJPA-279) Missing lookup for non-jta-data-source in JDBCConfigurationImpl.

Posted by "Michael Dick (JIRA)" <ji...@apache.org>.

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

Michael Dick closed OPENJPA-279.
--------------------------------

    Resolution: Fixed

> Missing lookup for non-jta-data-source in JDBCConfigurationImpl.
> ----------------------------------------------------------------
>
>                 Key: OPENJPA-279
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-279
>             Project: OpenJPA
>          Issue Type: Sub-task
>    Affects Versions: 0.9.7
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>             Fix For: 1.0.0
>
>
> This looks similar to the problem reported in OPENJPA-144, but since that has been resolved I'm opening a new sub-task.
> When JDBCConfigurationImpl obtains a second connection (often used to get sequence values) it only checks the Connection2 properties. It doesn't lookup a non-jta-data-source if one is specified in persistence.xml. 
> The lookup is done for jta-datasources but not for their non-jta counterparts. 

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