You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/05/22 02:11:16 UTC

[jira] Closed: (GERONIMO-3179) Allow specifying default datasources for legacy cmp

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

David Jencks closed GERONIMO-3179.
----------------------------------

    Resolution: Fixed

Fixed in rev 540376.

Dain, what do you think about allowing explicit setting of non-jta datasource in the openejb plan somewhere?

> Allow specifying default datasources for legacy cmp
> ---------------------------------------------------
>
>                 Key: GERONIMO-3179
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3179
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: persistence
>    Affects Versions: 2.0-M6
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 2.0-M6
>
>
> The JTA datasource is set from plan xml, but openjpa needs a non-jta datasource for its sequences to work with derby.  If we allow setting default datasource names on the openejb module builder, at least there will be some way to hook up the non-jta datasource to an appropriate database,  for at least one cmp module.
> Maybe we need to allow setting the non-jta ds as well in the individual app plan??

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