Hi Chanika,
Thanks for the heads up. I'm using DSS 3.2.1, is this the correct approach
for 3.2.1?
Thanks.
/Gayashan
On Wed, Nov 26, 2014 at 1:09 PM, Chanika Geeganage chan...@wso2.com wrote:
As a result of [1] we moved QoS Config to be specified in the .dbs file
itself rather than in the
Yes, then you can use services.xml file.
On Wed, Nov 26, 2014 at 2:54 PM, Gayashan Amarasinghe gayas...@wso2.com
wrote:
Hi Chanika,
Thanks for the heads up. I'm using DSS 3.2.1, is this the correct approach
for 3.2.1?
Thanks.
/Gayashan
On Wed, Nov 26, 2014 at 1:09 PM, Chanika Geeganage
Thanks Chanika.
On Wed, Nov 26, 2014 at 2:59 PM, Chanika Geeganage chan...@wso2.com wrote:
Yes, then you can use services.xml file.
On Wed, Nov 26, 2014 at 2:54 PM, Gayashan Amarasinghe gayas...@wso2.com
wrote:
Hi Chanika,
Thanks for the heads up. I'm using DSS 3.2.1, is this the correct
Hi all,
What is the best way to do this? For the moment i'm following this process.
Say i have a sample service JSONSample.dbs. To engage an axis2 module to
this service, I'll create the services.xml file for this service with the
following format, JSONSample_services.xml and engage the module
As a result of [1] we moved QoS Config to be specified in the .dbs file
itself rather than in the services.xml file and then change the DBDeployer
accordingly. At the moment (in DSS 3.2.2) we have added transport and
security info in the dataservice config. See [2] for more info.
[1]
