You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2014/05/20 18:04:40 UTC

[jira] [Resolved] (SLING-3237) Refine new node creation workflow

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

Stefan Egli resolved SLING-3237.
--------------------------------

    Resolution: Fixed

Implemented the following:
 * there's a NodeTypeRegistry, loaded from the repository at start time (offline-mode pending: SLING-3584)
 * node creation dialog takes NodeTypeRegistry into account when listing possible node types
 * node creation handles different serializationKinds accordingly

Considering this done therefore. Additional issues can be treated separately.

> Refine new node creation workflow
> ---------------------------------
>
>                 Key: SLING-3237
>                 URL: https://issues.apache.org/jira/browse/SLING-3237
>             Project: Sling
>          Issue Type: Sub-task
>          Components: IDE
>            Reporter: Robert Munteanu
>            Assignee: Stefan Egli
>             Fix For: Sling Eclipse IDE 1.0.0
>
>
> When creating a new node the dialog unconditionally generates a ${node-name}.xml file. This doesn't really account for whether we are allowed to generate such a node in this location, or whether the node has full or partial coverage.
> This can lead to invalid structures being serialized on disk.
> Originally reported by [~dsuess]



--
This message was sent by Atlassian JIRA
(v6.2#6252)