Rickard Öberg wrote:
> Michael Hunger wrote:
>> Another thought on that. We have libraries for every kind of
>> infrastructure out there.
>> Why not just take on the JavaMail API and build an
>> library/entitystore-mail as an example / prototype for qi4j messaging?
>> So we could explore how a generic (composable) message could look like
>> and how the interactions with the differnt entitystores on its way work.
>>
>> Are we talking about pure qi4j messaging or interoperability with the
>> existing messaging systems out there?
>
> Preferably interop with existing systems, like POP/SMTP, XMPP, JMS, etc.
> Mail seems like a good start :-) Hey, it could use the REST stuff even
> since there are connectors in Restlet for messaging systems. As one
> option to do it.
Actually, another route is to make an integration with an ESB-ish
system, which will give "automatic" access to a whole host of messaging
transports.
How about making an EntityStore on top of Apache Camel? Or maybe we're
not talking about an EntityStore, per se, but rather a SideEffect on top
of a normal EntityStore, like the IndexingSideEffect ("when you've done
storing this message, send it through this messaging thingy").
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
