I'm confused. It seems that the problem is occuring during your build when you use velocity/dom4j to build DAOs...right? How is this an iBATIS issue?
It seems to me that velocity/dom4j must be validating your sql map files - not iBATIS. iBATIS only validates when you actually build the SqlMapClient, and iBATIS always loads DTDs from the JARs.
So maybe there is some way to turn off validation in velocity/dom4j, or to define a local XML catalog.
Jeff Butler
On 9/18/06, Hycel Taylor <[EMAIL PROTECTED]> wrote:
We think we understand something better now. We are able to build now,
because the apache web site is more stable. So, after we did the
build, we disconnected from the internet and ran some unit tests.
They worked, which proves that during runtime, IBatis is doing
validation from the jar and not from the internet. If this is the
case, I brings us to our next question.
We use Velocity, during our build runs to create our dao's from the
sql map xml files. What we believe may be happening, is as soon as
the Dom4J parser starts to parse a sql file, the internet is accessed
the retrieve the dtd to do validation. We tried taking the dtd
element out, but we then get exceptions.
How can we run our ant build scripts without having IBatis access the internet?
Thanks for your continued help in this matter.
