Hi Yasothara, - No need to implement an UI for receiver.. It is dynamically created based on the properties that you defined in receiver core.. - Keep more time for testing (specially for perf test and long running test)
Other than above all looks good. Thanks, Mohan On Thu, Jul 28, 2016 at 10:16 AM, Yashothara Shanmugarajah < yashoth...@wso2.com> wrote: > Hi, > > I have herewith attached the link [1] to my milestone plan for the RabbitMQ > receiver. Please be kind enough to provide necessary feedback, at your > convenience. > > Please let me know if there's anything else that I should work on or that > you think I missed. > > [1] > https://docs.google.com/a/wso2.com/spreadsheets/d/1g9vNrnJ_TbmZROd7SSo-lVKC-F9F9ruPrs0BlCUQCMU/edit?usp=sharing > > Thank you. > > / <http://wso2.com/>Best Regards, > Yashothara.S > Software Engineer > WSO2 > http://wso2.com > > On Wed, Jul 27, 2016 at 9:44 AM, Yashothara Shanmugarajah < > yashoth...@wso2.com> wrote: > >> (adding architecture group) >> >> / <http://wso2.com/>Best Regards, >> Yashothara.S >> Software Engineer >> WSO2 >> http://wso2.com >> >> On Wed, Jul 27, 2016 at 9:40 AM, Yashothara Shanmugarajah < >> yashoth...@wso2.com> wrote: >> >>> Hi all, >>> >>> I have evaluated reusing the axis2 transport and ESB inbound transports. >>> If we use Axis2 transport, we need to change configuration in axis2.xml. So >>> after discussion with Suho and Mohan, I decided to create rabbitMQ from the >>> scratch. >>> >>> Thanks. >>> >>> / <http://wso2.com/>Best Regards, >>> Yashothara.S >>> Software Engineer >>> WSO2 >>> http://wso2.com >>> >>> On Thu, Jul 7, 2016 at 5:04 PM, Sriskandarajah Suhothayan <s...@wso2.com >>> > wrote: >>> >>>> @Yashothara >>>> >>>> Before deciding please evaluate reusing Axis2 and ESB inbound >>>> transports, check for performance (like it always builds the message, etc ) >>>> & usability (like we need a restart if we need to modify the adaptor) >>>> >>>> Regards >>>> Suho >>>> >>>> On Thu, Jul 7, 2016 at 3:56 PM, Mohanadarshan Vivekanandalingam < >>>> mo...@wso2.com> wrote: >>>> >>>>> Anyway, if you guys have any issues on using axis2 transport for >>>>> this.. Then please add them in strategy mail thread [1] as well.. We had a >>>>> discussion on this already but haven't seen any concerns on using axis2 >>>>> transport.. >>>>> >>>>> [1] RabbitMQ into CEP (was: Re: URGENT: Fw: Potenial use of WSO2 for >>>>> Global Upstream Oil Industry) >>>>> >>>>> Thanks, >>>>> Mohan >>>>> >>>>> >>>>> On Thu, Jul 7, 2016 at 3:44 PM, Yashothara Shanmugarajah < >>>>> yashoth...@wso2.com> wrote: >>>>> >>>>>> +1 >>>>>> >>>>>> Best Regards, >>>>>> Yashothara.S >>>>>> >>>>>> Software Engineer >>>>>> WSO2 >>>>>> >>>>>> >>>>>> On Thu, Jul 7, 2016 at 3:32 PM, Sriskandarajah Suhothayan < >>>>>> s...@wso2.com> wrote: >>>>>> >>>>>>> +1 >>>>>>> >>>>>>> Regards >>>>>>> Suho >>>>>>> >>>>>>> On Thu, Jul 7, 2016 at 3:31 PM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> I guess we can check for possibilities of reusing inbound endpoint >>>>>>>> code here. This way we can identify what is missing to do this from >>>>>>>> both >>>>>>>> sides. WDYT? >>>>>>>> >>>>>>>> On Thu, Jul 7, 2016 at 2:48 PM, Sriskandarajah Suhothayan < >>>>>>>> s...@wso2.com> wrote: >>>>>>>> >>>>>>>>> It's better if we can avoid using Axis2 Transport if we need to >>>>>>>>> restart CEP/DAS for each and every changes. >>>>>>>>> Please verify. >>>>>>>>> >>>>>>>>> Regards >>>>>>>>> Suho >>>>>>>>> >>>>>>>>> On Thu, Jul 7, 2016 at 2:14 PM, Yashothara Shanmugarajah < >>>>>>>>> yashoth...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Hi All, >>>>>>>>>> >>>>>>>>>> I have planned to develop RabbitMQ Input Adapter (Receiver) for >>>>>>>>>> CEP. RabbitMQ task is getting the messages and forward it to the >>>>>>>>>> receiver. A "Consumer (C)" is a program that mostly waits to receive >>>>>>>>>> messages. Queue is the one which stores messages for a sometime. >>>>>>>>>> Exchange >>>>>>>>>> on one side it receives messages from producers and the other side it >>>>>>>>>> pushes them to queues. The exchange must know exactly what to do >>>>>>>>>> with a >>>>>>>>>> message it receives. As I am going to do Input Adapter I have to >>>>>>>>>> focus on >>>>>>>>>> Consumer part. RabbitMQ receiver have to connect to broker and >>>>>>>>>> listen for >>>>>>>>>> messages from particular queue and exchange. I planned to use Axis2 >>>>>>>>>> transport as CEP is integrated with Axis2 Transport. I planned to use >>>>>>>>>> binary message builder and after that read the message and create the >>>>>>>>>> internal event format. >>>>>>>>>> >>>>>>>>>> Your comments and suggestions are highly appreciated. >>>>>>>>>> >>>>>>>>>> Thanks. >>>>>>>>>> Best Regards, >>>>>>>>>> Yashothara.S >>>>>>>>>> >>>>>>>>>> Software Engineer >>>>>>>>>> WSO2 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> *S. Suhothayan* >>>>>>>>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>>>>>>>> *WSO2 Inc. *http://wso2.com >>>>>>>>> * <http://wso2.com/>* >>>>>>>>> lean . enterprise . middleware >>>>>>>>> >>>>>>>>> >>>>>>>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>>>>>>> http://suhothayan.blogspot.com/ >>>>>>>>> <http://suhothayan.blogspot.com/>twitter: >>>>>>>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | >>>>>>>>> linked-in: >>>>>>>>> http://lk.linkedin.com/in/suhothayan >>>>>>>>> <http://lk.linkedin.com/in/suhothayan>* >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> Malaka Silva >>>>>>>> Senior Technical Lead >>>>>>>> M: +94 777 219 791 >>>>>>>> Tel : 94 11 214 5345 >>>>>>>> Fax :94 11 2145300 >>>>>>>> Skype : malaka.sampath.silva >>>>>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>>>>>> Blog : http://mrmalakasilva.blogspot.com/ >>>>>>>> >>>>>>>> WSO2, Inc. >>>>>>>> lean . enterprise . middleware >>>>>>>> http://www.wso2.com/ >>>>>>>> http://www.wso2.com/about/team/malaka-silva/ >>>>>>>> <http://wso2.com/about/team/malaka-silva/> >>>>>>>> https://store.wso2.com/store/ >>>>>>>> >>>>>>>> Save a tree -Conserve nature & Save the world for your future. >>>>>>>> Print this email only if it is absolutely necessary. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *S. Suhothayan* >>>>>>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>>>>>> *WSO2 Inc. *http://wso2.com >>>>>>> * <http://wso2.com/>* >>>>>>> lean . enterprise . middleware >>>>>>> >>>>>>> >>>>>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>>>>> http://suhothayan.blogspot.com/ >>>>>>> <http://suhothayan.blogspot.com/>twitter: >>>>>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | >>>>>>> linked-in: >>>>>>> http://lk.linkedin.com/in/suhothayan >>>>>>> <http://lk.linkedin.com/in/suhothayan>* >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *V. Mohanadarshan* >>>>> *Associate Tech Lead,* >>>>> *Data Technologies Team,* >>>>> *WSO2, Inc. http://wso2.com <http://wso2.com> * >>>>> *lean.enterprise.middleware.* >>>>> >>>>> email: mo...@wso2.com >>>>> phone:(+94) 771117673 >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> *S. Suhothayan* >>>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>>> *WSO2 Inc. *http://wso2.com >>>> * <http://wso2.com/>* >>>> lean . enterprise . middleware >>>> >>>> >>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >>>> http://lk.linkedin.com/in/suhothayan >>>> <http://lk.linkedin.com/in/suhothayan>* >>>> >>> >>> >> > -- *V. Mohanadarshan* *Associate Tech Lead,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com <http://wso2.com> * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
