Re: [windup-dev] EAP6-EAP7 migration
Eduardo,
is it possible to do a system call (instead of direct API usage) to run
a generated CLI script and let AS deal with it?
Or a system call to boot the controller, and then use the REST API?
The reason for that is, that AFAIR, fiddling with standalone.xml was
officially deprecated way of configuring EAP, and the recommended,
forward compatible way, was officially CLI commands.
Is that still the case?
Thanks,
Ondra
On 2.9.2015 18:08, Eduardo Martins wrote:
Besides depending on EAP binaries, you would also need an embeddable
EAP, and that is only on WildFly (and doesn’t integrate with windup due to logging
issues).
—E
> On 02 Sep 2015, at 16:43, Ondrej Zizka <ozizka(a)redhat.com> wrote:
>
> I am adding 3rd way:
>
> We could read the EAP 6 config using CLI, and write the EAP 7 config using CLI.
>
> That would need us to get the location of the EAP 6 dir and the new EAP 7 dir,
> and then run both in host controller mode, or how is it called.
>
> Is that viable?
>
> Ondra
>
>
> On 1.9.2015 15:41, Matej Briskar wrote:
>> Hello team,
>> there are new issues in the jira issues tracker for migrating EAP6->EAP7
thanks to Eduardo. Currently we have 3 new issues
(https://issues.jboss.org/browse/WINDUPRULE-66).
>>
>> We have two ways we may resolve them:
>> a) create XSLT - this will take a lot of time, but user may love us for it
>> b) put there only hint - simple to do.
>>
>> Not sure which way to go and if we have some time to spend doing XSLT.
(estimation is 1 week for 1 XSLT transformation).
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev