[ http://issues.apache.org/jira/browse/IBATIS-20?page=history ]
Clinton Begin updated IBATIS-20:
--------------------------------
Priority: Minor (was: Major)
I'm reducing the priority of this issue. I'm guessing that we'll stop support
for 1.x, as it's been over a year taht 2.0 has been out. At the very least,
all projects should convert to the new XML document format, even if you still
use the 1.x API.
> 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
> 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
