Re: [gatein-dev] New field on node type gtn:visible - how to migrate the data?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 01/22/2014 03:32 PM, Nicolas Filotto wrote:
If you want to define a new property to a give node type you will
indeed have to do what you pointed out
(http://docs.jboss.org/exojcr/1.15.7-GA/developer/en-US/html_single/#JCR.N...),
it is not done automatically by the JCR as the default update policy
used is IGNORE_IF_EXIST and in your case you need REPLACE_IF_EXISTS
as described in the how to. So you will need do it manually and do
it within the context of the data migration.
Alright, sounds reasonable. Do you remember if/when/where this done in
the past? If so, it would help me a lot to have it as a reference.
Another approach would be to define a mixin type that only defines
your property and add this mixin type on demand to your nodes, this
way the old node type won't be modified
Considering that this would be for a node that is shipped with GateIn
itself, I'm not sure if this approach is desirable or recommended. But
if there's a precedent for this, I would also like to use it as a
reference.
Thanks!
Juca.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJS39pHAAoJECKM1e+fkPrX+pIH/0vkol4dUoG4kTIZdKWp4s8C
d5pYrE9+lumicvty9kxSRnlQlaVJuauyjgYLh1gAkvi8SXryBd3t8nm6xqXMrm/9
53ErhUghvh0nRb73KJ3otfV43PWbxE8z4FP3IFl9sZllfp9KWtUp9/gU16RmIPxP
srpyy3RWvW9alFOn1lv34SX1sBXbc5WkZvAmD6H61KiX3xRwW2oncjfK18lUlBLF
CXzy3j2DD72QexN/u8FANRlno0eeetL1jJ16gL/ZJA85/pAlOW8OS/5v3+Ht0mlI
9D2sZF22reyCjl0AaFPSWH6B1VNBwjk5fRu/zCht/b3Za8oWyNWeIjL8KK9BDNA=
=XsmJ
-----END PGP SIGNATURE-----