Hi Hiranya, Many thanks for this review, we're currently working on fixing the most prominent issues (some of which you have raised) and then plan to move into others.
- Asiri On Tue, Sep 21, 2010 at 2:42 PM, Hiranya Jayathilaka <[email protected]>wrote: > Some more points based on my personal experience with the plugins: > > 0. Please update the documentation and clearly mention that the > installation procedure can take a while > 1. Underscore is not allowed in project names. Why? > 2. What is the empty rectangle just below the text "Existing Artifacts"? > - Ok got it :) > - But when there is nothing to display in this area better to show a text > message saying "No artifacts added yet" or something like that > - Also increase the default height of this panel (it looks more like a > text box otherwise) > - Same applies for dependency view panels > 3. Selecting an endpoint or a sequence on the UI should automatically > expand the properties tab (if it's hidden or collapsed) > 4. Endpoint message format dropdown > - Soap 1.1, Soap 1.2 should be changed to SOAP 1.1 and SOAP 1.2 > respectively > 5. For boolean parameters (tracing, stats etc) provide checkboxes instead > of dropdowns > 6. Need tooltip texts for all the important properties in the properties > window > 7. Endpoint properties tab > - Rename 'Basic' to 'General' > - Rename 'Suspend progression factor' to 'Suspend duration progression > factor' > 8. Ability to create endpoints of different types is crucial. This should > be a blocker for this release. Address endpoints and WSDL endpoints are the > mostly used endpoint types. Default endpoint is used only under very > specific conditions. > 9. When you open an endpoint, the endpoint object should be already > selected and the properties tab should be opened up - Same goes for > sequences > 10. Better use lower case letters for directory names (Artifacts -> > artifacts) > 11. Sequence editor > - For the root sequence object show 'Add Mediator' instead of 'New Child' > - When changing to the source view from the design view without saving all > the changes, the unsaved changes do not show up in the source view - It > would be great if we can fix this > - XSLT mediator source xpath null? > - Please fix the serilizers to serialize only the required elements. In > case of endpoints they serialize a whole bunch of unwanted stuff thus > resulting in rediculously long configuration files > - Hitting ctrl+s while a proeprty in the properties window is selected do > not save the parent configuration > - Arrange the mediators in the menus in alphabetical order (this should be > done in the web UI too) > - We need unique icons for each mediator (Currently there are some > overlaps) > - How do I associate the 'onError' sequence with a sequnce > 12. When a new proxy service is created it contains an in-sequence with a > log mediator. This is not necessary. > - IMO this UI is not good enough. A proxy service cannot be modelled as a > tree. But since you are already working on a different graphical view for > proxy services we can live with this for the moment. > - When pointing to a named reference (sequence or endpoint) should > display the existing artifacts in a dropdown for the user to select from > - In case of WSDLs we need to think of a way to tie in with the GReg gar > files concept (future work) > 13. We need local entry support asap (I wouldn't even mind considering > this as a blocker for this release). Otherwise one must always use the > registry to store XSLTs etc > 14. Created a proxy service named proxyservice1 and it was saved to a file > named proxyservice1.xml. Then I renamed the file to proxy_service1.xml. > Opened up the corresponding artifact.xml but the path to deployable field > has not been updated. Similarly I renamed the proxy service itself. Still > the name displayed in the artifact.xml was not changed. I think the same > happens with other types of artifacts. > > Thanks, > Hiranya > > On Tue, Sep 21, 2010 at 10:48 AM, Saminda Wijeratne <[email protected]>wrote: > >> 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 >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
