Having examined the DTD, it's actually illegal, but not enforced.
I have tried something new where I wrap each of the txMgr nodes in their own context, but
without specifying their IDs...That's not working so hot either under transaction management.
Oh well,
-D
-----Original Message-----
From: Niels Beekman [mailto:n.beekman@wis.nl]
Sent: Thursday, March 01, 2007 4:33 PM
To: user-java@ibatis.apache.org
Subject: RE: Simple question...
Hi,
I'm leaning towards the "no-way-in-the-world-would-this-work
configuration" :) I think you should specify only one transactionManager
element and include all SqlMaps from there. See the developers guide
(from the website) for some samples.
Niels
-----Original Message-----
From: Dave Rodenbaugh [mailto:drodenbaugh@WILDBLUECORP.COM]
Sent: donderdag 1 maart 2007 18:57
To: user-java@ibatis.apache.org
Subject: Simple question...
Is the following a legal config in the dao.xml? iBATIS 2.2.0 allows
this initialization (i.e. no XML barfing), but I the first DB access
(relating to the order/sql-map-config.xml) when I use this construct
gives me a "There is no statement named 'findOrderBy...' in this
SqlMap"...
I'm trying to distinguish between what might be a classpath loading
issue vs. a no-way-in-the-world-would-this-work configuration.
<daoConfig>
<context>
<transactionManager type='SQLMAP'>
<property name='SqlMapConfigResource'
value='com/foo/order/sql-map-config.xml'/>
</transactionManager>
<transactionManager type='SQLMAP'>
<property name='SqlMapConfigResource'
value='com/foo/serviceimage/sql-map-config.xml'/>
</transactionManager>
<transactionManager type='SQLMAP'>
<property name='SqlMapConfigResource'
value='com/foo/catalog/sql-map-config.xml'/>
</transactionManager>
<dao interface='com.foo.order.OrderDao'
implementation='com.foo.order.OrderDaoImpl'/>
.... other daos ....
</context>
</daoConfig>
Thanks,
-D
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.5/707 - Release Date: 3/1/2007
2:43 PM
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.5/707 - Release Date: 3/1/2007 2:43 PM
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.5/707 - Release Date: 3/1/2007 2:43 PM
|