<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Tue, 11 Aug 2015 at 17:59 Ladislav Thon <<a href="mailto:lthon@redhat.com">lthon@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Inline.<br>
<br>
>> This is mostly about clarifying what should I do before starting the new<br>
>> server in --admin-only.<br>
>><br>
>> In standalone -- am I supposed to copy snippets from old standalone.xml<br>
>> to new standalone.xml?<br>
>><br>
>> In domain -- uh oh, sorry, I don't really know, maybe this is somehow<br>
>> connected to the ability of newer domain controller to manage older servers?<br>
>><br>
><br>
> The intent here was not to let people start with a new standard config<br>
> shipped by us and then use these ops to import stuff from a previous<br>
> config. The expectation is they are starting with their existing config<br>
> and changing it.<br>
<br>
So this is in some ways the most important part of this discussion :-)<br>
<br>
I just took standalone-ha.xml from EAP 6.4 and tried starting WildFly 10<br>
Beta1 with it. Failed immediately because "WFLYCTL0309: Legacy extension<br>
'org.jboss.as.threads' is not supported on servers running this version."<br>
<br>
Removed the extension, started again, failed with "Unexpected element<br>
'{urn:jboss:domain:threads:1.1}subsystem'" (of course!).<br>
<br>
Removed the "threads" subsystem, started again, failed with two error<br>
messages related to the "datasources" and "ejb3" subsystems.<br></blockquote><div><br></div><div>These are bugs. EJB and datasources are still very much supported, I am going to look into this. </div><div><br></div><div>Stuart</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Is this the intended workflow? I didn't get further, because I somehow<br>
get a feeling that patching the new default configuration with relevant<br>
bits from the old one will be easier when only a handful of changes in<br>
the configuration were made, and probably on-par when the configuration<br>
changes were more involved. Of course it's just a feeling, but the first<br>
impression is important too :-)<br>
<br>
> It's possible they'll want to start with some sort of a hybrid, i.e.<br>
> take our new standard config, then bring their own stuff in, and then<br>
> let us migrate parts. If so the user is responsible for creating that<br>
> initial hybrid. If some other tooling helps them with that, all the<br>
> better, but that's out of scope for these ops.<br>
<br>
Of course, no question about that.<br>
<br>
LT<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div></div>