Return-Path: Delivered-To: apmail-struts-dev-archive@www.apache.org Received: (qmail 93793 invoked from network); 9 Mar 2006 02:37:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Mar 2006 02:37:38 -0000 Received: (qmail 15318 invoked by uid 500); 9 Mar 2006 02:37:34 -0000 Delivered-To: apmail-struts-dev-archive@struts.apache.org Received: (qmail 15275 invoked by uid 500); 9 Mar 2006 02:37:34 -0000 Mailing-List: contact dev-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list dev@struts.apache.org Received: (qmail 15262 invoked by uid 99); 9 Mar 2006 02:37:34 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Mar 2006 18:37:34 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Mar 2006 18:37:33 -0800 Received: by ajax (Postfix, from userid 65534) id A9B656ACA9; Thu, 9 Mar 2006 02:37:12 +0000 (GMT) From: bugzilla@apache.org To: dev@struts.apache.org Subject: DO NOT REPLY [Bug 38560] - [shale] include local copies of dtds In-Reply-To: X-Bugzilla-Reason: AssignedTo Message-Id: <20060309023712.A9B656ACA9@ajax> Date: Thu, 9 Mar 2006 02:37:12 +0000 (GMT) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=38560 ------- Additional Comments From craig.mcclanahan@sun.com 2006-03-09 02:37 ------- Ryan, could you send me a stack trace of the failure from this scenario? The reason I'm asking is that the core of Shale never actually parses a faces-config.xml file itself, so it may actually be the JSF implementation that is doing this. The only place that Shale parses a faces-config.xml file is in the Tiger Extensions, and the DTD *is* declared locally there (see class org.apache.shale.tiger.config.FacesConfigParser). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For additional commands, e-mail: dev-help@struts.apache.org