Why do we need this, when we have a way to define data source from UI? Even if we want, we can define it as a registry resource (resource where the UI writes) don't we? It is generally bad to have two ways to do the same thing.
On Wednesday, June 11, 2014, Rajith Vitharana <[email protected]> wrote: > Hi all, > > Currently there are no deployer to deploy datasources if it was given as a > xml file inside a CAPP. So we are going to implement a Datasource deployer > for this purpose. It will take a datasource.xml file which reside inside a > CAPP and deploy that datasource in to the server. > > Thanks, > > -- > Rajith Vitharana > > Software Engineer, > WSO2 Inc. : wso2.com > Mobile : +94715883223 > Blog : http://lankavitharana.blogspot.com/ > -- S.Uthaiyashankar VP Engineering WSO2 Inc. http://wso2.com/ - "lean . enterprise . middleware" Phone: +94 714897591
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
