On Tue, Aug 6, 2013 at 11:04 AM, Srinath Perera <[email protected]> wrote:
> There are some categories defined in EIP http://www.eaipatterns.com/ > > Some classes are > > Filters > Message routers > Send message out - e.g. send, callout, send event > transformations > message builders - may be part of transformation > invoke java/ custom functions > I sent this note to the other thread: On categorizing, that needs to come as a design decision from ESB and mediation experts collectively. What we have right now is only an alphabetical ordering in DevS. That is useful only for some cases. But even on the classification on the ESB UI is not right, as what we understood when we looked at them yesterday. For e.g "Advanced" category seemed to be the place where most useful yet complex mediators are located, and "advanced" has no meaning. +1 for using EIP semantics, for e.g. clone, aggregator and splitter should be in message routing category of EIP. But we need the full list be properly broken down into categories please... > > > > > > On Mon, Aug 5, 2013 at 9:00 PM, Harshana Martin <[email protected]> wrote: > >> Hi Viraj, >> >> +1 >> >> Thanks and Regards, >> Harshana >> >> >> On Mon, Aug 5, 2013 at 3:13 AM, Viraj Rajaguru <[email protected]> wrote: >> >>> Hi, >>> >>> Currently in ESB Graphical Composer tool, there is only one category for >>> all the mediators in tool palette. Mediators are arranged in >>> an alphabetical order to increase the efficiency of searching for a >>> mediator. >>> >>> But while having a discussion regarding the editor with Samisa, we >>> realized that existing categorization (one category with alphabetical >>> order) would be helpful if user knows the name of the mediator exactly. So >>> existing tool palette will not guide a new user appropriately. >>> >>> As a solution, it is proposed to have a proper categorization for the >>> mediators in the tool palette. For an example we can categorize mediators >>> into "Filters", "Extensions" etc. as management console does. So users can >>> easily search the mediators in relevant category since category name is >>> giving a general idea about that group of mediators. >>> Another advantage of using categorization is we can apply different >>> color themes for different categories. It will increase the readability of >>> the diagram. >>> >>> WDYT ? >>> >>> >>> Thanks, >>> Viraj. >>> >>> -- >>> Viraj Rajaguru >>> Software Engineer >>> WSO2 Inc. : http://wso2.com >>> >>> Mobile: +94 77 3683068 >>> >>> >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> >> Harshana Martin >> Associate Technical Lead >> WSO2 Inc. : http://wso2.com >> >> Mobile: +94 775 998 115 >> Profile: https://www.google.com/profiles/harshana05 >> Blog: http://harshana05.blogspot.com >> Twitter: http://twitter.com/harshana05 >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > ============================ > Srinath Perera, Ph.D. > http://people.apache.org/~hemapani/ > http://srinathsview.blogspot.com/ > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
