Gayan: Was there any reason for generating a client id for subscribers and setting a fixed value for publishers?
TopicSubscriber.doSubscribe(): MqttClient mqttClient = MQTTConnector.getMQTTSubClient(Util.getRandomString( 5)); On Fri, Nov 7, 2014 at 1:17 PM, Isuru Haththotuwa <isu...@apache.org> wrote: > > > On Fri, Nov 7, 2014 at 12:59 PM, Isuru Haththotuwa <isu...@apache.org> > wrote: > >> >> On Fri, Nov 7, 2014 at 12:52 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> >> wrote: >> >>> I got containers to be created. >>> But didn't get the member started event. Either agent is not sending or >>> CC is not receiving. Looking into it currently. >>> >> I'm seeing this issue as well. The agent is sending the events, but >> Stratos is not receiving them. Trying with a simple mqtt client now. >> > In [1], we are using the client id in mqtttopic.properties file as it is > and using it to start the MQTTClient. However, in the wiki it says that > client id should be unique across all publishers [2]. I might be missing > something here, but is this case handled? > > [1]. org.apache.stratos.messaging.broker.connect.MQTTConnector > > [2]. > http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#MqttClient(java.lang.String, > java.lang.String) > > >> >>> On Fri, Nov 7, 2014 at 12:28 PM, Imesh Gunaratne <im...@apache.org> >>> wrote: >>> >>>> Hi Isuru, >>>> >>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <isu...@apache.org> >>>> wrote: >>>> >>>>> >>>>> IMHO we should have the context name 'stratos' in the url. Then it is >>>>> more intuitive. having just /api doesn't say that this API belongs to >>>>> Stratos. >>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is >>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this >>>>> might do the same, but that might not be the case always. Just my two >>>>> cents. >>>>> >>>>>> >>>>>> >>>>>> A good point, I reviewed your concern before doing this modification, >>>> most of the well known APIs do not include the product name in the context. >>>> Rather as you have mentioned they use the hostname to identify the product, >>>> please see below examples. This is why I removed "stratos" from the >>>> context, WDYT? >>>> >>>> Facebook Graph API: >>>> https://developers.facebook.com/docs/graph-api/using-graph-api/v2.2 >>>> Twitter API: >>>> https://dev.twitter.com/rest/reference/get/statuses/mentions_timeline >>>> Github API: https://developer.github.com/v3/ >>>> OpenStack API: http://developer.openstack.org/api-ref-compute-v2.html >>>> EC2 API: >>>> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html >>>> Google Cloud Compute API: >>>> https://cloud.google.com/compute/docs/reference/latest/#Addresses >>>> StackExchange API: https://api.stackexchange.com/docs/answers >>>> >>>> Thanks >>>> >>>> On Fri, Nov 7, 2014 at 11:19 AM, Isuru Haththotuwa <isu...@apache.org> >>>> wrote: >>>> >>>>> Hi Imesh, >>>>> >>>>> On Fri, Nov 7, 2014 at 1:35 AM, Imesh Gunaratne <im...@apache.org> >>>>> wrote: >>>>> >>>>>> Please note that we have now introduced API versioning in >>>>>> docker-grouping-merge branch. Now the REST API context has been changed >>>>>> as >>>>>> follows, no changes were done to existing resource paths: >>>>>> >>>>>> Previous API URL: >>>>>> https://{hostname}:{port}/stratos/admin/{resource-path} >>>>>> >>>>>> New API URL: >>>>>> https://{hostname}:{port}/api/{resource-path} >>>>>> >>>>> IMHO we should have the context name 'stratos' in the url. Then it is >>>>> more intuitive. having just /api doesn't say that this API belongs to >>>>> Stratos. >>>>> Therefore, https://{hostname}:{port}/stratos/api/{resource-path} is >>>>> better IMHO. If we have a proper hostname (stratos.apache.org) this >>>>> might do the same, but that might not be the case always. Just my two >>>>> cents. >>>>> >>>>>> >>>>>> Version specific API URLs: >>>>>> https://{hostname}:{port}/api/v4.0/{resource-path} >>>>>> https://{hostname}:{port}/api/v4.1/{resource-path} >>>>>> >>>>>> Following changes to be done: >>>>>> - Update CLI and Dashboard >>>>>> - Allow API version to be specified in an HTTP header >>>>>> >>>>>> Thanks >>>>>> >>>>>> On Tue, Nov 4, 2014 at 5:22 PM, Imesh Gunaratne <im...@apache.org> >>>>>> wrote: >>>>>> >>>>>>> We now have the docker-grouping-branch in a compilable state with >>>>>>> latests modifications. Please test all workflows related to service >>>>>>> grouping and docker, once things are stable will merge this branch to >>>>>>> master. >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> On Mon, Nov 3, 2014 at 7:48 PM, Manula Chathurika Thantriwatte < >>>>>>> manu...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I have completed deploy-application, undeploy-application, >>>>>>>> deploy-service-group and undeploy-service-group commands in CLI and >>>>>>>> pushed >>>>>>>> the changes to docker-grouping-merge branch. I'll compete the >>>>>>>> other commands as soon as possible and looks for the UI as well. >>>>>>>> >>>>>>>> Thanks ! >>>>>>>> >>>>>>>> On Mon, Nov 3, 2014 at 7:40 PM, Imesh Gunaratne <im...@apache.org> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I have now fixed autoscaler service stub bundle exports and >>>>>>>>> stratos manager import statements. Currently working on Stratos >>>>>>>>> Manager, >>>>>>>>> seems like there are duplicated domain classes: >>>>>>>>> >>>>>>>>> >>>>>>>>> org.apache.stratos.common/src/main/java/org/apache/stratos/common/Properties.java >>>>>>>>> >>>>>>>>> org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/util/Properties.java >>>>>>>>> >>>>>>>>> org.apache.stratos.rest.endpoint/src/main/java/org/apache/stratos/rest/endpoint/bean/kubernetes/Properties.java >>>>>>>>> >>>>>>>>> On Mon, Nov 3, 2014 at 3:24 PM, Rajkumar Rajaratnam < >>>>>>>>> rajkum...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Fixed AS issues >>>>>>>>>> >>>>>>>>>> On Mon, Nov 3, 2014 at 2:44 PM, Lasindu Charith <lasi...@wso2.com >>>>>>>>>> > wrote: >>>>>>>>>> >>>>>>>>>>> I have fixed some compilation errors in Cloud Controller. >>>>>>>>>>> >>>>>>>>>>> On Mon, Nov 3, 2014 at 2:07 PM, Manula Chathurika Thantriwatte < >>>>>>>>>>> manu...@wso2.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> I have started on grouping CLI commands. >>>>>>>>>>>> >>>>>>>>>>>> Thanks ! >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:53 PM, Rajkumar Rajaratnam < >>>>>>>>>>>> rajkum...@wso2.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Fixed messaging component issues. >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Nov 3, 2014 at 1:14 PM, Imesh Gunaratne < >>>>>>>>>>>>> im...@apache.org> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I have now merged latest changes from 4.0.0-grouping branch >>>>>>>>>>>>>> to docker-grouping-merge branch. We can now fix merge issues in >>>>>>>>>>>>>> docker-grouping-merge branch. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Once features are stable will move changes to master branch. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 9:15 AM, Imesh Gunaratne < >>>>>>>>>>>>>> im...@apache.org> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Isuru is working on a major refactoring task ("[Grouping] >>>>>>>>>>>>>>> Branch may be Unstable ATM"). Will hold this effort until that >>>>>>>>>>>>>>> is completed. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Sun, Nov 2, 2014 at 12:19 AM, Lahiru Sandaruwan < >>>>>>>>>>>>>>> lahi...@wso2.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I have tested grouping feature in EC2 up to instance are >>>>>>>>>>>>>>>> spawning. Will be testing further. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:57 PM, Rajkumar Rajaratnam < >>>>>>>>>>>>>>>> rajkum...@wso2.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> When and where are we creating and adding cluster monitors >>>>>>>>>>>>>>>>> (not app monitors) to the AutoscalerContext? >>>>>>>>>>>>>>>>> I couldn't find any places. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thanks. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 9:37 PM, Lahiru Sandaruwan < >>>>>>>>>>>>>>>>> lahi...@wso2.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 8:21 PM, Lahiru Sandaruwan < >>>>>>>>>>>>>>>>>> lahi...@wso2.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I get a NPE while trying to deploy the app definition >>>>>>>>>>>>>>>>>>> without properties, looking into it. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I have added a null check. Will commit the fix. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> [2014-11-01 20:17:18,922] ERROR >>>>>>>>>>>>>>>>>>> {org.apache.stratos.rest.endpoint.handlers.CustomThrowableExceptionMapper} >>>>>>>>>>>>>>>>>>> - Internal server error >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> java.lang.NullPointerException >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.deployApplicationDefinition(ServiceUtils.java:139) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.stratos.rest.endpoint.services.StratosAdmin.deployApplicationDefinition(StratosAdmin.java:139) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>>>>>>>>>>>>>>>>>> Method) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:606) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:755) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:14 PM, Imesh Gunaratne < >>>>>>>>>>>>>>>>>>> im...@apache.org> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I have now fixed few more issues: >>>>>>>>>>>>>>>>>>>> - Removing subscription resource from REST API and CLI. >>>>>>>>>>>>>>>>>>>> - Adding isKubernetesCluster property to >>>>>>>>>>>>>>>>>>>> ApplicationClusterContext. >>>>>>>>>>>>>>>>>>>> - Passing properties from Application definition to the >>>>>>>>>>>>>>>>>>>> cluster objects. This is needed for Kubernetes. >>>>>>>>>>>>>>>>>>>> - Packaging drools files in stratos distribution (some >>>>>>>>>>>>>>>>>>>> of the files were placed in repository/conf while the rest >>>>>>>>>>>>>>>>>>>> were at >>>>>>>>>>>>>>>>>>>> repository/conf/drools). >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Please find the sample application definition file >>>>>>>>>>>>>>>>>>>> which I have been using for testing attached with this >>>>>>>>>>>>>>>>>>>> mail. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Sat, Nov 1, 2014 at 3:09 PM, Imesh Gunaratne < >>>>>>>>>>>>>>>>>>>> im...@apache.org> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Can a service cluster(say php cluster) span across two >>>>>>>>>>>>>>>>>>>>> partitions(in other words two kub cluster)? I guess >>>>>>>>>>>>>>>>>>>>> kubernetes can manage >>>>>>>>>>>>>>>>>>>>> their containers within a kub cluster, not between kub >>>>>>>>>>>>>>>>>>>>> clusters? For >>>>>>>>>>>>>>>>>>>>> example, if we say we need 3 replicas, it can ensure >>>>>>>>>>>>>>>>>>>>> there are 3 replicas >>>>>>>>>>>>>>>>>>>>> in one kub cluster. It can't manage 3 replicas within two >>>>>>>>>>>>>>>>>>>>> kub cluster. Am I >>>>>>>>>>>>>>>>>>>>> missing something here? >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Raj: A good point, we can handle this in Stratos, >>>>>>>>>>>>>>>>>>>>> shouldn't be a problem. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>> Imesh Gunaratne >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Technical Lead, WSO2 >>>>>>>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Lahiru Sandaruwan >>>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos, >>>>>>>>>>>>>>>>>>> Senior Software Engineer, >>>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com >>>>>>>>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> email: lahi...@wso2.com blog: >>>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/ >>>>>>>>>>>>>>>>>>> linked-in: >>>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Lahiru Sandaruwan >>>>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos, >>>>>>>>>>>>>>>>>> Senior Software Engineer, >>>>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com >>>>>>>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> email: lahi...@wso2.com blog: >>>>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/ >>>>>>>>>>>>>>>>>> linked-in: >>>>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Raj >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Lahiru Sandaruwan >>>>>>>>>>>>>>>> Committer and PMC member, Apache Stratos, >>>>>>>>>>>>>>>> Senior Software Engineer, >>>>>>>>>>>>>>>> WSO2 Inc., http://wso2.com >>>>>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> email: lahi...@wso2.com blog: >>>>>>>>>>>>>>>> http://lahiruwrites.blogspot.com/ >>>>>>>>>>>>>>>> linked-in: >>>>>>>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Imesh Gunaratne >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Technical Lead, WSO2 >>>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Imesh Gunaratne >>>>>>>>>>>>>> >>>>>>>>>>>>>> Technical Lead, WSO2 >>>>>>>>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Raj >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Regards, >>>>>>>>>>>> Manula Chathurika Thantriwatte >>>>>>>>>>>> Software Engineer >>>>>>>>>>>> WSO2 Inc. : http://wso2.com >>>>>>>>>>>> lean . enterprise . middleware >>>>>>>>>>>> >>>>>>>>>>>> email : manu...@wso2.com / man...@apache.org >>>>>>>>>>>> phone : +94 772492511 >>>>>>>>>>>> blog : http://manulachathurika.blogspot.com/ >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> *Lasindu Charith* >>>>>>>>>>> Software Engineer, WSO2 Inc. >>>>>>>>>>> Mobile: +94714427192 >>>>>>>>>>> Web: blog.lasindu.com >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Raj >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Imesh Gunaratne >>>>>>>>> >>>>>>>>> Technical Lead, WSO2 >>>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Regards, >>>>>>>> Manula Chathurika Thantriwatte >>>>>>>> Software Engineer >>>>>>>> WSO2 Inc. : http://wso2.com >>>>>>>> lean . enterprise . middleware >>>>>>>> >>>>>>>> email : manu...@wso2.com / man...@apache.org >>>>>>>> phone : +94 772492511 >>>>>>>> blog : http://manulachathurika.blogspot.com/ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Imesh Gunaratne >>>>>>> >>>>>>> Technical Lead, WSO2 >>>>>>> Committer & PMC Member, Apache Stratos >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Imesh Gunaratne >>>>>> >>>>>> Technical Lead, WSO2 >>>>>> Committer & PMC Member, Apache Stratos >>>>>> >>>>>> -- >>>>>> Thanks and Regards, >>>>>> >>>>>> Isuru H. >>>>>> +94 716 358 048* <http://wso2.com/>* >>>>>> >>>>>> >>>>>> * <http://wso2.com/>* >>>>>> >>>>>> >>>>>> >>>> >>>> >>>> -- >>>> Imesh Gunaratne >>>> >>>> Technical Lead, WSO2 >>>> Committer & PMC Member, Apache Stratos >>>> >>> >>> >>> >>> -- >>> Raj >>> >>> -- >>> Thanks and Regards, >>> >>> Isuru H. >>> +94 716 358 048 >>> >>> -- >>> <%2B94%20716%20358%20048> >>> <%2B94%20716%20358%20048> >>> Thanks and Regards, >>> >>> Isuru H. >>> <%2B94%20716%20358%20048> >>> +94 716 358 048* <http://wso2.com/>* >>> >>> >>> * <http://wso2.com/>* >>> >>> >>> -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
