Re: Domain Events

[Andi Huber]

I just realized, we are planning to deprecate support for Guava's event
bus with Isis 2.0.0 anyway [1].

Consequently I'll update my test methodology regarding JEE 7+ support [2].

[1] https://issues.apache.org/jira/browse/ISIS-1753

[2] https://issues.apache.org/jira/browse/ISIS-1767


On 10.11.2017 23:24, Óscar Bou - GOVERTIS wrote:
>
>
>
> Hi Andy.
>
> Guava event bus implementation is not useful for many use cases, as it
> enqueues calls, changing the usually expected execution flow.
> That was the initial reason we implemented the Axon event bus support.
>
> I saw CDI event bus implementation and seems it can handle that use
> case (assuming it dispatches events as soon as they happen, not
> queueing them).
>
> We are not currently planning on using JEE, but just to let you know
> the original motivation, as I’m seeing you’re testing Guava events
> working properly instead of Axon (devs would encounter that queueing
> problem if Axon is not available).
>
>
> Regards,
>
> Oscar
>
>
>
>
>
>> El 28 oct 2017, a las 12:40, Andi Huber > > escribió:
>>
>> I just realized, we have Axon as isis/runtime dependency for more than a
>> year now!? (Had thought that was a very recent change in direction.)
>>
>> So I guess, we may put CDI event processing on the wish-list for now,
>> and support Axon on JEE.
>>
>> Cheers, Andi
>>
>> On 28.10.2017 11:00, Andi Huber wrote:
>>> Hi Dan,
>>> while working on JEE support for Isis, I encountered difficulties with
>>> the Axon framework:
>>>
>>> Just the first exception thrown (there might be other issues as well)
>>> originates from Axon requesting an EntityManager from JEE, which is not
>>> available out of the box if not configured. (And we don't need to
>>> configure one, because we - as of yet - use JDO.)
>>>
>>> Following earlier posts on the mailing list, I think we had event
>>> processing using Guava, which worked on JEE containers without issues.
>>>
>>> CDI (since JEE 6 [1]) provides event processing as well, and Weld
>>> [2] which
>>> is the reference implementation of CDI, is now also available for Java
>>> SE. So I guess Weld could be deployed on non-CDI environments to provide
>>> event processing.
>>>
>>> I'm confident, with some additional investigation, we can use Axon on
>>> JEE, but the question emerges:
>>>
>>> Are we sure we want to use Axon for event processing, considering that
>>> we have a tendency towards CDI anyway?
>>>
>>> Cheers, Andi
>>>
>>> [1] https://docs.oracle.com/javaee/6/tutorial/doc/gkhic.html#gkhih
>>> [2] http://docs.jboss.org/weld/reference/latest/en-US/html/events.html
>>>
>>
>
>
> Óscar Bou Bou
> Socio - IT & GRC Management Services Director
> m: +34 620 267 520
> s: www.govertis.com e: o@govertis.com 
>
> LinkedIn: https://www.linkedin.com/in/oscarbou
> Twitter: @oscarbou 
>
>
>
> Este mensaje y los ficheros anexos son confidenciales. Los mismos
> contienen información reservada que no puede ser difundida. Si usted
> ha recibido este correo por error, tenga la amabilidad de eliminarlo
> de su sistema y avisar al remitente mediante reenvío a su dirección
> electrónica; no deberá copiar el mensaje ni divulgar su contenido a
> ninguna persona.
>
> Su dirección de correo electrónico junto a sus datos personales
> constan en un fichero titularidad de GOVERTIS ADVISORY SERVICES, S.L.
> cuya finalidad es la de mantener el contacto con Ud. Si quiere saber
> de qué información disponemos de Ud., modificarla, y en su caso,
> cancelarla, puede hacerlo enviando un escrito al efecto, acompañado de
> una fotocopia de su D.N.I. a la siguiente dirección: GOVERTIS ADVISORY
> SERVICES, S.L. Avda Cortes Valencianas, 58 – 8º - 6ª. 46015 -
> Valencia,  y Paseo de la Castellana, 153, 28045 - MADRID. Asimismo, es
> su responsabilidad comprobar que este mensaje o sus archivos adjuntos
> no contengan virus informáticos, y en caso que los tuvieran eliminarlos.
>
>

Re: Domain Events

[Óscar Bou - GOVERTIS]

Andi sorry. The speller he he ...


> El 10 nov 2017, a las 23:24, Óscar Bou - GOVERTIS  
> escribió:
> 
> 
> 
> 
> Hi Andy.
> 
> Guava event bus implementation is not useful for many use cases, as it 
> enqueues calls, changing the usually expected execution flow.
> That was the initial reason we implemented the Axon event bus support.
> 
> I saw CDI event bus implementation and seems it can handle that use case 
> (assuming it dispatches events as soon as they happen, not queueing them).
> 
> We are not currently planning on using JEE, but just to let you know the 
> original motivation, as I’m seeing you’re testing Guava events working 
> properly instead of Axon (devs would encounter that queueing problem if Axon 
> is not available).
> 
> 
> Regards,
> 
> Oscar
> 
> 
> 
> 
> 
>> El 28 oct 2017, a las 12:40, Andi Huber  escribió:
>> 
>> I just realized, we have Axon as isis/runtime dependency for more than a
>> year now!? (Had thought that was a very recent change in direction.)
>> 
>> So I guess, we may put CDI event processing on the wish-list for now,
>> and support Axon on JEE.
>> 
>> Cheers, Andi
>> 
>>> On 28.10.2017 11:00, Andi Huber wrote:
>>> Hi Dan,
>>> while working on JEE support for Isis, I encountered difficulties with
>>> the Axon framework:
>>> 
>>> Just the first exception thrown (there might be other issues as well)
>>> originates from Axon requesting an EntityManager from JEE, which is not
>>> available out of the box if not configured. (And we don't need to
>>> configure one, because we - as of yet - use JDO.)
>>> 
>>> Following earlier posts on the mailing list, I think we had event
>>> processing using Guava, which worked on JEE containers without issues.
>>> 
>>> CDI (since JEE 6 [1]) provides event processing as well, and Weld [2] which
>>> is the reference implementation of CDI, is now also available for Java
>>> SE. So I guess Weld could be deployed on non-CDI environments to provide
>>> event processing.
>>> 
>>> I'm confident, with some additional investigation, we can use Axon on
>>> JEE, but the question emerges:
>>> 
>>> Are we sure we want to use Axon for event processing, considering that
>>> we have a tendency towards CDI anyway?
>>> 
>>> Cheers, Andi
>>> 
>>> [1] https://docs.oracle.com/javaee/6/tutorial/doc/gkhic.html#gkhih
>>> [2] http://docs.jboss.org/weld/reference/latest/en-US/html/events.html
>>> 
>> 
> 
> 
> 
> Óscar Bou Bou
> Socio - IT & GRC Management Services Director
> m: +34 620 267 520
> s: www.govertis.com e: o@govertis.com
> 
> LinkedIn: https://www.linkedin.com/in/oscarbou
> Twitter:  @oscarbou
> 
> 
> 
> Este mensaje y los ficheros anexos son confidenciales. Los mismos contienen 
> información reservada que no puede ser difundida. Si usted ha recibido este 
> correo por error, tenga la amabilidad de eliminarlo de su sistema y avisar al 
> remitente mediante reenvío a su dirección electrónica; no deberá copiar el 
> mensaje ni divulgar su contenido a ninguna persona.
> 
> Su dirección de correo electrónico junto a sus datos personales constan en un 
> fichero titularidad de GOVERTIS ADVISORY SERVICES, S.L. cuya finalidad es la 
> de mantener el contacto con Ud. Si quiere saber de qué información disponemos 
> de Ud., modificarla, y en su caso, cancelarla, puede hacerlo enviando un 
> escrito al efecto, acompañado de una fotocopia de su D.N.I. a la siguiente 
> dirección: GOVERTIS ADVISORY SERVICES, S.L. Avda Cortes Valencianas, 58 – 8º 
> - 6ª. 46015 - Valencia,  y Paseo de la Castellana, 153, 28045 - MADRID. 
> Asimismo, es su responsabilidad comprobar que este mensaje o sus archivos 
> adjuntos no contengan virus informáticos, y en caso que los tuvieran 
> eliminarlos.
> 
> 

Re: Domain Events

[Óscar Bou - GOVERTIS]

Hi Andy.

Guava event bus implementation is not useful for many use cases, as it enqueues 
calls, changing the usually expected execution flow.
That was the initial reason we implemented the Axon event bus support.

I saw CDI event bus implementation and seems it can handle that use case 
(assuming it dispatches events as soon as they happen, not queueing them).

We are not currently planning on using JEE, but just to let you know the 
original motivation, as I’m seeing you’re testing Guava events working properly 
instead of Axon (devs would encounter that queueing problem if Axon is not 
available).


Regards,

Oscar





> El 28 oct 2017, a las 12:40, Andi Huber  escribió:
> 
> I just realized, we have Axon as isis/runtime dependency for more than a
> year now!? (Had thought that was a very recent change in direction.)
> 
> So I guess, we may put CDI event processing on the wish-list for now,
> and support Axon on JEE.
> 
> Cheers, Andi
> 
> On 28.10.2017 11:00, Andi Huber wrote:
>> Hi Dan,
>> while working on JEE support for Isis, I encountered difficulties with
>> the Axon framework:
>> 
>> Just the first exception thrown (there might be other issues as well)
>> originates from Axon requesting an EntityManager from JEE, which is not
>> available out of the box if not configured. (And we don't need to
>> configure one, because we - as of yet - use JDO.)
>> 
>> Following earlier posts on the mailing list, I think we had event
>> processing using Guava, which worked on JEE containers without issues.
>> 
>> CDI (since JEE 6 [1]) provides event processing as well, and Weld [2] which
>> is the reference implementation of CDI, is now also available for Java
>> SE. So I guess Weld could be deployed on non-CDI environments to provide
>> event processing.
>> 
>> I'm confident, with some additional investigation, we can use Axon on
>> JEE, but the question emerges:
>> 
>> Are we sure we want to use Axon for event processing, considering that
>> we have a tendency towards CDI anyway?
>> 
>> Cheers, Andi
>> 
>> [1] https://docs.oracle.com/javaee/6/tutorial/doc/gkhic.html#gkhih
>> [2] http://docs.jboss.org/weld/reference/latest/en-US/html/events.html
>> 
> 



Óscar Bou Bou
Socio - IT & GRC Management Services Director
m: +34 620 267 520
s:  www.govertis.com  e: 
o@govertis.com 

LinkedIn: https://www.linkedin.com/in/oscarbou 

Twitter:@oscarbou 



Este mensaje y los ficheros anexos son confidenciales. Los mismos contienen 
información reservada que no puede ser difundida. Si usted ha recibido este 
correo por error, tenga la amabilidad de eliminarlo de su sistema y avisar al 
remitente mediante reenvío a su dirección electrónica; no deberá copiar el 
mensaje ni divulgar su contenido a ninguna persona.

Su dirección de correo electrónico junto a sus datos personales constan en un 
fichero titularidad de GOVERTIS ADVISORY SERVICES, S.L. cuya finalidad es la de 
mantener el contacto con Ud. Si quiere saber de qué información disponemos de 
Ud., modificarla, y en su caso, cancelarla, puede hacerlo enviando un escrito 
al efecto, acompañado de una fotocopia de su D.N.I. a la siguiente dirección: 
GOVERTIS ADVISORY SERVICES, S.L. Avda Cortes Valencianas, 58 – 8º - 6ª. 46015 - 
Valencia,  y Paseo de la Castellana, 153, 28045 - MADRID. Asimismo, es su 
responsabilidad comprobar que este mensaje o sus archivos adjuntos no contengan 
virus informáticos, y en caso que los tuvieran eliminarlos.

Re: Domain Events

[Andi Huber]

I just realized, we have Axon as isis/runtime dependency for more than a
year now!? (Had thought that was a very recent change in direction.)

So I guess, we may put CDI event processing on the wish-list for now,
and support Axon on JEE.

Cheers, Andi

On 28.10.2017 11:00, Andi Huber wrote:
> Hi Dan,
> while working on JEE support for Isis, I encountered difficulties with
> the Axon framework:
>
> Just the first exception thrown (there might be other issues as well)
> originates from Axon requesting an EntityManager from JEE, which is not
> available out of the box if not configured. (And we don't need to
> configure one, because we - as of yet - use JDO.)
>
> Following earlier posts on the mailing list, I think we had event
> processing using Guava, which worked on JEE containers without issues.
>
> CDI (since JEE 6 [1]) provides event processing as well, and Weld [2] which
> is the reference implementation of CDI, is now also available for Java
> SE. So I guess Weld could be deployed on non-CDI environments to provide
> event processing.
>
> I'm confident, with some additional investigation, we can use Axon on
> JEE, but the question emerges:
>
> Are we sure we want to use Axon for event processing, considering that
> we have a tendency towards CDI anyway?
>
> Cheers, Andi
>
> [1] https://docs.oracle.com/javaee/6/tutorial/doc/gkhic.html#gkhih
> [2] http://docs.jboss.org/weld/reference/latest/en-US/html/events.html
>