Hi, When we are going to implement reverse engineering support, the main issue is the layout management of the diagram as we are handling many mediators in a single compartment. As a solution we thought of using grouping mechanism for the proxy services (A proxy service will have a certain group box and relevant mediators and endpoints goes in to that group box.). This will help us to manage the layout to some extent as this will split the whole diagram in to manageable sections. If we would success with this approach we can give the reverse engineering support for the initial release.
Thanks, Viraj. On Mon, Feb 6, 2012 at 7:22 AM, Samisa Abeysinghe <sam...@wso2.com> wrote: > > > On Sun, Jan 29, 2012 at 6:41 PM, Chathuri Wimalasena <chath...@wso2.com>wrote: > >> We still do not have the reverse engineering support since it is >> technically quite hard. > > > > Why is that so hard? > > In the Graphic first model, we have: > > Graphic -- represents --> Object Model -- serialize --> XML model > > In the reverse directions we have: > > XML model -- de-serialize --> Object Model -- represents --> Graphic > > If the design is right, I see no issues doing this. > > >> At the moment, we are focusing on completing the mediators and improving >> look and feel of the editor. >> >> Review is scheduled for this Wednesday (01/02/2012) and we will be able >> to give a pack for testing after that. At the moment, this editor is not >> being connected with C-App concepts (i.e it is there as a separate feature >> where users can create a synapse configuration). >> >> Regards, >> Chathuri >> >> >> >> On Sun, Jan 29, 2012 at 4:21 PM, Viraj Rajaguru <vi...@wso2.com> wrote: >> >>> Hi, >>> >>> Fixes for the above mentioned issues will be available in "Overall >>> Milestone Plan CS 2.0.0" [1]. Some fixes are already done. >>> >>> We do not have the reverse engineering support yet. >>> >>> We are supporting following mediators. >>> >>> - Log Mediator >>> - Drop Mediator >>> - Property Mediator >>> - Enrich Mediator >>> - Send Mediator >>> - Filter Mediator >>> - Switch Mediator >>> - XSLT Mediator >>> - Fault Mediator >>> - Header Mediator >>> - DBLookup Mediator >>> - DBReport Mediator >>> - Clone Mediator >>> - Iterate Mediator >>> - Aggregate Mediator >>> - Callout Mediator >>> - Transaction Mediator >>> - RMSequence Mediator >>> >>> And also graphical implementation of around 12 new mediators have been >>> done. Only serialization logic has to be implemented for them. >>> >>> >>> Thanks, >>> >>> [1] >>> https://docs.google.com/a/wso2.com/document/d/1gTLfLBuEphtHesJf_eSyHNLcisrogEW8Aw4v-2R-iFQ/edit?hl=en_US >>> >>> >>> On Sun, Jan 29, 2012 at 7:22 AM, Samisa Abeysinghe <sam...@wso2.com>wrote: >>> >>>> What is the ETA for these fixes? In other words, in which milestone >>>> would these fixes be available? >>>> >>>> Do we have reverse engineering support now? Meaning, can I edit the >>>> source and it will reflect the changes in the graphical view. >>>> >>>> How many meadiators are supported? >>>> >>>> What is the plan for testing? >>>> >>>> On mediators, Jan 25, 2012 at 9:53 AM, Viraj Rajaguru >>>> <vi...@wso2.com>wrote: >>>> >>>>> Hi, >>>>> >>>>> We had a discussion on ESB Graphical Editor with Hiranya. In this >>>>> discussion we figured out how to overcome existing issues in the editor. >>>>> Followings are the proposed solutions. >>>>> >>>>> - We are not going to represent Local Entries graphically inside >>>>> the editor, Instead we put them on the tool palette.Then user can add >>>>> them >>>>> to relevant mediators using the context menu. >>>>> - And also we can add defined sequences to "receive" attribute in >>>>> the "Send Mediator" using the context menu as above. It is not >>>>> necessary to >>>>> represent this relationship in graphically. >>>>> >>>>> And also following issues were recognized in this discussion. >>>>> >>>>> - When we add a new Sequence, a dialog box should not be appeared >>>>> to request a name for sequence. >>>>> - In Failover endpoint, Loadbalance endpoint, Switch mediator and >>>>> Clone mediator, there should not be an option to add output connectors >>>>> manually.It should be automated. >>>>> - File name should be appeared in the editor header. >>>>> - Defined endpoints should also go to the pallet as re-usable >>>>> components. >>>>> - Endpoints in the border should be handled in a better way. >>>>> - When open the sequence editor diagram, area for the diagram >>>>> should be auto generated. >>>>> - Name of the sequence should be displayed in the top of the page >>>>> as well as in the sequence. >>>>> - Name of the mediators and endpoints should be appeared in their >>>>> figure. >>>>> - Mediator grouping should be added. >>>>> - A suitable extensions should be used for ESB Graphical editor >>>>> files and for Sequence editor files. >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> >>>>> On Tue, Jan 24, 2012 at 12:18 PM, Viraj Rajaguru <vi...@wso2.com>wrote: >>>>> >>>>>> Hi , >>>>>> >>>>>> I tried to generate a Sample Synapse Configuration (See attached file >>>>>> "Synapse Configuration - Example 1.txt") using the ESB Graphical editor. >>>>>> There were some issues while design the diagram. >>>>>> >>>>>> - How can we represent the Local Entry graphically ? >>>>>> - Send mediator has only input connector and output connector >>>>>> (See attached "Send_Mediator.png"). How can we represent the value of >>>>>> the >>>>>> "receive" attribute in Send mediator.(For a example, <send >>>>>> receive="geoResponseSeq"> .In this case "geoResponseSeq" is a defined >>>>>> sequence.How can we represent this relationship between "sequence" and >>>>>> "Send mediator" inside the graphical editor.) ? >>>>>> >>>>>> Please comment on these issues if you have any idea. >>>>>> >>>>>> Screen shots for Relevant Diagram for the "Synapse Configuration - >>>>>> Example 1" and the generated Synapse configuration are attached with >>>>>> this. >>>>>> >>>>>> >>>>>> Thanks, >>>>>> >>>>>> -- >>>>>> *Viraj Rajaguru* >>>>>> email: vi...@wso2.com <email%3avi...@wso2.com> cell: +94 77 3683068 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Viraj Rajaguru* >>>>> email: vi...@wso2.com <email%3avi...@wso2.com> cell: +94 77 3683068 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Carbon-dev mailing list >>>>> Carbon-dev@wso2.org >>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>> >>>>> Thanks, >>>> Samisa... >>>> >>>> Samisa Abeysinghe >>>> VP Engineering >>>> WSO2 Inc. >>>> http://wso2.com >>>> http://wso2.org >>>> >>>> >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> >>> -- >>> *Viraj Rajaguru* >>> email: vi...@wso2.com <email%3avi...@wso2.com> cell: +94 77 3683068 >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Chathuri Wimalasena >> Senior Software Engineer; WSO2, Inc.; http://wso2.com/ >> email: chath...@wso2.com; phone: +94 772 608 596 >> blog: http://chathuriwimalasena.blogspot.com/ >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Viraj Rajaguru* email: vi...@wso2.com <email%3avi...@wso2.com> cell: +94 77 3683068
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
