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 >
