[ 
http://issues.apache.org/jira/browse/MYFACES-183?page=comments#action_12316974 
] 

Mike Kienenberger commented on MYFACES-183:
-------------------------------------------

I've been trying to write a patch for this, but it appears that this error is 
caught and reported in the org.apache.xerces code and isn't thrown back to the 
caller.

Possibly the only thing that could be done is to change these INFO log messages 
to also output the name of the original jar as well as the temporary jar 
created.

16:24:03.218 INFO   [main] 
org.apache.myfaces.config.FacesConfigurator.feedJarConfig(FacesConfigurator.java:316)
 >12> Reading config 
jar:file:/D:/DOCUME~1/mlk/LOCALS~1/Temp/myfaces48297.jar!/META-INF/faces-config.xml

At least two other users have had problems with this situation on the 
myfaces-user list, so it'd be good if something could be done to make tracking 
down jars with configuration problems easier.

-Mike


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

>
> 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

Reply via email to