<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 17.7.2015 08:22, Stian Thorgersen
wrote:<br>
</div>
<blockquote
cite="mid:1352841341.40862378.1437114156177.JavaMail.zimbra@redhat.com"
type="cite">
<pre wrap="">We shouldn't need deprecated stuff in realm model and user model. That's what the migration stuff is there to do.
Problem with regards to json representations is that we don't have an elegant way to deal with migration. If we add that we won't have the problem of keeping deprecated stuff around and it'll just be a matter of keeping some json transformation classes similar to what we do for jpa/mongo.</pre>
</blockquote>
Maybe for JSON representations, we can use "JsonAnyGetter" and
"JsonAnySetter" annotations to migrate old properties from
representation classes. Problem is, that this approach is always a
bit more work than keeping the old properties and migrate them
directly.<br>
<br>
Like for DB, we have 2 approaches for migrations right now:<br>
1) MigrationModelManager, which is easier to use, but it requires
that all the old properties are <span style="color:#808000;"></span>still
kept on JPA and Mongo entity classes.<br>
2) Liquibase and Mongo specific migrations, which migrates old data
at DB level and doesn't require old properties to be kept. But it's
pain to write migration scripts for them.<br>
<br>
Maybe easiest is between minor versions to keep old properties and
use the "easy" way of migrations, but for major versions, use the
generic approach and get rid of all the outdated stuff from both
JSON and DB?<br>
<br>
Marek<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<blockquote
cite="mid:1352841341.40862378.1437114156177.JavaMail.zimbra@redhat.com"
type="cite">
<pre wrap="">
----- Original Message -----
</pre>
<blockquote type="cite">
<pre wrap="">From: "Bill Burke" <a class="moz-txt-link-rfc2396E" href="mailto:bburke@redhat.com"><bburke@redhat.com></a>
To: <a class="moz-txt-link-abbreviated" href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a>
Sent: Friday, 17 July, 2015 2:29:48 AM
Subject: [keycloak-dev] deprecated removals in future
We're accumulating deprecated metadata in models and data model.
Eventually we should draw a line in the sand and say we will only
support migration from a certain version to current.
i.e. Keycloak 2.0 would only allow migration from the last 1.x version.
We need to clean all the old stuff out prior to product.
--
Bill Burke
JBoss, a division of Red Hat
<a class="moz-txt-link-freetext" href="http://bill.burkecentral.com">http://bill.burkecentral.com</a>
_______________________________________________
keycloak-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
keycloak-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>