Hi Kasun/Malaka, Once we import a connector into DevS, it will be stored in a shared location for all the ESB projects in workplace. We can use the connectors in this shared location while creating CAPP. Please note that these connectors will not be uploaded to the SVN or Git while uploading created Developer Studio projects since DevS projects and Connectors are located in two different locations in the directory hierarchy.
Consider an automated deployment scenario where a CI tool like Jenkins involving in building and deploying CAPPs into servers using the source code deployed in a SVN or Git repository. Due to the fact mentioned in the above paragraph, the automated build will be failed due to the unavailability of connectors in the SVN/Git. To avoid this build failure we can consider following solutions. 1. Include connectors into DevS project hierarchy(using new project type or including connectors into ESB project) and upload them into SVN/Git with other DevS projects. 2. Build connectors as maven artifacts and deploy them into a public Maven repository. Including connectors into ESB projects and upload them into SVN/Git seems redundant work as we have to upload the same connector again and again when we have large number of ESB projects. And creating a new project type for connectors also an overhead for users. They have to create ESB projects, Composite projects, Connectors projects etc.. I think it will be more convenient, if we can build and deploy connectors as Maven artifacts into a public maven repo. Then all we need is to put a maven dependency in the CAPP pom file to include a connector into CAPP. Is there any possibility to deploy connectors as maven artifacts into a public repo? Thanks, Viraj. On Mon, Jul 13, 2015 at 7:22 PM, Dushan Abeyruwan <dus...@wso2.com> wrote: > Hi > It seems dropping connectors to "synapse-libs" which sounds like > incorrect ideally, it must be something called 'connectors' > > Can we see possibility to correct this if possible ? (I mean there must be > some changes to be done at synapse core level as well if we need to correct > this) > > Then it should be > > <CApp.type>Connectors=zip,bpel/workflow=zip,lib/ > registry/filter=jar,webapp/jaxws=war,lib/library/bundle= > jar,service/dataservice=dbs,s > > Cheers, > Dushan > > On Mon, Jul 13, 2015 at 5:05 AM, Shakila Sivagnanarajah <shak...@wso2.com> > wrote: > >> Hi all, >> >> I use "zip" as the artifact type. But we should use a proper type. I >> think "synapse/lib" would be better. If I use synapse/lib, the CApp will >> contain <Connector_Name>.synapse_lib instead of <Connector_Name>.zip. I >> defined the CApp.type as [1] in the CApp pom. But still getting the same. I >> attach the CApp (spoComAppPro_1.0.0.car) here. How can we proceed with this? >> >> [1] <CApp.type>synapse/lib=zip >> ,bpel/workflow=zip,lib/registry/filter=jar,webapp/jaxws=war,lib/library/bundle=jar,service/dataservice=dbs,synapse/local-entry=xml,synapse/proxy-service=xml,carbon/application=car,registry/resource=zip,lib/dataservice/validator=jar,synapse/endpoint=xml,web/application=war,lib/carbon/ui=jar,service/axis2=aar,synapse/sequence=xml,synapse/configuration=xml,wso2/gadget=dar,lib/registry/handlers=jar,lib/synapse/mediator=jar,synapse/task=xml,synapse/api=xml,synapse/template=xml,synapse/message-store=xml,synapse/message-processors=xml >> </CApp.type> >> >> Thank you. >> >> On Mon, Jul 13, 2015 at 12:47 PM, Jasintha Dasanayake <jasin...@wso2.com> >> wrote: >> >>> >>> >>> On Mon, Jul 13, 2015 at 12:16 PM, Viraj Rajaguru <vi...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> We are going to implement "including connectors into CApp" feature in >>>> DevS side. >>>> >>>> Currently, we can import a connector into DevS using import connector >>>> wizard. Imported connector will be stored in shared location for all the >>>> ESB projects in workplace. That means, once you import a connector it will >>>> be visible to all the ESB projects. >>>> To facilitate to include these connectors into CApp, we can list all >>>> the connectors that are available in this location in the Composite >>>> Application project's pom file editor. Then users can select required >>>> connectors and create a CApp. >>>> >>> >>> +1 for this approach , we also have to think about importing scenarios >>> , if user import esb project which already added connectors then we need >>> to properly handle it >>> >>> >>>> >>>> Using above mentioned approach, we can support the use case mentioned >>>> by Kasun. >>>> - We want to invoke a Twitter operation. >>>> - Import the Twitter connector from connector-store(into DevS) and use >>>> the Twitter connector operation in our mediation logic. >>>> - Include connector and the artifact(API, Proxy service, Sequence) into >>>> CApp and deploy the CApp. >>>> >>>> And also currently there is no option to remove imported connectors. >>>> There is only "Import connectors" wizard. We are going to change this >>>> wizard to "Manage connectors" which will allow users to import and remove >>>> connectors to/from DevS. >>>> >>> >>> +1 for renaming the name but first we should think where we initiate >>> this wizard based on that we can decide the name >>> >>> Thanks and Regards >>> /Jasintha >>> >>> >>> Thanks, >>>> Viraj. >>>> >>>> On Fri, Jul 10, 2015 at 9:55 AM, Kasun Indrasiri <ka...@wso2.com> >>>> wrote: >>>> >>>>> Good progress Shakila. Lets get the end-to-end use case working. >>>>> >>>>> On Thu, Jul 9, 2015 at 5:27 PM, Shakila Sivagnanarajah < >>>>> shak...@wso2.com> wrote: >>>>> >>>>>> Hi Malaka, >>>>>> >>>>>> I have tested the scenarios [1] and [2]. [1] is working fine and to >>>>>> test [2], I am unable to bundle connector and proxy-service in a CApp. >>>>>> If I >>>>>> add those two in to the config project, the CApp will contain >>>>>> proxy-service >>>>>> only. >>>>>> >>>>>> [1] Including more than one connector in CApp. >>>>>> [2] Use the connector inside a proxy service, Api and sequence that >>>>>> are included in the same CApp. >>>>>> >>>>>> Thank you. >>>>>> >>>>>> On Thu, Jul 9, 2015 at 10:20 AM, Shakila Sivagnanarajah < >>>>>> shak...@wso2.com> wrote: >>>>>> >>>>>>> Hi Malaka, >>>>>>> >>>>>>> As you noted, I will test for possible scenarios. >>>>>>> >>>>>>> Thank you. >>>>>>> >>>>>>> On Thu, Jul 9, 2015 at 10:10 AM, Malaka Silva <mal...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Shakila, >>>>>>>> >>>>>>>> Good Progress on this. >>>>>>>> >>>>>>>> Let's verify some scenario similar to following, >>>>>>>> >>>>>>>> 1. Include more that one connector. >>>>>>>> 2. Use the connector inside a proxy service, Api and sequence >>>>>>>> that are included in the same capp. >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Jul 8, 2015 at 6:23 PM, Shakila Sivagnanarajah < >>>>>>>> shak...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> I have done the connector deployment from CApp. >>>>>>>>> >>>>>>>>> Thank you >>>>>>>>> >>>>>>>>> On Wed, Jul 8, 2015 at 10:25 AM, Shakila Sivagnanarajah < >>>>>>>>> shak...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> >>>>>>>>>> Please find the CApp [1]. >>>>>>>>>> >>>>>>>>>> This is my progress: >>>>>>>>>> >>>>>>>>>> 1. I added the connector zip in to the CApp as an artifact and >>>>>>>>>> specified the artifact type as "zip". >>>>>>>>>> 2. As the same way to deploy the artifact, I have implemented a >>>>>>>>>> method to deploy the synapse library in [2] (Still testing). >>>>>>>>>> 3. I have added some constants in [3]. >>>>>>>>>> >>>>>>>>>> I am following the way that Dushan noted. Initially I am doing >>>>>>>>>> this with a single connector. As the first step, Now I am doing the >>>>>>>>>> connector deployment (CAR -- > upload -- > deploy connector). >>>>>>>>>> >>>>>>>>>> [1] >>>>>>>>>> https://drive.google.com/a/wso2.com/file/d/0B3SvJgvWs9I_eWY5UEJhM3pzb0k/view?usp=sharing >>>>>>>>>> >>>>>>>>>> [2] >>>>>>>>>> <CARBON-MEDIATION-HOME>/components/application-deployers/org.wso2.carbon.application.deployer.synapse/src/main/java/org/wso2/carbon/application/deployer/synapse/SynapseAppDeployer.java >>>>>>>>>> >>>>>>>>>> [3] >>>>>>>>>> <CARBON-MEDIATION-HOME>/components/application-deployers/org.wso2.carbon.application.deployer.synapse/src/main/java/org/wso2/carbon/application/deployer/synapse/SynapseAppDeployerConstants.java >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thank you. >>>>>>>>>> >>>>>>>>>> On Wed, Jul 8, 2015 at 6:02 AM, Dushan Abeyruwan <dus...@wso2.com >>>>>>>>>> > wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Tue, Jul 7, 2015 at 8:07 AM, Jasintha Dasanayake < >>>>>>>>>>> jasin...@wso2.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> @viraj >>>>>>>>>>>> >>>>>>>>>>>> Shall we enable this in ESB project level , since there is a >>>>>>>>>>>> option already in ESB project , that we can improve to pack >>>>>>>>>>>> connector into >>>>>>>>>>>> capp when adding the ESB project into Capp ? >>>>>>>>>>>> >>>>>>>>>>> +1 this should be feasible with ESB Project level as its >>>>>>>>>>> already there in DevS >>>>>>>>>>> >>>>>>>>>>> Shashika, could please provide more detail (design and >>>>>>>>>>> implementation detail/changes you have done) how you planned to >>>>>>>>>>> integrate >>>>>>>>>>> this ? >>>>>>>>>>> >>>>>>>>>>> however, please note that we need manage depdenencies correctly >>>>>>>>>>> >>>>>>>>>>> CAR -- > upload -- > deploy connector/s --- >[[*critical:* >>>>>>>>>>> monitor the status of connector deployment]] -- if success ---> >>>>>>>>>>> execute >>>>>>>>>>> connector-meta-import --> if success -- > then deploy other >>>>>>>>>>> synapse-artifacts >>>>>>>>>>> >>>>>>>>>>> *guess, the difficulty can be holding synapse artifact >>>>>>>>>>> deployment till connector's uploaded successfully and import >>>>>>>>>>> connector meta >>>>>>>>>>> data, have found solution for this ?* >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thanks and Regards >>>>>>>>>>>> /Jasintha >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Jul 7, 2015 at 4:33 PM, Shakila Sivagnanarajah < >>>>>>>>>>>> shak...@wso2.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Kasun, >>>>>>>>>>>>> >>>>>>>>>>>>> Since there is no feature in developer studio to import >>>>>>>>>>>>> connector zip into the CApp, I have manually added the zip in >>>>>>>>>>>>> to car. Now I am debugging and modifying the code [1]. I think I >>>>>>>>>>>>> am going >>>>>>>>>>>>> well with the task. >>>>>>>>>>>>> >>>>>>>>>>>>> [1] >>>>>>>>>>>>> https://github.com/wso2/carbon-mediation/blob/master/components/application-deployers/org.wso2.carbon.application.deployer.synapse/src/main/java/org/wso2/carbon/application/deployer/synapse/SynapseAppDeployer.java >>>>>>>>>>>>> >>>>>>>>>>>>> Thank you. >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Jul 7, 2015 at 4:22 PM, Kasun Indrasiri < >>>>>>>>>>>>> ka...@wso2.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Any progress on this task? >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Jul 2, 2015 at 11:09 PM, Malaka Silva < >>>>>>>>>>>>>> mal...@wso2.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Shakila will be starting to implement this functionality >>>>>>>>>>>>>>> from ESB side. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> @Shakila - Any blockers user this mail thread to discuss. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Jun 30, 2015 at 5:57 PM, Jasintha Dasanayake < >>>>>>>>>>>>>>> jasin...@wso2.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> From tooling perspective, this is similar to class mediator >>>>>>>>>>>>>>>> deployment using Capp , Since Capp class mediator deployment >>>>>>>>>>>>>>>> now working >>>>>>>>>>>>>>>> fine with Capp so this can be done , However this is also >>>>>>>>>>>>>>>> kind of sever >>>>>>>>>>>>>>>> extension so we have to educate the users to use this properly. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks and Regards >>>>>>>>>>>>>>>> /Jasintha >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, Jun 30, 2015 at 5:11 PM, Kasun Indrasiri < >>>>>>>>>>>>>>>> ka...@wso2.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> AFAIR, this was discussed several times. But in the >>>>>>>>>>>>>>>>> context of ESB as a service, I think this will be quite >>>>>>>>>>>>>>>>> useful. I don't >>>>>>>>>>>>>>>>> think we have any technical difficulty in doing this. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Use case : >>>>>>>>>>>>>>>>> - We want to invoke a twitter operation. >>>>>>>>>>>>>>>>> - Import the twitter connector from connector-store( into >>>>>>>>>>>>>>>>> DevS) and use the twitter connector operation in our >>>>>>>>>>>>>>>>> mediation logic. >>>>>>>>>>>>>>>>> - Now we want to deploy the artifact into ESB but it is >>>>>>>>>>>>>>>>> required to deploy/enable the connector beforehand. (If the >>>>>>>>>>>>>>>>> connector is >>>>>>>>>>>>>>>>> not deployed in the ESB instance, this config deployment will >>>>>>>>>>>>>>>>> fail.) >>>>>>>>>>>>>>>>> - If we can include the connector as part of the cApp, >>>>>>>>>>>>>>>>> then the connector deployment is completely transparent to >>>>>>>>>>>>>>>>> the users. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> WDYT? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Kasun Indrasiri >>>>>>>>>>>>>>>>> Software Architect >>>>>>>>>>>>>>>>> WSO2, Inc.; http://wso2.com >>>>>>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> cell: +94 77 556 5206 >>>>>>>>>>>>>>>>> Blog : http://kasunpanorama.blogspot.com/ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *Jasintha Dasanayake* >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *Senior Software EngineerWSO2 Inc. | http://wso2.com >>>>>>>>>>>>>>>> <http://wso2.com/>lean . enterprise . middleware* >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *mobile :- 0711368118 <0711368118>* >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Best Regards, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Malaka Silva >>>>>>>>>>>>>>> Senior Tech 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/> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Save a tree -Conserve nature & Save the world for your >>>>>>>>>>>>>>> future. Print this email only if it is absolutely necessary. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Kasun Indrasiri >>>>>>>>>>>>>> Software Architect >>>>>>>>>>>>>> WSO2, Inc.; http://wso2.com >>>>>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>>>>> >>>>>>>>>>>>>> cell: +94 77 556 5206 >>>>>>>>>>>>>> Blog : http://kasunpanorama.blogspot.com/ >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Shakila Sivagnanarajah >>>>>>>>>>>>> Associate Software Engineer >>>>>>>>>>>>> Mobile :+94 (0) 770 760240 >>>>>>>>>>>>> shak...@wso2.com >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>>>>> *Jasintha Dasanayake* >>>>>>>>>>>> >>>>>>>>>>>> *Senior Software EngineerWSO2 Inc. | http://wso2.com >>>>>>>>>>>> <http://wso2.com/>lean . enterprise . middleware* >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> *mobile :- 0711368118 <0711368118>* >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>> Architecture@wso2.org >>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Dushan Abeyruwan | Technical Lead >>>>>>>>>>> Technical Support-Bloomington US >>>>>>>>>>> PMC Member Apache Synpase >>>>>>>>>>> WSO2 Inc. http://wso2.com/ >>>>>>>>>>> Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* >>>>>>>>>>> Mobile:(001)812-391-7441 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Shakila Sivagnanarajah >>>>>>>>>> Associate Software Engineer >>>>>>>>>> Mobile :+94 (0) 770 760240 >>>>>>>>>> shak...@wso2.com >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Shakila Sivagnanarajah >>>>>>>>> Associate Software Engineer >>>>>>>>> Mobile :+94 (0) 770 760240 >>>>>>>>> shak...@wso2.com >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> Malaka Silva >>>>>>>> Senior Tech 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/> >>>>>>>> >>>>>>>> Save a tree -Conserve nature & Save the world for your future. >>>>>>>> Print this email only if it is absolutely necessary. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Shakila Sivagnanarajah >>>>>>> Associate Software Engineer >>>>>>> Mobile :+94 (0) 770 760240 >>>>>>> shak...@wso2.com >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Shakila Sivagnanarajah >>>>>> Associate Software Engineer >>>>>> Mobile :+94 (0) 770 760240 >>>>>> shak...@wso2.com >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Kasun Indrasiri >>>>> Software Architect >>>>> WSO2, Inc.; http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> cell: +94 77 556 5206 >>>>> Blog : http://kasunpanorama.blogspot.com/ >>>>> >>>> >>>> >>>> >>>> -- >>>> Viraj Rajaguru >>>> Senior Software Engineer >>>> WSO2 Inc. : http://wso2.com >>>> >>>> Mobile: +94 77 3683068 >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> *Jasintha Dasanayake* >>> >>> *Senior Software EngineerWSO2 Inc. | http://wso2.com >>> <http://wso2.com/>lean . enterprise . middleware* >>> >>> >>> *mobile :- 0711368118* >>> >>> _______________________________________________ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Shakila Sivagnanarajah >> Associate Software Engineer >> Mobile :+94 (0) 770 760240 >> shak...@wso2.com >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Dushan Abeyruwan | Technical Lead > Technical Support-Bloomington US > PMC Member Apache Synpase > WSO2 Inc. http://wso2.com/ > Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* > Mobile:(001)812-391-7441 > > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
