Hi Jeff,
No EJB (yet although the next phase of the project will be using JMS) Everything is to be deployed in a single WAR for this release , and the DB connection pool is Container managed.
<resource-ref id= "ResourceRef_1122309943109">
<res -ref-name> jdbc/db2Connection</ res-ref-name >
<res -type> javax.sql.DataSource</ res-type >
<res -auth> Container</ res-auth >
<res -sharing-scope> Shareable</ res-sharing-scope >
</resource-ref >
(Any news on the formal abator release with BaseVO / BaseDAO yet ?)
Best Regards
Paul.
-----Original Message-----
From: Jeff Butler [mailto: [EMAIL PROTECTED]]
Sent: 28 March 2006 14:15
To: user-java@ibatis.apache.orgSubject: Re: Websphere config
Are you using EJB with container managed transactions? The configurations are different depending on the answer to that question. Let me know and I'll send back a sample config.
Jeff Butler
On 3/28/06, Paul Carr < [EMAIL PROTECTED]> wrote:
I've got the dao.xml Reader bit working ( copied the wrong line and
didn't realise till I sent the last email )
I still need to know how to configure the transaction manager to use
webspheres connection pool ?
Best Regards
Paul.
This works for me (in WAS 5.1 and WAS 6.0 - I assume it works in WAS 5.0 too):
dao.xml:
<transactionManager type="SQLMAP">
<property name="SqlMapConfigResource"
value="path_to_your_sqlmapconfig_file"/>
</transactionManager>
SqlMapConfig.xml:
<transactionManager type="JTA" commitRequired="true">
<property name="UserTransaction"
value="java:comp/env/UserTransaction"/>
<dataSource type="JNDI">
<property name="DataSource"
value="java:comp/env/jdbc/db2Connection"/>
</dataSource>
</transactionManager>
If you were using EJB and CMT, then change the SqlMapConfig file's transaction manager to type="EXTERNAL".
Jeff Butler
On 3/28/06, Paul Carr <[EMAIL PROTECTED]> wrote:
