<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 3, 2016 at 12:27 PM, Juraci Paixão Kröhling <span dir="ltr"><<a href="mailto:jpkroehling@redhat.com" target="_blank">jpkroehling@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 03.02.2016 12:25, Thomas Heute wrote:<br>
</span><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
IMO going to Wildfly management tools to configure Hawkular is IMO not a<br>
great experience.<br>
<br>
IMO for Hawkular users, Wildfly is an internal detail and its complexity<br>
should be relatively hidden.<br>
</blockquote>
<br></span>
That's a valid point. The counter point, to me, is that if/when Hawkular adds the possibility to manage this aspect of Wildfly (properties), we get Hawkular support for free :) Hawkular managing itself!<br></blockquote><div><br></div><div>If needed, yes but I don't see how one exclude the other one.</div><div><br></div><div>Thomas</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- Juca.<br>
</blockquote></div><br></div></div>