Thank you Clinton.. Chris
"Clinton Begin" <[EMAIL PROTECTED]> 07/15/2008 10:38 AM Please respond to [email protected] To [email protected] cc Subject Re: NullPointerException after upgrade to 2.3.2 I'll add the patch now... and let you know when to grab from SVN. Clinton On Tue, Jul 15, 2008 at 11:29 AM, <[EMAIL PROTECTED]> wrote: Is the fix committed so I can get it and build from SVN? Chris Mathrusse [EMAIL PROTECTED] Sybase, Inc One Sybase Drive Dublin, CA 94568 (925) 236-5553 "Clinton Begin" <[EMAIL PROTECTED]> 07/15/2008 10:27 AM Please respond to [email protected] To [email protected] cc Subject Re: NullPointerException after upgrade to 2.3.2 Known bug, sorry about that. I hope to get to a fix soon... it's easy, just time. Clinton On Tue, Jul 15, 2008 at 11:24 AM, <[EMAIL PROTECTED]> wrote: I just upgraded to 2.3.2 due to the fact that Spring 2.5.5 seems to need it. After I upgraded I am now getting a NullPointerException after executing a procedure. This was working prior to the upgrade and seems to be associated to the TypeHandlerFactory.setTypeHanlder method at line 143. As I step through the code it appears that the result is returned from the procedure. I can see the value returned and my CustomTypeHandler is being invoked and is returning the correct value. ('N' == Boolean.FALSE) It appears this error begins in the class ComplexDataExchange.setData() method. On line 95 the following statement is executed: if (typeHandlerFactory.hasTypeHandler(parameterMap.getParameterClass())) { However, my parameterMap has no parameterClass specified and when it is retrieved a null value is returned. This causes the NullPointerException to occur in the TypeHandlerFactory.setTypeHanlder() method at line 143: if (handler == null && Enum.class.isAssignableFrom(type)) { The test is made to see if the handler is null but no test is performed to see if the type is null and this results in the NullPointerException. Is it now required to have a ParameterClass specified on every statement? Chris
