I did it and works fine.
Thanks to everyone
Regards
2008/10/4 Clinton Begin <[EMAIL PROTECTED]>:
> The differences between JDBC and EXTERNAL are simply that EXTERNAL does
> NOTHING when commit and rollback are called (which works for 99% of managed
> transaction containers).
>
> http://svn.apach
The differences between JDBC and EXTERNAL are simply that EXTERNAL does
NOTHING when commit and rollback are called (which works for 99% of managed
transaction containers).
http://svn.apache.org/repos/asf/ibatis/trunk/java/ibatis-2/ibatis-2-core/src/com/ibatis/sqlmap/engine/transaction/external/Ex
OK, I'll try it.
But I've got a doubt.
There is code into my application that runs over JBoss but it doesn't
have transactions managed by application server.
For example, all classes stored in a deployed WAR file.
In this case, I wouldn't like to delegate to an EXTERNAL tx manager,
would commitTr
I'll try one more time - it IS possible if you use the EXTERNAL
transaction manager. Give it a try - surely it wouldn't take more
than 5 minutes of your time to try it???
Jeff Butler
On Fri, Oct 3, 2008 at 4:03 PM, Chema <[EMAIL PROTECTED]> wrote:
> I guess it's not possible.
> I 'm going to use
I guess it's not possible.
I 'm going to use JDBC API, I guess
Thank you very much !!
2008/10/3 Kai Grabfelder <[EMAIL PROTECTED]>:
> Jeff is totaly right, with this configuration iBATIS will never take part in
> the container managed transactions...
>
>
> --- Original Nachricht ---
> Absender:
Jeff is totaly right, with this configuration iBATIS will never take part in
the container managed transactions...
--- Original Nachricht ---
Absender: Jeff Butler
Datum: 03.10.2008 21:14
> I think you should use EXTERNAL transaction manager - this is EXACTLY
> why it exists. JBOSS, not iBATIS,
I think you should use EXTERNAL transaction manager - this is EXACTLY
why it exists. JBOSS, not iBATIS, is your transaction manager in this
case.
Jeff Butler
On Fri, Oct 3, 2008 at 2:05 PM, Chema <[EMAIL PROTECTED]> wrote:
> I don't want to keep the secret :-D
>
>
> cacheModelsEnabled="true"
I don't want to keep the secret :-D
No more.
And like you said, I don't use an EXTERNAL tx manager, but JDBC type
I think that the only solution is perform "delete" sentences by JDBC
API , so don't commit current transaction (managed by application
server).
What do you t
iBATIS will not call commit() if you have
...
I'm guessing this is NOT what you have configured - but it would be
nice to see your configuration.
Jeff Butler
On Fri, Oct 3, 2008 at 1:44 PM, Chema <[EMAIL PROTECTED]> wrote:
> I can't upgrade because my application runs over JVM 1.4 and iBat
I can't upgrade because my application runs over JVM 1.4 and iBatis
2.3.0 is the last release compatible with JVM 1.4
About your question, from documentation:
"The element also allows an optional attribute
commitRequired that can be true or
false. Normally iBATIS will not commit transactions unl
sqlMap.delete() performs a commit? That should not be the case if the tx
manager is configured correctly.
Whats your configuration? Could you please also try updating ibatis to 2.3.4,
2.3.0 is really old...
Regards
Kai
--- Original Nachricht ---
Absender: Chema
Datum: 03.10.2008 15:01
> That d
That doesn't work because sqlMap.delete() performs commit automatically.
I'm using the transaction manager of JBoss , with JNDI/JDBC.
Can I disabled this ? By code is not possible because Jboss TX manager
throws a SQLExeception.
Another w/a ?
Thanls !
2008/10/3 Kai Grabfelder <[EMAIL PROTE
if you are using CTM (container managed transactions), like in your case, you
can't start, commit or end
transactions manually. The container is doing this for you.
The following should work
> sqlMap.delete("deleteRecords", param);
If it does not I think your sqlmap configuration is not correct.
13 matches
Mail list logo
