[
https://jira.jboss.org/jira/browse/JBIDE-5614?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBIDE-5614:
-------------------------------------
Well I would consider this to be important. IMO, having the editor look as though it is
working OK, when it's not, is one of the most frustrating things for a user. I
don't think it would be too difficult to provide some feedback to the user.
XML templating Exceptions being hidden from user
------------------------------------------------
Key: JBIDE-5614
URL:
https://jira.jboss.org/jira/browse/JBIDE-5614
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Affects Versions: 3.1.0.CR1
Reporter: Tom Fennelly
Fix For: 3.1.0.CR2
For example, where the XSD imports other XSDs and the import paths do not resolve
properly, the exception is just printed to the console
(FreemarkerTemplateContentGraphModelProviderImpl.getFreemarkerTemplateContentGraphModel)
and the editor continues on as though nothing went wrong. User just sees an empty XML
model, with now errors/warnings, unless the open the console and look for stack traces
etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira