You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by Nail Uenlue <na...@gmail.com> on 2009/07/29 12:59:46 UTC
INOUT mode for Oracle Object Types
Hi everyone,
I have the following code in my map configuration:
<parameterMap id="getKeywordParam" class="ch.generali.converter.bean.Keyword">
<parameter property="keywords"
typeHandler="ch.xxx.converter.dao.KeywordTypeHandlerCallback"
javaType="OBJECT" jdbcType="KEYWORD_TAB" mode="INOUT" />
<parameter property="language" jdbcType="NUMERIC" mode="IN"
javaType="java.lang.Integer" />
<parameter property="vertragsnr" jdbcType="VARCHAR" mode="IN"
javaType="java.lang.String" />
</parameterMap>
<procedure id="getKeyword" parameterMap="getKeywordParam">
{call vvever.pck_ev_xxx.if_get_xxx_liste(?,?,?)}
</procedure>
My custom typehandler in that case is not that important as i get the
correct result of my query as long as i define the parameter
"keywords" as an IN-parameter.
As soon as i define it as INOUT, ibatis raises an error and never
reaches my TypeHandlerCallback.
The specification of the procedure is as follows:
procedure .if_get_xxx_liste (
keywordList IN OUT keyword_tab,
language IN number,
s_ver_vertrag in varchar2);
What could be the reason for this behavour?
cu,
Nail
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org