Re: [Hawkular-dev] Hawkular integration
I don't think this answers the question.
Or at least it's not clear what you suggest in terms of where the
integration code with the bus should happen.
It's not clear to me what you mean by "standalone deployments".
Thomas
On 05/20/2015 02:38 PM, John Mazzitelli wrote:
Which is why we agreed at the F2F to have REST endpoints as the
component interface that clients would use, but have a "hawkular" assembly that
would include extra bus listeners/producers that would talk to other hawkular components
when deployed in a Hawkular environment. This was the dual assembly idea (one with just
core pieces, for standalone deployments, and another one that included hawkular glue code
that allowed it to run in a hawkular environment).
----- Original Message -----
> On 20 May 2015, at 11:19, Thomas Heute wrote:
>> I think a library can be reused, or Hawkular metrics can be reused as
>> standalone project. I hardly think that a component depending on the bus
>> would be reused by anyone.
>
> +1
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev