[ 
http://issues.apache.org/jira/browse/IBATIS-224?page=comments#action_12368182 ] 

Sven Boden commented on IBATIS-224:
-----------------------------------

I added a patch to UnknownTypeHandler to IBATIS-224 (it will also solve 
IBATIS-210). This would solve enum support in Java 5+, and it would still be 
compatible with pre Java 5 environments (using reflection to get at new 
functionality).

I think the change is acceptible, but I would like to get second opinions. We 
don't support Java 5 (1.5) yet, but it's going to come back anyway.





> isNotNull node causes typehandler mappings in statement to fail
> ---------------------------------------------------------------
>
>          Key: IBATIS-224
>          URL: http://issues.apache.org/jira/browse/IBATIS-224
>      Project: iBatis for Java
>         Type: Bug
>   Components: SQL Maps
>     Versions: 2.1.6
>  Environment: linux/java 1.5
>     Reporter: Reuben Firmin
>     Priority: Critical
>  Attachments: UnknownTypeHandler.java, ibatis-224_sven.zip, ibatis224.tar.gz
>
> Here's my insert statement.
>     <insert id="createDeployment" parameterClass="deployment">
>         INSERT INTO Deployment (
>             environmentId, deploymentTypeId, deploymentStatusId, 
> deploymentTime
>                 <isNotNull 
> property="threadCountOverride">,threadCountOverride</isNotNull>
>         ) VALUES (
>             #environmentId#, #deploymentTypeId#, #deploymentStatusId#, 
> #deploymentTime#
>                 <isNotNull 
> property="threadCountOverride">,#threadCountOverride#</isNotNull>
>         )
>         <selectKey resultClass="int" keyProperty="deploymentId">
>             SELECT @@IDENTITY as value
>         </selectKey>
>     </insert>
> deploymentTypeId and deploymentStatusId are enums in the bean, mapped to 
> values using custom type handlers. Without the isNotNull structure around 
> threadCountOverride (which *is* nullable), the statement works. With the 
> isNotNull, deploymentStatusId and deploymentTypeId are mapped to 
> UnknownTypeHandler, and the insert fails to map the parameters from the bean.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to