Re: Flush cache implemented in sqlmap2

They should be. Have you tried them?

>>> Nathan Maves <Nathan.Maves <at> Sun.COM> 11/19/04 12:41 PM >>>
I have found the methods in the SqlmapClient but are they implemented
and do they work?

Custom property editor?

SQL Maps is great framework!

In my current project java.util.Calendar is used to store dates in
bean properties. Does SQLMaps work with this type?

Is this possible to add custom property editor to a bean which would
preprocess/convert property's value somehow before storing or after
reading it from database?

Using classes for composite keys

Hello,

I started implementing some classes in Hibernate where the recommended 
procedure is to create a class for your composite key and use that 
instead of multiple fields. Does iBatis support this?

Thanks,

L

Re: Custom property editor?

Aliaksandr Radzivanovich wrote:

>SQL Maps is great framework!
>
>In my current project java.util.Calendar is used to store dates in
>bean properties. Does SQLMaps work with this type?
>  
>
Not out of the box.

>Is this possible to add custom property editor to a bean which would
>preprocess/convert property's value somehow before storing or after
>reading it from database?
>
Yes indeed.  Take a look at the javadocs for 
com/ibatis/sqlmap/client/extensions/TypeHandlerCallback.  It includes an 
example of how to write a true/false<->YES/NO mapper which should get 
you started.

HTH,
Kris

PS - Where are the javadocs?  Okay, for now take a look at the source 
file - that's in the distribution under debug/ibatis-debug.jar.

--

-- 
Kris Jenkins
Email: kris <at> jenkster.com
Web:   http://cafe.jenkster.com/

Socket write error

Hi all

One customer reported a problem to us, that they are getting the following
error message:

com.ibatis.dao.client.DaoException: Error executing
query for object.  Cause: java.sql.SQLException: Io exception: Connection
reset by peer: socket write error

The cause is a restart of the Database while the application is still
running.

The transactionManager is configured via
 <transactionManager type="JDBC" >
	<dataSource type="JNDI">
		<property name="DataSource"
value="java:comp/env/jdbc/dataSourceName"/>
	</dataSource>
 </transactionManager>

Oracle suggest something like the following, when using TopLink, to
reestablish a connection:

	if (clientSession != null)
			db = clientSession;

		if (db == null || !db.isConnected()) {

			logger.info("Login Info:  trying to connect to
ClientSession ...");

ISolation levels

Problem in executing a batch

Generic SQL Map - sorry if this is a repost !

Re: Custom property editor?

Thanks Kris, I've already found this class. My problem is that in some
cases it's a bit cumbersome to deal with type handlers in XML mapping
file.
It's not a problem for result maps, for example:
<resultMap id="personResult" class="person">
   <result property="birthDate" column="BirthDate" typeHandler="thDate"/>
Once described this result map can be used for any number of queries.
But to apply type handler to a parameter (not a result) I have to use
parameter map, or I have to specify
#parameterName,typeHandler=typeHandlerName#
for every mapped bean property like in the following example.
INSERT INTO Person (ID, …, BirthDate)
VALUES (#id#, …, #birthDate,typeHandler=thDate#)
When using parameter map it is impossible to use bean property names,
only their indices. So mapping and statement would look like
<parameterMap id="personParam" class="person">
   <parameter property="id"/>
   ...
   <parameter property="birthDate" typeHandler="thDate"/>
INSERT INTO Person (ID, …, BirthDate)
VALUES (?, …, ?)
Thus, for every single insert or update statement I have to provide
its own unique parameter map, or I have to specify type handler for
the same property in every update statement.
Am I right in my assumption?
So my suggestion is: it would be nice to create one general parameter
map and then using it with any number update statements providing bean
property names instead of their indices. Is this possible?
Your help will be appreciated.

Re: Custom property editor?

Aliaksandr Radzivanovich wrote:

>Thanks Kris, I've already found this class. My problem is that in some
>cases it's a bit cumbersome to deal with type handlers in XML mapping
>file.
>It's not a problem for result maps, for example:
><resultMap id="personResult" class="person">
>   <result property="birthDate" column="BirthDate" typeHandler="thDate"/>
>Once described this result map can be used for any number of queries.
>But to apply type handler to a parameter (not a result) I have to use
>parameter map, or I have to specify
>#parameterName,typeHandler=typeHandlerName#
>for every mapped bean property like in the following example.
>INSERT INTO Person (ID, …, BirthDate)
>VALUES (#id#, …, #birthDate,typeHandler=thDate#)
>When using parameter map it is impossible to use bean property names,
>only their indices. So mapping and statement would look like
><parameterMap id="personParam" class="person">
>   <parameter property="id"/>
>   ...
>   <parameter property="birthDate" typeHandler="thDate"/>
>INSERT INTO Person (ID, …, BirthDate)
>VALUES (?, …, ?)
>Thus, for every single insert or update statement I have to provide
>its own unique parameter map, or I have to specify type handler for
>the same property in every update statement.
>Am I right in my assumption?
>So my suggestion is: it would be nice to create one general parameter
>map and then using it with any number update statements providing bean
>property names instead of their indices. Is this possible?
>Your help will be appreciated.
>  
>

I believe you're right - you'll have to specify the typeHandler in every 
place that you use the property.

As for your suggestion, we'll have to farm this out to Clinton et. al., 
but it strikes me as messy.  Here's my alternative suggestion 
(shamelessly lifted from Spring 's Validator interface) - add a new 
method to TypeHandlerCallback:

    /** Returns true if this typehandler supports the given class. */
    boolean supports( Class clazz );

For a property with a non-standard javaType, SqlMap would transparently 
use the first registered TypeHandler that claims to support the 
property's class.
Perhaps SqlMap would consult these /before/ the standard typehandlers, 
which would give people the possibility of overriding the default 
handling, too.

Any thoughts, anybody?

--

-- 
Kris Jenkins
Email:  kris <at> jenkster.com
Blog:   http://cafe.jenkster.com/
Wiki:   http://wiki.jenkster.com/