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

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

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

Felix Meschberger updated SLING-44:
-----------------------------------

    Description: 
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 ?

  was:Currently the ContentManager interface has only one method to create a Content instance, which takes a path, the Content class and a Map of properties to be set on a Content instance to be created by the method. A method to create Content object in the component and have that object stored would be an important enhancement.

        Summary: Replace ContentManager.create(String, Class, Map) by create(Content) method  (was: Add ContentManager.create(String path, Content content) method)

Retargeting this issue to actually replace the create(String, Class, Map) method by a new create(Content) method.

> 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
>             Fix For: 2.0.0
>
>
> 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.