[
http://jira.jboss.com/jira/browse/JBESB-417?page=comments#action_12359689 ]
Burr Sutter commented on JBESB-417:
-----------------------------------
Concerning the dev, test, staging, production item...
That is more a matter of making sure the steps involved in moving a "project"
out of dev and into production are at least tested/well documented. In the future there
might be a central repository that is responsible for this type of thing.
For instance, if I need to update 2 ESBs with the same services/archives together, can I
simply have a shared file system between the 2 servers? Can I ask one ESB server and all
its associated services to "stand down" in which case it no longer consume
messages and all new messages would be routed to other ESB servers that hosted those same
services (matched by category and name)?
There may be more questions like this.
Service lifecycle
-----------------
Key: JBESB-417
URL:
http://jira.jboss.com/jira/browse/JBESB-417
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Management, Rosetta
Reporter: Mark Little
Assigned To: Kevin Conner
Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2
Both simple lifecycle on single bus as well as dev, test, staging, production management
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira