[Hawkular-dev] generation of message POJOs via JSON schema

[Lukas Krejci]

On Friday, February 27, 2015 13:46:05 Jay Shaughnessy wrote:
> On 2/27/2015 1:28 PM, Stefan Negrea wrote:
> > <clip>
> > 
> > Now, one thing that I would be very concerned to see is transforming the
> > bus into a central repository and source for schemas. The bus should be
> > designed following the "dumb pipes" [1] principle. It should take care of
> > delivery but never ever inspect or make decisions based on actual content
> > piped.
> > 
> > [1]
> > http://martinfowler.com/articles/microservices.html#SmartEndpointsAndDumb
> > Pipes
> No doubt the bus should be (and is) dumb plumbing.  What we are talking
> about are the apps using the bus, and what makes it easy for them to
> provide and consume messages.  It seems like we could do a little better
> than reading docs, screwing up, and retrying, at least for Java
> clients. 

+100

The schema, after all is a sort of documentation. If it is "functionally" tied 
with the implementation itself (i.e. one generated from the other) then it 
also never gets out of sync, unlike the written documentation.

> I would happily incorporate a Gson-ready pojo guaranteed to
> parse out the Json dropped on HawkularMetricsData topic.  I don't really
> care which client jar I need to get it, whether it was a kettle client
> jar or a metrics client jar.
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev