<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
How it's done affects how the user uses it.<br>
<br>
A) With the XSLT approach, user will have to point windup to the
single standalone.xml file I guess. But it can be done
"statically", nothing really running.<br>
B) With CLI, the user will point Windup to the 2 directories (EAP 6,
EAP 7). And the operation will try to run some CLI.<br>
<br>
B is imo more convenient, and also will reuse the existing code
handing the standalone.xml read/write (and take care of namespaces),<br>
but will take longer to implement correctly. So I guess it's
something for later sprints?<br>
<br>
Ondra<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 2.9.2015 17:45, Lincoln Baxter, III
wrote:<br>
</div>
<blockquote
cite="mid:CAEp_U4FjRPZJB1P1h_BTEZeEyML4dK-CxKpoUrmwNior4e2VRA@mail.gmail.com"
type="cite">
<div dir="ltr">I think that generating the configuration is a good
idea. I don't have a strong preference about how it is done.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Sep 2, 2015 at 11:43 AM, Ondrej
Zizka <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ozizka@redhat.com" target="_blank">ozizka@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I am
adding 3rd way:<br>
<br>
We could read the EAP 6 config using CLI, and write the EAP
7 config<br>
using CLI.<br>
<br>
That would need us to get the location of the EAP 6 dir and
the new EAP<br>
7 dir,<br>
and then run both in host controller mode, or how is it
called.<br>
<br>
Is that viable?<br>
<br>
Ondra<br>
<div>
<div class="h5"><br>
<br>
On 1.9.2015 15:41, Matej Briskar wrote:<br>
> Hello team,<br>
> there are new issues in the jira issues tracker for
migrating EAP6->EAP7 thanks to Eduardo. Currently we
have 3 new issues (<a moz-do-not-send="true"
href="https://issues.jboss.org/browse/WINDUPRULE-66"
rel="noreferrer" target="_blank">https://issues.jboss.org/browse/WINDUPRULE-66</a>).<br>
><br>
> We have two ways we may resolve them:<br>
> a) create XSLT - this will take a lot of time, but
user may love us for it<br>
> b) put there only hint - simple to do.<br>
><br>
> Not sure which way to go and if we have some time
to spend doing XSLT. (estimation is 1 week for 1 XSLT
transformation).<br>
</div>
</div>
> _______________________________________________<br>
> windup-dev mailing list<br>
> <a moz-do-not-send="true"
href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br>
> <a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/windup-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/windup-dev</a><br>
<br>
_______________________________________________<br>
windup-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/windup-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/windup-dev</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">Lincoln Baxter, III<br>
<a moz-do-not-send="true" href="http://ocpsoft.org"
target="_blank">http://ocpsoft.org</a><br>
"Simpler is better."</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
windup-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/windup-dev">https://lists.jboss.org/mailman/listinfo/windup-dev</a></pre>
</blockquote>
<br>
</body>
</html>