On 9 Jul 2014, at 18:53, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
On Wed, Jul 9, 2014 at 3:26 PM, Brian Stansberry <brian.stansberry(a)redhat.com>
wrote:
We should sort out the wildfly-server dependency, whatever it is, and
either eliminate it or make it something that relies on an optional
capability.
Agreed, most of the hard deps ware because of ARQ container needs, but that is gone now.
I have most of work done to move it out. just need some more testing.
One thing that looks fishy is Audit logging (part of controller) that has hard coded mgmt
paths to JMX subsystem
not really sure how this works if jmx is not present.
Kabir, if we move jmx out will there be any issues with that? Beyond fact that audit
logging working only when jmx subsystem is present?
IIRC all it does is when you
remove an audit log handler, to look under subsystem=jmx to make sure it’s audit logger is
not using the handler. So it should not be an issue.
--
tomaz
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev