Seems like that would require a lot of content to be potentially updated. Would this be possible to handle as part of the node type definition? It may require coordination with the JackRabbit team, but it would seem to me that this would be something you'd want to handle at the type definition level and persist across repositories instead of being saved within the IDE.
-Dan -----Original Message----- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Monday, June 03, 2013 8:42 AM To: dev@sling.apache.org Subject: Re: [tooling] Moving forward with IDE tooling On Mon, Jun 3, 2013 at 2:34 PM, Robert Munteanu <romb...@apache.org> wrote: > ...I'm not sure how we would achieve a fine control over > serialisation. Is think something you would see as user-controllable?... Maybe just a someNamespace:deepSerialize resource property would be sufficient? If it's set on a subtree, that subtree gets serialized as a single file, otherwise each resource is serialized in a single file. -Bertrand ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3343 / Virus Database: 3184/6378 - Release Date: 06/02/13
