Clinton,
On Sun, Apr 18, 2010 at 2:45 PM, Clinton Begin wrote:
> You did the right thing... iBATIS transaction managers are meant to be easy
> to implement yourself.
>
Yes, they are easy to implement!
That said, this was a matter of constant debate back in the good old days
> when none of the s
Thanks Andrius and Larry for the information. Modified to use #param#
instead of $param$. This fixed our problems.
Larry Meadors wrote:
>
> ...or since you're using ibatis2, #param# instead of $param$. :)
>
> On Sat, Apr 17, 2010 at 2:55 AM, Andrius Juozapaitis
> wrote:
>> It's likely that
Thanks Adinath.
This will all help. Let's figure this out together.
The odd thing for me is this. A typical transaction lifecycle (be it global
or otherwise would be:
* Open Connection
* Do Work
* Commit or Rollback
* Close Connection (even if this implies a return to the connection pool)
I haven't been following this thread closely, but with JBoss at least,
you have the option of configuring datasources as no-transaction:
no-tx-datasource. With this type of datasource, you are free to call
commit and rollback yourself. With container-managed transactions, you
should not be ca
On Mon, Apr 19, 2010 at 8:15 AM, Clinton Begin wrote:
> Thanks Adinath.
>
> This will all help. Let's figure this out together.
>
> The odd thing for me is this. A typical transaction lifecycle (be it
> global or otherwise would be:
>
> * Open Connection
> * Do Work
> * Commit or Rollback
> *
On Mon, Apr 19, 2010 at 10:33 AM, Guy Rouillier wrote:
> I haven't been following this thread closely, but with JBoss at least, you
> have the option of configuring datasources as no-transaction:
> no-tx-datasource. With this type of datasource, you are free to call commit
> and rollback yourself
Attempting to run a z/OS application using DB2 V9 JDBC ibatis:
"com.ibatis.dao.client.DaoException: Failed to execute queryForObject - id
...
Cause: com.ibm.db2.jcc.am.SqlException: [jcc][50053][12311][4.7.94] T2zOS
exception: [jcc][T2zos]T2zosConnection.flowConnect:execConnect:1347: DB2
engine S
On 4/19/2010 2:07 PM, Adinath wrote:
Regarding your thoughts about a smart resource manager, that is
indeed what happens. Remember that datasource may be retrieved and
closed any number of times during the processing of a single EJB
method. During the execution of single EJB me
