[jira] Closed: (SLING-38) Support declaring the class name of the ContentManager in the sling:defineObjects tag

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed SLING-38.
----------------------------------

    Resolution: Fixed

Added contentManagerClass attribute to sling:defineObjects tag which allows the definition of a class
name for the ContentManager variable.

Fixed in Rev. 581826

> Support declaring the class name of the ContentManager in the sling:defineObjects tag
> -------------------------------------------------------------------------------------
>
>                 Key: SLING-38
>                 URL: https://issues.apache.org/jira/browse/SLING-38
>             Project: Sling
>          Issue Type: Improvement
>          Components: JSP
>    Affects Versions: 2.0.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Currently the contentManager scripting variable is typed as ContentManager. In fact some times the JcrContentManager interface might be needed. In such situations, the concrete class name should be configurable in the sling:defineObjects tag much like the actual class name of the Content object.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.