Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Tomitribe commitment to EE4J

> On Oct 14, 2017, at 1:55 AM, Guillermo González de Agüero <z06.guillermo@xxxxxxxxx> wrote:
> On JMS, at least the CDI alignment work should be released IMO, as it's needed for EJB decoupling. Onwards, do you (you and your team) expect JMS to be adaptable to the new cloud messaging? Payara has done some JCA resource adapters for them [1]. I wonder if JMS could handle the new systems. Perhaps with the new more open process, some representatives of those libraries would like to participate there.

On the JMS note.  Andy and Jonathan Fisher are the most JMS-excited our our side.  Definitely the new annotations that were to be introduced in JMS 2.1 were awesome for JMS messaging.  I'd be interested in anyone's thoughts on if they could apply elsewhere or there could potentially be more `Message` subclasses to encompass new cloud-specific things.

To be honest, one of the best things JMS 2.1 it would have introduced is JAX-RS-like marshalling of incoming message data to strongly typed objects.  Say,

    public void processBuild(BuildCreated buildCreated) {


There'd be rules that would be identical to HTTP/JAX-RS that says if the type is TextMessage and the mime type is application/json, use JSON-B to marshal it to an instance of BuildCreated and invoke `processBuild`

We could further say if `processBuild` had a return value, there could be annotations to say where it goes and how it is converted.


Back to the top