You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@myfaces.apache.org by "Mike Kienenberger (JIRA)" <de...@myfaces.apache.org> on 2006/03/01 23:58:50 UTC

[jira] Reopened: (MYFACES-183) FacesConfigurator should report where xml parsing errors occur

     [ http://issues.apache.org/jira/browse/MYFACES-183?page=all ]
     
Mike Kienenberger reopened MYFACES-183:
---------------------------------------

     Assign To: Mike Kienenberger

It looks like this issue could addressed by using the same process as the JSF RI did.

https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=197

> FacesConfigurator should report where xml parsing errors occur
> --------------------------------------------------------------
>
>          Key: MYFACES-183
>          URL: http://issues.apache.org/jira/browse/MYFACES-183
>      Project: MyFaces Core
>         Type: Improvement
>     Versions: 1.0.9m9
>     Reporter: Mike Kienenberger
>     Assignee: Mike Kienenberger
>     Priority: Minor
>      Fix For: 1.1.0

>
> org.apache.myfaces.config.FacesConfigurator should report which resources it was parsing when it encounters an error.
> This could be done by wrapping the parsing exception with another more verbose exception.  Thus, something like
> MyApp ERROR [main 04-12 11:24:18] Digester: Parse Error at line 2 column 14: Document is invalid: no grammar found.
> org.xml.sax.SAXParseException: Document is invalid: no grammar found.
> becomes
> MyApp ERROR [main 04-12 11:24:18] FacesConfigurator : Error parsing jsf-spring-2.7.1.jar:faces-config.xml: Parse Error at line 2 column 14: Document is invalid: no grammar found.
> org.xml.sax.SAXParseException: Document is invalid: no grammar found.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira