-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 01/22/2014 04:21 PM, Nicolas Filotto wrote:
>> In our product PLF, we have an upgrade framework that manages
>> everything (if/when/where). In gatein, I don't think that you
>> have anything that can help you, I guess that the gatein team can
>> tell you more.
Alright, I'll do some other experiments to see if I can manage a
migration "on-the-fly" for this case.
>> 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.
>
>> I don't get you when you say "be for a node that is shipped with
>> GateIn", I don't see the relationship with a mixin type
I might be wrong, specially as this is the first time I deal with this
part, but I understand that a mixin would be something targeted to
developers hoping to extend GateIn, so that they won't need to deal
with the shipped types. In our case, we are shipping GateIn, so, we
can deal with those :-)
Juca.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iQEcBAEBCgAGBQJS3+MCAAoJECKM1e+fkPrXEJ8IAJQGGxt/1FAP5nFbz1EZcFcI
wOzhgPnDuD5/ewolb4HU4mKirhJdpRvhjR9DZfjoIJ6pIA+vMpdK+kW2uLuYa+OY
//G/5BtQD4goHaVbOmj7WTW+QhqZnnkozyp+nEBUC22eYuSmIDOMtft4AoyFaTyW
bsnphYjf33Se5LrHYfKeDjma3gp0usO8pFxxWcKFajZIn/SUrE27MYmkMSAfZ6wO
7tf0NKZI9EpTdW4B0lOvsMUOWw8zXhK9gVlaWApxB1KSNyBhYvPoD1GOPJSOOaOz
5TcT2/xQcxtrzW6s09na273KBk9DOu8dOUjxCUWyNkmVn+Krb9n1YH04txkj+aE=
=XADL
-----END PGP SIGNATURE-----
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev