IMHO it should be there under tools and also a button should be given in the policy editor to validate.
Then a user can easily validate an external policy using this tool and also a user who's creating a policy can validate without navigating much. On Tue, Aug 12, 2014 at 10:45 AM, Selvaratnam Uthaiyashankar < [email protected]> wrote: > Shouldn't this policy validate go to policy editor? Why do we have it as a > separate link? > > For example, I am editing a policy in policy editor. Should I copy the > policy from there, click another link, paste there and validate? Isn't that > a major inconvenience? > > Regards, > Shankar > > > On Monday, August 11, 2014, Gayan Gunawardana <[email protected]> wrote: > >> Hi All, >> >> I'm currently developing $subject which will help to do XACML schema >> validation before saving a policy. Current implementation schema validation >> happens just before saving a policy so that you will get to know validity >> of policy only when you try to save the policy and also you may need to >> check the validity of a policy without saving the policy. >> >> >> >> >> >> >> -- >> Gayan Gunawardana >> Software Engineer; WSO2 Inc.; http://wso2.com/ >> Email: [email protected] >> Mobile: +94 (71) 8020933 >> > > > -- > 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 > > -- Dulanja Liyanage WSO2 Inc. M: +94776764717
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
