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

Posted to dev@sling.apache.org by "Jörg Hoh (JIRA)" <ji...@apache.org> on 2015/05/27 10:54:17 UTC

[jira] [Created] (SLING-4754) Improve error message if referenced resource type is not available

Jörg Hoh created SLING-4754:
-------------------------------

             Summary: Improve error message if referenced resource type is not available
                 Key: SLING-4754
                 URL: https://issues.apache.org/jira/browse/SLING-4754
             Project: Sling
          Issue Type: Improvement
          Components: Scripting
    Affects Versions: Scripting Sightly Engine 1.0.2
            Reporter: Jörg Hoh
            Priority: Minor


When content references a sightly component, which is not available, it throws a SightlyException with the message "Unable to generate Java class for template /apps/.../foobar.html".

Which is correct, but in case the referenced component is just not there, the error handling could be improved to something like "Unable to resolve template %s in the repository".  

It took me a look in the sourcecode to find the actual root cause, when I got a stacktrace of the generic SightlyException in UnitLoader.java, line 151.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)