[jboss-dev-forums] [Design of JBoss ESB] - Re: Design of a Content Based Routing Service

[ddunkin]

anonymous wrote : I think it make sense to leave it open-ended. Do you think this would be more work for us?

No, I don't think it will be any more work. I may actually be less work. However, it may just be more abiguous for a user starting out. Good example usage will be important.

anonymous wrote : - will we use a rules repository (will this be a database? And if so will it have it's own schema?) I think you use an xmlfile, read from an url somewhere right?
  | - how do you update the rules? You use an mbean for that right?

The way I implemented it was around deployment units. All the components in my home-grown ESB are EARs or SARs. These deployment units may contain rulesets, in an xml file, that define the routing for those components. I have a deployer that takes these routing-rule files, builds a single rule base for all deployed rulesets, and binds it to a location in JNDI. Updating rules involves redeploying the ruleset that needs to be updated.

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

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980526