ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clinton Begin" <clinton.be...@gmail.com>
Subject Re: Unavailable DTD
Date Tue, 19 Sep 2006 01:49:10 GMT
DOM4J is an absolute nightmare.  I wouldn't recommend using it for anything
ever.  I would almost go as far as to phase out anything dependent upon
it...that's how much I dislike DOM4J.

And yes, that is likely your problem.  I'm sorry I don't have an immediate
solution other than changing the DOCTYPE for your SQL Map files -- locally
host them using a file:// URL.


On 9/18/06, Hycel Taylor <hycel1@gmail.com> 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.

View raw message