It shouldn't be hitting the server regardless.   iBATIS uses a custom EntityResolver that looks it up in the JAR file.  Check to make sure  your doctype is correctly set to

Or if for some reason your XML parser isn't honoring the EntityResolver, then you can keep local copies of the DTD and use a file:// url.


On 5/14/07, raju <> wrote:


We are using  iBATIS, and the our xml files for the DAOs include a common
entity for CRUD and  list operations.

This entity is a public identifier with URL which makes it hard to test new
versions without commiting them first.It also becomes a problemwhen xml file

Has anyone tried out using  entity in iBATIS xml config files without
actually hitting te URL specified in the DTD?

Any ideas or samples to achieve the above would be of great help.

Thanks in advance


View this message in context:
Sent from the iBATIS - User - Java mailing list archive at