Hi Eric,
Let me comment on some of your points keeping the other points to Paul
or Asankha :-),
Hubert, Eric wrote:
Hi ,
thanks for your official announcement of your first draft of the ESB roadmap. It reads quite interesting. Of course I have some questions and comments. ;-)
What about the integration of the WSO2 registry and the ESB? I haven't read something about it in your release plan. Nevertheless I have seen some commits in that area.
Yes. WSO2 Registry has been already integrated with the ESB on the svn
trunk. So it should not go to the Road Map I think.
We would be very interested to be able to model the service dependencies
(including service versions) as our producers do face some problems in that
area. On the other side I'm not sure if the versioning support of the WSO2
registry does offer the same functionality/flexibility one has in using just
plain synapse.xml and cvs/subversion or any version control. In order to
rollback to an old set of configuration I simply need to execute a script to
check out the last version from the repository and restart the cluster. Does
the WSO2 registry supports some versioning over the whole content (not only
single entries)? Or would that mean to backup a database and do a restore?
WSO2 Registry supports entries versioning and collection versioning as
well. You don't have to mess with the database to revert to a earlier
version, that functionality is embedded into the WSO2 Registry.
Will the graceful shutdown support incl. some central storage of all cluster members as well as shell scripts for operational purposes or do we need to write something around the JMX support in order to make this more "admin friendly"?
Do you plan to extend the number of mediators shipped with the distribution (including UI support)? For example the Route-Mediator from Ruwan seems to be very flexible and useful.
I think Router is a core mediator and we should include that, for the
next release with UI. (Well, that is my personal feeling)
Anyhow I have a question regarding the configuration UI. Is this meant for education purposes only or do you expect any of your users to use this for real life scenarios? I mean it really looks great, but is not very suitable if the number of "object/elements" in each area reaches real life dimensions.
Just to give you one example. The UI of the switch mediator wastes a lot of
space. On field for the expression and below a simple table with two columns
(value and endpoit/sequence) would be more sufficient.
Do you plan some improvements in that area or is the UI only meant as an
example how one could visualize the config?
The point
"Better pagination, searching/filtering and ordering of the service, endpoints and sequence list and statistics"
gives some hope you are planning enhancements for the 2.0 release. This is one
point were I really would love to see some touch-up. Right now it is more
likely we will use the plain xml-file approach.
We expect the configuration UI to be used to create the real life
scenarios, but I must agree on the fact that it needs improvements and
we will be doing a major UI improvement with the 2.0 release.
Thanks,
Ruwan
Regarding statistics I would see another business requirement. Currently the user has only some kind of "snapshot" statistics. You create a service and the counter starts. As far as I know you are neither able to reset specific endpoints/service, nor to see some trend information (process of time). But this is very important, if you want to make a statement about the usage of your services. Also a last access time (probably easy to add) would help to identify services which are not used and might be taken offline.
>From the research area the following points sound interesting:
"Raise Alerts from mediation, and provide ability to view Alerts from monitoring
console"
Does this go into the direction of defining some SLA and reporting violations?
This would be a really useful feature.
"Enhanced JMX reporting and Cluster management"
In that area you seem to be on a good way. Going ahead in that direction would
be fine as this is a need probably many customs will express.
Keep up the good work guys. I hope some of my feedback is useful to further improve this product!
Regards,
Eric
________________________________
Von: [EMAIL PROTECTED] im Auftrag von Paul Fremantle
Gesendet: Fr 18.04.2008 14:52
An: [email protected]; esb >> WSO2 ESB User Mailing list
Betreff: [esb-java-dev] ESB roadmap published
Asankha has posted our first draft of the ESB roadmap here:
http://wso2.org/wiki/display/esbjava/WSO2+Enterprise+Service+Bus+Roadmap
Comments are welcome!
Thanks
Paul
--
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair
VP, Apache Synapse
Office: +44 844 484 8143
Cell: +44 798 447 4618
blog: http://pzf.fremantle.org <http://pzf.fremantle.org/>
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
------------------------------------------------------------------------
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
