You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/11/30 21:15:43 UTC

[jira] Closed: (SLING-44) Replace ContentManager.create(String, Class, Map) by create(Content) method

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

Felix Meschberger closed SLING-44.
----------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 2.0.0)

This will not be implemented as the Sling API is completely different. In addition the new ResourceManager replacing the ContentManager now has a single method for storing new and existing resources (actually their mapped objects) which is called store(Resource).


> Replace ContentManager.create(String, Class, Map) by create(Content) method
> ---------------------------------------------------------------------------
>
>                 Key: SLING-44
>                 URL: https://issues.apache.org/jira/browse/SLING-44
>             Project: Sling
>          Issue Type: New Feature
>          Components: Content
>    Affects Versions: 2.0.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> The create(String, Class, Map) method was once assumed to take the responsibility to abstractly create and configure a Content object on behalf of Components or even on behalf of some system functionality at a time, where the Component interface had split methods to handle actions and rendering.
> Nowadays the Component interface just has one single service method (and is to be removed as per SLING-28 pending vote) and it is assumed that each Component implementation would knows its Content implementation and would be able to set the fields from any request parameters. If a requirment for a generic Content generator would rise again, I suggest to implement that on higher level than the "low-level" ContentManager.
> So the new method would be create(Content) which would just store the Content object at the location described by the Content.getPath() field.
> Any opinions on this ? Or proposals for better names, by that matter ?

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