"timfox" wrote : BTW, any reason why you're not just using MDBs?

Hmm Yes!

As I said I have a Topic where messages comes in. These must be processed and 
send to a queue for each connected system. 
I don't want so hardcode his so it must be self maintaining.
My Idea: Have a service which starts or stops durable subscribers on a topic 
based on registered servers...
The Order is relevant so I can only have one instance per connected Server.
Any small hints how I can handle this with MDB? I would prefer this way because 
of DLQ handling and transactions...

In the end I need a scaleable system which consumes messages from a topic and 
send the processed data (different for each server) to connected 
servers/outgoing queue (which register themself).

One Idea is to have an MDB which handles the message for all servers, but this 
is not that scaleable, because the order is relevant so I only can have one MDB 
instance...
 


"[EMAIL PROTECTED]" wrote : <config-property 
name="Strict">False</config-property> 
Thx for this hint but I try be be spec compliant... 



/MDB consuming messages


View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994137#3994137

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994137
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to