You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Clinton Begin (JIRA)" <ib...@incubator.apache.org> on 2005/02/12 23:04:13 UTC
[jira] Closed: (IBATIS-20) upgrading from old version defaults to wrong TransactionManager
[ http://issues.apache.org/jira/browse/IBATIS-20?page=history ]
Clinton Begin closed IBATIS-20:
-------------------------------
Assign To: Clinton Begin
Resolution: Won't Fix
Upgrading is a one shot deal. This is such an isolated case and a low priority, I don't see it causing most people any trouble. Everyone should be moving to 2.0, at least in terms of the XML files (i.e. use the 1.x Java API with 2.x files). You can tweak the config file by hand after the conversion.
> upgrading from old version defaults to wrong TransactionManager
> ----------------------------------------------------------------
>
> Key: IBATIS-20
> URL: http://issues.apache.org/jira/browse/IBATIS-20
> Project: iBatis for Java
> Type: Bug
> Environment: jboss 3.2.1, iBatis 2.0.8 (upgraded from iBatis 1.2.9)
> Reporter: alex mccarrier
> Assignee: Clinton Begin
> Priority: Minor
>
> We are using EJB to demarcate transactions. Old iBatis sql config file contained this:
> <settings useGlobalTransactions="true"
> cacheModelsEnabled="true" />
> <datasource name="snmDataSource"
> factory-class="com.ibatis.db.sqlmap.datasource.JndiDataSourceFactory"
> default="true" >
> <property name="DBFullJndiContext" value="java:/DataSource" />
> </datasource>
> Which configured iBatis to use external global transaction management, which from the documentation I understand this to be the default unless I specify to use Managed Global Transactions by including settings attribute called "userTransactionJndiName" (iBatis 1.2.9 manual, pp 39-40).
> When iBatis 2.0.8 tries to do the conversion, it defaults to Managed Global Transactions, then throws a ClassCastException because it can't find a UserTransaction object at jndi name "" (because there is none specified).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira