I can confirm that this problem shows up, I have had it quite a number of times. Usually for me, the following two mistakes lead to the stacktrace:
- unbalanced quotes in tags, e.g. <h:outputText value=#{someBean.property}" />
- unbalanced tags, like forgetting to change the closing tag when changing the opening tag
I agree it's quite unsettling to get such a stacktrace, especially that those things are not the easiest to spot if your IDE doesn't tell you so.
I haven't gotten around to debug into this, however I have a hunch that this may be related to deploying on tomcat... I would think that more people would complain about this if it happened on e.g. Glassfish.
[Message sent by forum member 'manuelbernhardt']
http://forums.java.net/jive/thread.jspa?messageID=480901