Re: [ebxmlms-develop] Beyond hermes 1.0

[Philipp B. <pb...@we...>]

Hi Patrick,

Please let me tell you my point of view about hermes and jms.
I like the idea of Ronald to see the monitors of hermes as a plugin. I think it is not much work to create an interface for the monitors and extract it to a plugin that can be easily configured. With a class (MessageServiceHandler) that has more then 5000 lines of code it would be a good option.

But to make the other way more flexible is much more complicated. I see the problem in the fact that hermes is not designed to push the message to the client. I have problems to find the right way to modify hermes for my needs.

How I told in a post before, my modified hermes put all messages to a queue. But in my opinion this is a very dirty solution. My hermes modifications have dependencies to jms classes. The goal would be that only a plugin has these dependencies.

My whish is that it would be possible to configure in msh.properties.xml the plugin and the fitting ApplicationContext.

Hermes is a great product, please see this mail as feedback of an user. And if you know a way how I can reach my goal please let me know.

Regards Philipp

____________________________________________________
Aufnehmen, abschicken, nah sein - So einfach ist 
WEB.DE Video-Mail: http://freemail.web.de/?mc=021200