Will do! I have a special interest in integration-type stuff. I can imagine using Zest in a DDD sort of way in order to model/implement your business logic. Have you guys done any work with Camel?
If you guys want, I am quite familiar with ActiveMQ. We could implement a JMS-based logging mechanism using AMQ quite easily. Another option might be Akka. Just spit-balling here. On Tue, Mar 31, 2015 at 9:35 AM, Niclas Hedhman <[email protected]> wrote: > Please take note on where you think we need to focus on documentation. It > is big topic and hard to get right. > > Niclas > > On Tue, Mar 31, 2015 at 4:23 PM, James Carman <[email protected]> > wrote: > >> I really need to dig into this code and start playing with it. This >> stuff sounds really cool! >> >> >> >> On Tue, Mar 31, 2015 at 5:44 AM, Stanislav Muhametsin >> <[email protected]> wrote: >> > On 31.3.2015 12:33, Kent Sølvsten wrote: >> >> >> >> Of course there would be challenges to avoid excessive work "when noone >> >> listens" - but application events have been discussed years ago (i think >> >> without being solved) - maybe it is about time to look at that again? >> >> >> > Without knowing the details of this, I would say that if situation when >> "no >> > one is listening" is known at assembly/model creation time, this part >> would >> > be easy for Qi4CS at least. >> > This is because Qi4CS does not generate any code during runtime - it >> > generates the code when one compiles the project that uses Qi4CS. >> > So anything no-op can be very much optimized. >> > > > > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java
