Hi,
Am 08.04.2008 um 08:43 schrieb Felix Meschberger:
Am Montag, den 07.04.2008, 17:55 +0200 schrieb Alexander Saar:
Nevertheless,
the property has the advantage, that it may already be set in the
repository when you extract it to package it in the bundle.
Not sure what you mean with extract it for packaging. Do you mean
system export? What I do ATM is writing initial content definitions
by hand. Not sure if the property is present directly after the node
is created (and not saved). Anyway I think checking the value of the
property in the repository does not help, because this does not allow
the developer to define if it should be checked in or not.
Yes, I meant system export. But also JSON export using the
JsonRenderer
Servlet (with jcr:* property export switched on). I am neither sure
whether jcr:isCheckedOut property is set or not and to what value
before
the node is saved after adding the mixin node type. But this doesn't
probably matter at all because you will export after saving.
Yes.
If you create the content manually, it is probably easier to use the
global flag.
Using the global flag is absolutely fine for me. If one needs more
fine grained control it is also possible to split the content and
declare different header parameters for the content pieces. So I think
this is enough flexibility for most application developers. Anyway
taking jcr:isCheckedOut into account would be great for content exports.
BR Alex
