Kasun, miyuru can we chat sometime and send mail/ add redmine items. --Srinath
On Sat, Sep 21, 2013 at 7:49 AM, Sanjiva Weerawarana <[email protected]>wrote: > Great feedback! > > For adding stuff to admin console .. generally I'm -1 on adding developer > stuff to the admin console. We've in fact been moving more and more towards > making it more of just an admin console and not a developer tool. > > Added Jackie too for doc updates. Jackie please review mail from Srinath > below if you haven't seen it already. > > Sanjiva. > > > On Tue, Sep 17, 2013 at 9:40 PM, Srinath Perera <[email protected]> wrote: > >> I did worked with ESB lot in a previous week and have some feedback >> >> 1. Now Docs are pretty good, we managed without having to ask ESB >> team much even though none of us work work with ESB day to day >> 2. Descriptions need few samples - currently often each mediator has >> one example. But if it can be used in different ways, it helps to have few >> examples. Ant manual does this very well. >> 3. It is bit tricky to find out where some stuff are. I think overall >> section structure can improve I think. >> >> Payload mediator is a life saver, and it make the expereince very neat. >> But still there are many samples that uses enrich which can be done with >> payload. >> >> Need to update the samples to use new things like payload medatior and >> receive method in <send> for service chaining >> >> Still one of the main challenge is debugging. I think we can improve >> experience by adding more logging. >> >> - improve <log .. > so we can add log messages without taking too >> much real state of the program (I sent a mail to arch@) >> - Add a mediator like env command that let us print all properties at >> a given point >> - Another idea is to add an mediator to hold execution and may be let >> interactive control and inspection for debugging via a admin service call >> (mapped as scripts) >> >> We need a list of all supported xpath functions in one place(is it >> already there?) >> >> Our aggregate is implicitly bound to a closest clone/ iterate. If you >> think is language terms, it actually solve three problems. >> >> 1) create new threads >> 2) iterate messages >> 3) wait for and process things (join threads) >> >> As all three cases are linked, sometime it is tricky to use aggregate and >> iterate. Think we can improve things. I will send another mail. >> >> Few other things >> >> 1. I think we need a say to do things atomically in ESB. Something >> like synchronised block or check and set operation . >> 2. I think we need support for regex extraction for text manipulation >> 3. I think we need support for List templates from Admin console UI >> >> >> WDYT? >> >> --Srinath >> >> -- >> ============================ >> Srinath Perera, Ph.D. >> Director, Research, WSO2 Inc. >> Visiting Faculty, University of Moratuwa >> Member, Apache Software Foundation >> Research Scientist, Lanka Software Foundation >> Blog: http://srinathsview.blogspot.com/ >> Photos: http://www.flickr.com/photos/hemapani/ >> Phone: 0772360902 >> > > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 > 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > Lean . Enterprise . Middleware > -- ============================ Srinath Perera, Ph.D. Director, Research, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
