Better logging to detect errors in CND
--------------------------------------
Key: JAHIA-3491
URL: http://www.jahia.net/jira/browse/JAHIA-3491
Project: Jahia Content Management Server
Issue Type: Improvement
Affects Versions: WCM 6.0 (Andromeda)
Reporter: Benjamin Papez
Fix For: WCM 6.0 (Andromeda)
When having a syntax error in the CND it is very difficult to find the real
reason, as often the only information I get in the log is that there is an
error in the CND file or that some node is not found.
e.g.
01.10.2008 13:55:01 *ERROR* [main] NodeTypeRegistry: Nodetype not found :
test_templates:multiSearchLangFields (NodeTypeRegistry.java, line 77)
The problem was not in this nodetype, but in one of the types before, which are
many. In this case I forgot to escape single quotes in the test templates'
definition.cnd here:
- hourWithDefaultAsNow (date, datetime[format='hh 'o''clock' a, zzzz']) = now()
But the only way to find this is by debugging. So it will be hell for template
developers to find syntactical errors, when they will not be familiar with
debugging. We need to improve the error logging, to help developes find
mistakes much easier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
