Return-Path: Delivered-To: apmail-jakarta-struts-dev-archive@jakarta.apache.org Received: (qmail 37554 invoked by uid 500); 14 Jun 2001 22:49:06 -0000 Mailing-List: contact struts-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: struts-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list struts-dev@jakarta.apache.org Received: (qmail 37412 invoked from network); 14 Jun 2001 22:49:03 -0000 Received: from mail.commerceone.com (HELO c1plenaexi01.commerceone.com) (12.22.60.14) by h31.sny.collab.net with SMTP; 14 Jun 2001 22:49:03 -0000 Received: by c1plenaexi01.commerceone.com with Internet Mail Service (5.5.2653.19) id ; Thu, 14 Jun 2001 15:47:58 -0700 Message-ID: From: "Sukachevin, Stoehr" To: "'struts-dev@jakarta.apache.org'" Subject: RE: DTD Location Date: Thu, 14 Jun 2001 15:45:31 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N That's what Craig did for struts-config_1_0.dtd, as he explained earlier today. -- Stoehr -----Original Message----- From: William Shulman [mailto:will@metaconsortium.com] Sent: Thursday, June 14, 2001 06:10 PM To: struts-dev@jakarta.apache.org Subject: Re: DTD Location Another way is to implement your own EntityResolver to maintain a local cache. This is explained in the javadoc for the EntryResolver class (somewhere in javax.xml...) -will KenHoying@ttpartners.com writes: > Currently, the XML indicates that the DTD is located over the web using a > public qualifier. Does it really check over the web for the DTD to > validate against? I would rather not do this for performance reasons. If > it does, can I change the reference to a SYSTEM ref instead. What is the > recommended approach for a production implementation? > > Thanks in Advance, > Ken Hoying > Practice Partner > TITAN Technology Partners > Pager: 216-275-7284 >