Return-Path: Delivered-To: apmail-jakarta-struts-dev-archive@www.apache.org Received: (qmail 195 invoked from network); 1 Jan 2004 22:48:23 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 1 Jan 2004 22:48:23 -0000 Received: (qmail 41671 invoked by uid 500); 1 Jan 2004 22:48:04 -0000 Delivered-To: apmail-jakarta-struts-dev-archive@jakarta.apache.org Received: (qmail 41620 invoked by uid 500); 1 Jan 2004 22:48:04 -0000 Mailing-List: contact struts-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list struts-dev@jakarta.apache.org Received: (qmail 41607 invoked from network); 1 Jan 2004 22:48:04 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 1 Jan 2004 22:48:04 -0000 Received: (qmail 16386 invoked by uid 50); 1 Jan 2004 22:48:13 -0000 Date: 1 Jan 2004 22:48:13 -0000 Message-ID: <20040101224813.16385.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: struts-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 25155] - provide meaningful error message for "UnavailableException: Parsing error processing resource path" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.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://nagoya.apache.org/bugzilla/show_bug.cgi?id=25155 provide meaningful error message for "UnavailableException: Parsing error processing resource path" husted@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From husted@apache.org 2004-01-01 22:48 ------- I guess what we would probably need to here is pre-validate the file before handing it to the digester, so it would be part of the "pre-flight" checks comtemplated by #5739. Of course, this could not be handled by a PlugIn, since the config is needed to load a PlugIn :) *** This bug has been marked as a duplicate of 5739 *** --------------------------------------------------------------------- To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: struts-dev-help@jakarta.apache.org