I did refer to wf-core to point to the base capabilities of wildfly. Nothing prevents you
from building upon the full EE server (wildfly), although you probably won’t need all the
stock components.
But what you say about Hawkular is interesting. I wasn’t aware of this effort until Mazz
brought it forward. Listening to what you say Jay, it seems I confused rhq.metrics with
rhq.next.
Can you point me to some documentation about the architecture and design decisions behind
rhq.next? Is it correct to say that rhq.next will leverage some of the rhq.metrics
components?
Regards, HeikoB
On 08 Jan 2015, at 16:54, Jay Shaughnessy <jshaughn(a)redhat.com>
wrote:
HeikoB, as for Wildfly-core, we haven't really used that afaik, just using Wildfly at
this point because I'm not sure Wildfly-core was quite ready last time we looked. Has
that changed? I assume wfly-core is much lighter that wfly, and that is the main
advantage, giving up the J2EE EAR/WAR support. etc. Perhaps both wfly-core and wfly
proper will both play a role going forward.