Dispatch messages system design consult

Question

I have a design question and would like to have suggestions.
I am using Weblogic 11g, EJB3.0 , Weblogic JMs
I have a system which it's target to retrieve and dispatch messages to couple of resources(databases).
Each message contain information and target database key.
So here is an flow example:
I get from web service a message and key target. I parse the message and dispatch it to the right database via the key target.
There is a possibility that a message will contain more then one target database.(for example the key 'all' means that I should dispatch to all databases.
If Insert is failing in one of the resources a rollback will occurred and I a re-try will re-execute the whole operation.
So now this is my issue:
Should I make the number of the queues as the number of my resources? (and dedicated each Queue to a specific resource)
(In this case I parse each message and just send it to the right queue while an MDB will listen and do the insertion to the right database)
If I do it that way I wont be able to make it dynamic, Meaning each time a new resource will need to be added/removed in the future I will need to open the code and make the right changes.
What you desgigners think? How could I implement it better dynamiclly?
thanks for your help,
ray

Answer 1

ok, suppose I have a READ_STATUS field, how would you store it then?? You have to keep track of ALL your users and that for all your messages. Suppose you have 25000 users? What I do now is store a comma delimited string for all unread users. So, in a new message, I create a string with the id's of all current users, like 1,2,3,4....24999,25000. In Flex, I convert this string to an array, which makes it easy to delete the current user's id and then write this string back to the db. Something inside me tells me that there have to be more effecient ways to do this...?
BTW, I don't use ORM, that's just the problem. If I have a person with several addresses, I keep a seperate table for the addresses and retreive those before sending a single person value object back to Flex. As it's not likely that a person would have more than 100 addresses (unless he is a criminal or Michael Jackson) this method is fine, but with storing thousands of user id's per message, well... suggestions?
Dany