<div dir="ltr"><div><div><div>In any case it cannot be org.jboss.*<br>it can be org.wildfly.<something><br></div><br></div>Looking trough the rebased code it is still war application depending on servlet container to be present.<br>
Taking that into consideration, this cannot be part of our main codebase/distribution, but having it as external add-on project sounds fine.<br><br>In this case i would go for org.wildfly.jmx-console as groupId and artifact id based on logical part of artifact inside the project.<br>
probably just jmx-console.<br><br>btw, your rebased project still imports java ee6 dependencies, given wildfly is ee7 now it would be wise to upgrade that.<br><br>--<br></div>tomaz<br></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Wed, Jun 4, 2014 at 3:53 PM, Sebastian Łaskawiec <span dir="ltr"><<a href="mailto:sebastian.laskawiec@gmail.com" target="_blank">sebastian.laskawiec@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi Brian<div><br></div><div>I thought about:</div><div><ul><li><pre style="font-size:12px;margin-top:0px;margin-bottom:0px;color:rgb(51,51,51)"><pre style="margin-top:0px;margin-bottom:0px"><font face="arial, helvetica, sans-serif"><b>org.jboss</b></font></pre>
</pre></li><li><pre style="font-size:12px;margin-top:0px;margin-bottom:0px;color:rgb(51,51,51)"><font face="arial, helvetica, sans-serif"><a href="http://org.jboss.as" target="_blank">org.jboss.as</a></font></pre>
</li><li><pre style="font-size:12px;margin-top:0px;margin-bottom:0px;color:rgb(51,51,51)"><font face="arial, helvetica, sans-serif">org.wildfly</font></pre></li></ul><div><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:12px;white-space:pre-wrap">,artifact id:</span></font></div>
</div><div><ul><li><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:12px;white-space:pre-wrap">wildfly-jmx-console</span><br></font></li><li><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:12px;white-space:pre-wrap"><b>jboss-jmx-console</b></span><br>
</font></li></ul><div><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:12px;white-space:pre-wrap">and finally version:</span></font></div></div><div><ul><li><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:12px;white-space:pre-wrap">start from the scratch 1.0.0-SNAPSHOT</span></font></li>
</ul><div><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:12px;white-space:pre-wrap">My preferences are - org.jboss as group id and jboss-jmx-console as artifact id. What do you think, is it ok?</span></font></div>
</div><div><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:12px;white-space:pre-wrap"><br></span></font></div><div><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:12px;white-space:pre-wrap">Best regards</span></font></div>
<div><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:12px;white-space:pre-wrap">Sebastian</span></font></div><div><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:12px;white-space:pre-wrap"><br>
</span></font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-06-03 22:33 GMT+02:00 Brian Stansberry <span dir="ltr"><<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a>></span>:<div>
<div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Sebastian,<div><br>
<br>
On 6/1/14, 1:21 PM, Sebastian Łaskawiec wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Brian<br>
<br>
Thanks for clarification and sorry for late response.<br>
<br>
I created Feature Request to add expose MBean server through HTTP<br>
management interface: <a href="https://issues.jboss.org/browse/WFLY-3426" target="_blank">https://issues.jboss.org/<u></u>browse/WFLY-3426</a><br>
<br>
</blockquote>
<br></div>
Thanks.<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It would be great to have MBean server exposed via Wildfly HTTP<br>
Management interface, but I know several teams which would like to have<br>
such functionality in JBoss AS 7. This is why I started looking at<br>
Darran's port to JMX console<br>
(<a href="https://github.com/dandreadis/wildfly/commits/jmx-console" target="_blank">https://github.com/<u></u>dandreadis/wildfly/commits/<u></u>jmx-console</a>). I rebased<br>
it, detached from Wildfly parent and pushed to my branch<br>
(<a href="https://github.com/altanis/wildfly/commits/jmx-console-ported" target="_blank">https://github.com/altanis/<u></u>wildfly/commits/jmx-console-<u></u>ported</a>). The<br>
same WAR file seems to work correctly on JBoss AS 7 as well as Wildfly.<br>
<br>
In my opinion it would be great to have this console available publicly.<br>
Is it possible to make the WAR file available through JBoss Nexus<br>
(perhaps thirdparty-releases repository)? If it is, I'd squash all<br>
commits and push only jmx-console code into new github repository (to<br>
make it separate from Wildfly).<br>
<br>
</blockquote>
<br></div>
What maven Group were you wanting to use? That jmx-console-ported branch has org.wildfly in the pom.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
Best regards<br>
Sebastian<br>
<br>
<br>
<br>
2014-05-22 3:23 GMT+02:00 Brian Stansberry <<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a><br></div>
<mailto:<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@<u></u>redhat.com</a>>>:<div><div><br>
<br>
I agree that if we exposed the mbean server over HTTP that it should be<br>
via a context on our HTTP management interface. Either that or expose<br>
mbeans as part of our standard management resource tree. That would make<br>
integration in the web console much more practical.<br>
<br>
I don't see us ever bringing back the AS5-style jmx-console.war that<br>
runs on port 8080 as part of the WildFly distribution. That would<br>
introduce a requirement for EE into our management infrastructure, and<br>
we won't do that. Management is part of WildFly core, and WildFly core<br>
does not require EE. If the Servlet-based jmx-console.war code linked<br>
from WFLY-1197 gets further developed, I see it as a community effort<br>
for people who want to install that on their own, not as something we'd<br>
distribute as part of WildFly itself.<br>
<br>
On 5/21/14, 7:37 AM, Sebastian Łaskawiec wrote:<br>
> Hi<br>
><br>
> One of our projects is based on JBoss 5.1 and we are considering<br>
> migrating it to Wildfly. One of our problems is Web based JMX<br>
Console...<br>
> We have pretty complicated production environment and Web based JMX<br>
> console with basic Auth delegated to LDAP is the simplest<br>
solution for us.<br>
><br>
> I noticed that there was a ticket opened for porting legacy JMX<br>
Console:<br>
> <a href="https://issues.jboss.org/browse/WFLY-1197" target="_blank">https://issues.jboss.org/<u></u>browse/WFLY-1197</a>.<br>
> However I think it would be much better idea to to have this<br>
> functionality in Web Administraction console. In my opinion it<br>
would be<br>
> great to have it under "Runtime" in "Status" submenu.<br>
><br>
> What do you think about this idea?<br>
><br>
> Best Regards<br>
> --<br>
> Sebastian Łaskawiec<br>
><br>
><br>
> ______________________________<u></u>_________________<br>
> wildfly-dev mailing list<br></div></div>
> <a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a> <mailto:<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.<u></u>jboss.org</a>><div>
<br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/<u></u>mailman/listinfo/wildfly-dev</a><br>
><br>
<br>
<br>
--<br>
Brian Stansberry<br>
Senior Principal Software Engineer<br>
JBoss by Red Hat<br>
______________________________<u></u>_________________<br>
wildfly-dev mailing list<br></div>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a> <mailto:<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.<u></u>jboss.org</a>><div>
<br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/<u></u>mailman/listinfo/wildfly-dev</a><br>
<br>
<br>
<br>
<br>
--<br>
Sebastian Łaskawiec<br>
</div></blockquote>
<br><div><div>
<br>
-- <br>
Brian Stansberry<br>
Senior Principal Software Engineer<br>
JBoss by Red Hat<br>
</div></div></blockquote></div></div></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br>Sebastian Łaskawiec
</font></span></div>
<br>_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br></blockquote></div><br></div>