ManagedTransaction closing Connection about mybatis HOT 5 CLOSED

Ha!  There was a big discussion thread about this on a previous mailing list. 
There
was a lot of back and forth about whether the connection should or shouldn't be
closed.  It's a gray area in the JDBC / JTA specs (plus probably a number of 
other
J2EE specs).   Different app servers behave different ways.  I originally though
exactly the same way you are, but after further investigation, it's "more 
common and
accepted" for consumers of a managed to connection to call close().  The 
container or
transaction manager shouldn't actually close the connection, but instead should 
just
"mark" it as no longer in use so that it can be closed at the end of the 
transaction
scope.  While it was still fuzzy as to which way to go, ultimately we decided 
that we
would use iBATIS 2 as the tie breaker -- which means we decided to close the
connection.  

Here's the original thread:

http://www.mail-archive.com/[email protected]/msg16138.html

I think the right thing to do here will be to create another implementation, or
perhaps a config property to not close the connection.  

As for the null check... that's one of those things where I would expect a null
pointer exception.  It's not an acceptable call of that method. 

Cheers,
Clinton

Added closeConnection property to transactionManager.  For example:

{{{
<transactionManager type="MANAGED">
    <property name="closeConnection" value="false"/>
</transactionManager>
}}}

Default is still true (close the connection).

Can you give a couple of  sample configuration code for "how to make the 
mybatis transaction management in EBJ3.0 contrainer" , thanks very much.