<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 12, 2015 at 9:18 AM, Ladislav Thon <span dir="ltr"><<a href="mailto:lthon@redhat.com" target="_blank">lthon@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
However, if there's not enough time to do everything requried, then I<br>
believe that low-risk things like "remove the threads extension and the<br>
threads subsystem" could be left to the user (provided that they are<br>
documented).</blockquote></div><br><br></div><div class="gmail_extra">I think we could ease the threads subsystem migration.<br></div><div class="gmail_extra">For most cases threads subsystem configuration is empty as it was just present<br></div><div class="gmail_extra">in our default config as <<span class="pl-ent">subsystem</span> <span class="pl-e">xmlns</span>=<span class="pl-s"><span class="pl-pds">"</span>urn:jboss:domain:threads:1.x<span class="pl-pds">"</span></span>/><br><br></div><div class="gmail_extra">We can change parser that in case that only empty config is present it wont <br></div><div class="gmail_extra">add the subsystem at all, this should ease the migration for users migrating default configurations.<br></div><div class="gmail_extra"><br></div></div>