Hi All,

Following points were raised & discussed at the review :-


   1. Properties view should reveal when double clicking an element on the
   esb editor
   2. Create endpoint menu should give other address / wsdl endpoint options
   (capp).
   3. Get rid of default configurations of an endpoint / sequence (because
   they are understood and adding them are just making the configuration
   longer)
   4. Endpoint error codes should be hard-coded (because the error codes are
   well knowns and they do not change) and allowed as checked boxes.
   5. There is no such thing as endpoint timeout enable / disable. Get rid
   of that true / false field and show the timeout properties always.
   6. Check “phsyco path” eclipse plugin to be used as an xpath editor for
   esb editor or write our own simple xpath editor.
   7. In the tree view sequences / endpoints should show its caption as
   “<sequence/endpoint_name> [type]”
   8. Tighten capp - esb editor integration - eg: sequences send mediator
   pointing to endpoints in the same project.
   9. How to specify sequences send mediator pointing to a endpoint which
   would be deployed in a registry later.
   10. Would be nice to have a proxy service as a flow rather than a tree
   kind of view (Graphical Editor) - It’s hard to represent a proxy service
   using a tree view..
   11. Rather than using “Anonymous” word use “inline”.
   12. Try adding tool-tips as help.
   13. Adding “description” tag for all types (mediators, sequences, etc)
   14. By default the “registry” entry should come to the synapse
   configuration
   15. Add a jira about the comment vanishing when editing esb
   configurations and say its a known issue.
   16. Property mediator “property name” should show well known property
   names. (may be through a dialog where the property name and the associated
   descriptions are shown), but user should be able to type a custom property
   name also.
   17. Name / attribute value validation
   18. would be nice to have a script mediator source code editable using
   the script editor inside eclipse.
   19. Try to have local entries for carbon studio 1.0 release.
   20. Have a preference page to allow configuring default namespace & use
   the synapse trunk (current) namespace by default.

(Anything missed?)

We plan to address as much issues as we can before the carbon studio 1.0
release. In the mean time if you have further comments on esb editor, please
let us know.

Thanks for the feed back from esb folks and all other participants!

WSO2 Tooling Team
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to