[wildfly-dev] Is JMX Needed in Core?

Darran Lofthouse darran.lofthouse at jboss.com
Thu Jul 10 06:51:54 EDT 2014


On 10/07/14 00:00, Tomaž Cerar wrote:
>
> On Wed, Jul 9, 2014 at 9:35 PM, Brian Stansberry
> <brian.stansberry at redhat.com <mailto:brian.stansberry at redhat.com>> wrote:
>
>
>     Does logging belong in web then then? Still seems like something that
>     even the uber-minimalists would want. I ask because it bugs me that we
>     have two meanings now for "core" -- the old "core" notion that was the
>     true core with zero subsystems, and now this new wildfly-core dist,
>     which has subsystems.
>
>
> Core *current* comes with following subsystems:
> - logging
> - jmx (on the way out)
> - deployment-scanner
> - remoting
> - io (because of remoting)
>
> I agree that jmx needs to go out,
> deployment scanner needs to stay.
> And remoting is needed to make cli & alike work...

In my mind the main thing I think that defines the core is that is 
provides you with a base manageable server, Remoting is an integral part 
of that.

JMX on the other hand is additional functionality layered on top, 
closely related to management but not a requirement of it.

>
>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>


More information about the wildfly-dev mailing list