<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 27, 2015 at 12:04 PM, Darran Lofthouse <span dir="ltr"><<a href="mailto:darran.lofthouse@jboss.com" target="_blank">darran.lofthouse@jboss.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2p3" class="a3s" style="overflow:hidden">If we can document a way EAP users can use EAP 6.4 and JBoss AS7 /<br>
WildFly users can use WildFly 9.0.0.Final in admin only mode to read in<br>
legacy config and write it as the latest then technically no one should<br>
be blocked if they happen to use a schema version now removed.<br></div></blockquote><div><br>Yes I think documenting migration paths is a way to go. Also Windup project can help here.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2p3" class="a3s" style="overflow:hidden">
A general issue with parsers is we have them loaded for all versions<br>
ever supported, could this be an opportunity to switch to some form of<br>
factory so that appropriate versions can be loaded on demand.</div></blockquote></div><br></div><div class="gmail_extra">That is good point. We should address this as well as a proper way for registering transformers,<br></div><div class="gmail_extra">given that currently only way to do it is via intentionally deprecated API.<br></div><div class="gmail_extra">Both of this things go to same category, registering / defining extension.<br></div><div class="gmail_extra"><br></div></div>