[ http://issues.apache.org/jira/browse/IBATIS-116?page=comments#action_12314012 ]
Sven Boden commented on IBATIS-116: ----------------------------------- Possibly this would also be fixed by the fix for IBATIS-152 depending on the actual exception stack trace. This is hypothetical... but assuming log4j is used with iBatis returning an empty ResultSet will cause a NullPointerException. Sven > New call to return output parameters even if no result set returned > ------------------------------------------------------------------- > > Key: IBATIS-116 > URL: http://issues.apache.org/jira/browse/IBATIS-116 > Project: iBatis for Java > Type: New Feature > Components: SQL Maps > Versions: 2.1.2 > Environment: DB2 (probably plus other databases) > Reporter: David Whipple > > We have legacy stored procedures which have input parameters and output > parameters and optional result sets. The application will not be able to > determine if the result set is going to be returned or not before the call. > If the call to the stored procedure returns a result set, we get the > result set and the output parameters just fine. > If the call does not return a result set, an exception is thrown, and we > do not get the output parameters which are needed by the application. > I believe a type of call that can handle this situation would be a good > feature. -- 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
