I'm not a camel expert.
On Feb 18, 2010, at 12:22 PM, Mario Zsilak wrote:
Hi,
I just took a glance at camel.apache.org but I spotted the following
statement:
<!-- start -->
Apache Camel can be used as a routing and mediation engine for the
following
projects:
* ...
* Apache ActiveMQ which is the most popular and powerful open
source
message broker
* ...
<!-- end -->
I guess that means that other message brokers (including commercial
ones)
are not supported within Apache Camel?
I think it means that the camel integration is shipped with those
projects and is not a comment on the ease of using camel with other
message systems. For instance I doubt tibco is going to ship camel
any time soon, but I have the impression that integrating with a jms
provider is basically a matter of configuration.
In that case I would be happy to see some kind of abstraction layer
so that
others (like me) can implement their own stuff ...
Where would this abstraction layer go, and what would it abstract?
What would you substitute for what?
david jencks
Apart from my requirements I guess most people don't need these
(very nice)
features at all.
However if there is a performance gain, especially when using only 1
server/james-instance, we should go for it.
Kind regards,
Mario
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]
]
Im Auftrag von Norman Maurer
Gesendet: Donnerstag, 18. Februar 2010 16:38
An: James Developers List
Betreff: [PROPOSAL] Using Camel as replacement of MailProcessor /
SpoolManager
Hi all,
in the past Stefano told me about his Idea of using camel within
james
(it was just an idea and he had no closer look yet). The last days I
did some research about camel (camel.apache.org) and I think he is
right.
So me plan is:
* Write a Consumer for our SpoolRepository which would fire of an
exchange object when a mail object is ready for processing
* Write a RouteBuilder which will create a route for every configured
processor and so replace the MailProcessor stuff at all. The route
would just to the Matcher, Mailet processing
With using Camel it would be possible (just an example) to load
balance between routes, throttle processing of low priority routes,
process mail on other server etc. I think this would push James
extensibility to a new level, and will allow developers to customize
james more easy.
WDYTH ?
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
