You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2018/02/26 21:07:02 UTC
[jira] [Updated] (SLING-3584) Offline-mode for NodeTypeRegistry
[ https://issues.apache.org/jira/browse/SLING-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu updated SLING-3584:
-----------------------------------
Fix Version/s: (was: Sling Eclipse IDE 1.2.2)
Sling Eclipse IDE 1.2.4
> Offline-mode for NodeTypeRegistry
> ---------------------------------
>
> Key: SLING-3584
> URL: https://issues.apache.org/jira/browse/SLING-3584
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.0
> Reporter: Stefan Egli
> Priority: Major
> Fix For: Sling Eclipse IDE 1.2.4
>
>
> The current NodeTypeRegistry introduced with SLING-3571 only works when connected to a running server (as it retrieves the nodetypes under /jcr:system...). During development a server might not always be running though and/or you might not want to be connected to it all the time (to support batch-publishing for example). Therefore I think we should have an offline-mode for the NodeTypeRegistry (by eg storing the node types in the .settings directory or similar)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)