From: ddegroff <do-...@jb...> - 2006-06-22 15:38:29
|
"ddossot" wrote : "Hot redeploy" is probably an overstatement from my side. | | Say, the contract of an outbound service has changed and you want to modify the transformation chain to be able to keep routing messages to it. You would then have to deploy a new config without stopping the whole service. | | Sorry for using the wrong terminology. I'm not sure I would know the "correct terminology" myself in this case, David. But, to introduce another practical example of what I believe this thread is discussing: Suppose you are exchanging a format (let's just say X12 EDI) with a trading partner external to the ESB. The trading partner (a major player who dictates what "standard" shall be used to communicate with them, "or else") revises their "standard" as of a certain date in the future. It would be wise to employ versioning, including date/time effectivity, so that development and testing could ensue prior to the "deadline", and deployment of the new version could occur even prior to the "go date". Once the effective date passes, the transformation would use the "new" format in compliance with the trading partner's demands. I'm working on yet another example for you, Tom. I wanted an opportunity to work through your tutorial beforehand. Thanks all, Dave De View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952720#3952720 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952720 |