Reka, it's good that you followed the same pattern we had in Cartridge design. It's best if you can generate the XSD and validate the definition, if not already done. +1. Will generate and validate against XSD.
> > Question: > > * Why we need both type and id? > "id" introduced for a readability purpose. If it is redundant, then we can get rid of the id and go ahead with the type. > * How the policy file and cartridge definition relates? Should one > configure policy file and cartridge definition together? > Yah. Devop need to configure cartridge definition as well as the policy file together. But still, according to my understanding, policy file can be generic and independent from the cartridge definition. In this case, we might not able to apply all the policies to all the cartridge definition. So, it is Stratos Manger's responsibility to validate the cartridge definition against the policy files and display the applicable list of policies to a cartridge. Thanks, Reka > > >> >> Thanks, >> Reka >> >> >> >> -- >> Reka Thirunavukkarasu >> Software Engineer, >> WSO2, Inc.:http://wso2.com, >> Mobile: +94776442007 >> > > > > -- > Best Regards, > Nirmal > > Nirmal Fernando. > PPMC Member & Committer of Apache Stratos, > Senior Software Engineer, WSO2 Inc. > > Blog: http://nirmalfdo.blogspot.com/ > -- Reka Thirunavukkarasu Software Engineer, WSO2, Inc.:http://wso2.com, Mobile: +94776442007
