[ http://issues.apache.org/jira/browse/IBATIS-224?page=comments#action_12368325 ]
Sven Boden commented on IBATIS-224: ----------------------------------- Fix is available for IBATIS-224 which works on both Java 5, but also still on JDK 1.3 and 1.4. (using reflection to make the difference). I would like to check in the change in SVN and close this JIRA on February 5th, unless complaints, objections, ... > 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
