Hi Eric,
While utilizing a web console in this way could be a big gain for some
users, others will always prefer automated shell solutions. This will
always be the same fight. :-)
By the way personally I see svn or cvs just as one option how to
implement the versioning backend. The best solution would be to
encapsulate the versioning backend with some kind of API and let the end
user decide/configure where to store the configuration. Valid options
might include any hibernate supported relational database (maybe the
integrated derby database by default), or svn/cvs repositories. I
wouldn't consider svn as a bad solution. This could also be part of an
automated process. Sometimes versioning of configuration could also help
in testing/development environments to hunt some bugs or narrow down
some problems related to certain configurations.
This seems a good point, I think we can easily wrap the svn with our own
versionning, so that all the features including role-back an so forth
will be available to the ESB. At the same time I would like to consider
WSO2 Registry product as the backend implementation for the versionning
because it can also handle all this including role-back if I am not
mistaken :-) . We will be integrating the registry for the next release
of the ESB and we can take this concept of versionning also in to
account with the integration of the WSO2 Registry.
Thanks,
Ruwan
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
