Just one thought: in your SqlMapConfig file, have you included your
ErrorMap.xml (or whatever it's called) BEFORE the SqlMap which is trying
to use it?

I've seen problems caused by this in the past.


Alistair.

-----Original Message-----
From: _Eric_ [mailto:[email protected]] 
Sent: 15 January 2009 12:44
To: [email protected]
Subject: include SQL mapping file


Hi all,

I have one mapping file for every message type I send. There is an error
handling used in every message type. So I want to put it in an seperate
mapping config:

<sqlMap namespace="Error">
        <typeAlias alias="Error" type="de.blah.database.type.ZdaError"
/>
        <resultMap id="ErrorMap" class="Error" >
                <result property="code" column="code" />
                <result property="message" column="message" />
        </resultMap>

        <select id="getError" parameterClass="int" resultMap="ErrorMap"
>
                SELECT code, message FROM error WHERE id=#value#
        </select>
</sqlMap>


To use it I used the select with the name space :<result
property="error" 
column="error" select="Error.getError"/> And put the sqlMap resource
into the sqlMapConfig.

The result is an iBatis error: Cause:
com.ibatis.sqlmap.client.SqlMapException: There is no statement named
Error.getError in this SqlMap.

How can I reuse in sveral mapping files?

Greetings
Eric


--
View this message in context:
http://www.nabble.com/include-SQL-mapping-file-tp21476828p21476828.html
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.



Please help Logica to respect the environment by not printing this email  /  
Merci d'aider Logica à préserver l'environnement en évitant d'imprimer ce mail 
/  Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei 
die Umwelt zu schuetzen  /  Por favor ajude a Logica a respeitar o ambiente não 
imprimindo este correio electrónico.



This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.


Reply via email to