Mailing-List: contact dev-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ibatis.apache.org
Received-SPF: pass (athena.apache.org: domain of clinton.begin@gmail.com
 designates 209.85.146.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=YLeEmeqMGP1h4EeKFc+qo0N2rC1i3uTLm6mNBlyCLbtCcDdTX/zvgEjfZddvIQLYfX
         xX4pE5h56JLDuu4H+M9lZshNNBswITEPxRz0l5yNw8eV6+cCP4Zu1VYnPlqlWU+unj8m
         Gr8zwkJXGLgtEXTp2Wz/mNwvOfPVzg3lQ8XuQ=
Message-ID: <16178eb10807180623k12f3cad1l68bd82116492dbdb@mail.gmail.com>
Date: Fri, 18 Jul 2008 07:23:55 -0600
From: "Clinton Begin" <clinton.begin@gmail.com>
To: dev@ibatis.apache.org
Subject: Re: iBATIS-375 [patch]
In-Reply-To: <383C450C-0EDD-4302-AA0B-B0468D784108@ezabel.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_83286_13274171.1216387435439"
References: <BC6B8EA6-AD82-47BB-AF08-6CA5B409FA3E@ezabel.com>
	 <16178eb10807172336k5c777ab0re51aea6fc8ff0256@mail.gmail.com>
	 <383C450C-0EDD-4302-AA0B-B0468D784108@ezabel.com>

------=_Part_83286_13274171.1216387435439
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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 <ian@ezabel.com> 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 <ian@ezabel.com> 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.
>>
>
>
>

------=_Part_83286_13274171.1216387435439
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">By default iBATIS should use the DTD in the JAR file, although some parsers have ignored this and hit the web anyway.&nbsp;&nbsp; But your tools will need to be configured appropriately.&nbsp; I know IntelliJ IDEA allows a mapping of a doctype URL to any file on the filesystem.<br>
<br>Clinton<br><br><div class="gmail_quote">On Fri, Jul 18, 2008 at 6:27 AM, Ian Zabel &lt;<a href="mailto:ian@ezabel.com">ian@ezabel.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">Clinton,<div><br></div><div>Thanks!</div><div><br></div><div>Looks like that link is not quite working properly, however. But I did find this:&nbsp;<a href="http://parabuild.viewtier.com:8080/parabuild/build/results.htm?cid=e107&amp;buildrunid=9925" target="_blank">http://parabuild.viewtier.com:8080/parabuild/build/results.htm?cid=e107&amp;buildrunid=9925</a></div>
<div><br></div><div>One question, off-topic. This patch modifies the DTD.&nbsp;What strategy do most people use for pointing their xml to the new DTD for development builds?&nbsp;</div><div>I&#39;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.&nbsp;</div>
<div><br></div><font color="#888888"><div>Ian.</div></font><div><div></div><div class="Wj3C7c"><div><br><div><div>On Jul 18, 2008, at 2:36 AM, Clinton Begin wrote:</div><br><blockquote type="cite"><div dir="ltr">I&#39;ve applied the patch.&nbsp; It looks like an okay feature.&nbsp; I&#39;m going to see if there&#39;s a better way for iBATIS 3, but for now this will do. <br>
<br>I&#39;ve update the iBATIS homepage to include a link to the continuous integration server.&nbsp; Follow the instructions for &quot;Developer Release&quot; on the download page once it updates. <br> <br><a href="http://ibatis.apache.org/javadownloads.cgi" target="_blank">http://ibatis.apache.org/javadownloads.cgi</a><br>
<br>Cheers,<br>Clinton<br><br><div class="gmail_quote">On Thu, Jul 17, 2008 at 9:12 PM, Ian Zabel &lt;<a href="mailto:ian@ezabel.com" target="_blank">ian@ezabel.com</a>&gt; wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Gents,<br> <br> I&#39;ve created a patch for the following issue which seems to have some popularity, and is a personal pain point for our legacy code.<br> <br> <a href="https://issues.apache.org/jira/browse/IBATIS-375" target="_blank">https://issues.apache.org/jira/browse/IBATIS-375</a><br>
 <br> Would love to see this make it into an official release.<br> <br> Regards,<br><font color="#888888"> Ian.<br> </font></blockquote></div><br></div></blockquote></div><br></div></div></div></div></blockquote></div><br>
</div>

------=_Part_83286_13274171.1216387435439--