>
> So, communication via Java API should be feasible.
That is an option as long as it works in a distributed environment (think
containers and different JVMs; would Java API work there? and how?) and the
same interface that is currently exposed on the public REST API is
available.
I'm not thinking as a general option.
But I have a wildfly server with metrics.war and alerts.war and mycomponent.war as client
under same deployment, why I can't use Java API and I need to use REST between them ?
EJB clients are also possible but this was not introduced before and I don't want to
do it.
But in the first scenario, looking for a user that wants to add its code colocated, the
Java API should be the easy one.