By default iBATIS should use the DTD in the JAR file, although some parsers have ignored this and hit the web anyway. But your tools will need to be configured appropriately. I know IntelliJ IDEA allows a mapping of a doctype URL to any file on the filesystem.
Clinton On Fri, Jul 18, 2008 at 6:27 AM, Ian Zabel <[EMAIL PROTECTED]> wrote: > Clinton, > Thanks! > > Looks like that link is not quite working properly, however. But I did find > this: > http://parabuild.viewtier.com:8080/parabuild/build/results.htm?cid=e107&buildrunid=9925 > > One question, off-topic. This patch modifies the DTD. What strategy do most > people use for pointing their xml to the new DTD for development builds? > I've changed my xml doctype to SYSTEM and pointed it to a local version of > the DTD. Is there a better way? Would be nice if anyone knows how set up the > XML to use a DTD from the iBatis JAR in META-INF or something. > > Ian. > > On Jul 18, 2008, at 2:36 AM, Clinton Begin wrote: > > I've applied the patch. It looks like an okay feature. I'm going to see > if there's a better way for iBATIS 3, but for now this will do. > > I've update the iBATIS homepage to include a link to the continuous > integration server. Follow the instructions for "Developer Release" on the > download page once it updates. > > http://ibatis.apache.org/javadownloads.cgi > > Cheers, > Clinton > > On Thu, Jul 17, 2008 at 9:12 PM, Ian Zabel <[EMAIL PROTECTED]> wrote: > >> Gents, >> >> I've created a patch for the following issue which seems to have some >> popularity, and is a personal pain point for our legacy code. >> >> https://issues.apache.org/jira/browse/IBATIS-375 >> >> Would love to see this make it into an official release. >> >> Regards, >> Ian. >> > > >
