Why do you prefer convention over explicit policy location. For example, I have Data service 1, 2, 3. Data service 1 and 2 are using policy 1. Data service 3 is using policy 2.
With using convention, either you can have 1 policy or 3 policy for above case. You will not be able to have only 2 policy. On Wednesday, August 20, 2014, Anjana Fernando <[email protected]> wrote: > Hi Chanika, > > Lets just put "enableSec" as an attribute in the root element of the data > service configuration. Like, <data enableSec="true"> .. and as for the > policy file location, I guess there is a standard location the ESB would > look up if its not given explicitly, we will also just skip the policy > location attribute and just go by convention where the policy file would be > located. > > Cheers, > Anjana. > > > On Wed, Aug 20, 2014 at 2:17 PM, Chanika Geeganage <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> Hi, >> >> We recently came across a requirement to support QoS related >> configurations to .dbs file itself rather than adding a separate >> services.xml file. Therefore we are going to add the transport and security >> policy related configurations in the same way that in ESB proxy services >> configurations. The changes are: >> 1. Adding transports="https http" attribute to configure transport info >> 2. Adding enableSec tag with the policy key to configure security >> i.e: >> <policy key="path/to/policy"/> >> <enableSec/> >> >> In the deployment time these configurations will be extracted. Will this >> be a good approach to follow? >> >> Thanks >> >> -- >> Best Regards.. >> >> Chanika Geeganage >> Software Engineer >> WSO2, Inc.; http://wso2.com >> >> > > > -- > *Anjana Fernando* > Senior Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- 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
