+1 for sticking into a single schema for now. We need to compensate that with proper comments in schema/ xml config file and proper error handling.
thanks, On Thu, Feb 11, 2016 at 12:06 AM, Manoj Kumara <[email protected]> wrote: > +1 for keeping single schema as it would be easy to maintain as well. Lets > make this with the minimum required entries that being used at the moment > as we can update this when new fields need to be included. > > Regards, > Manoj > > *Manoj Kumara* > WSO2 Inc. *| **lean. enterprise. middleware.* > *Mobile:* +94 713 448188 > > On Thu, Feb 11, 2016 at 12:00 AM, Chiranga Alwis <[email protected]> > wrote: > >> Hi, >> >> I have created a preliminary XML schema definition for the >> wso2as-web.xml. Please refer the following mail thread for the initial >> discussion about this topic: >> >> Moving single-sign-on configuration property content to wso2as-web.xml in >> WSO2 App Server 6.0.0. >> >> The definition I have created primarily contains configurations for >> single-sign-on, class-loading, stats publishing and etc. >> >> When observing the schema definition it would be clear that I have made >> majority of the configurations which can be overridden at web-app level as >> optional (for example: sso configurations) This has been done mainly to >> avoid the requirement of maintaining two XSDs for global and web-app level. >> For mandatory elements, default values would be set from the application >> code, if the particular elements are unspecified. >> >> Any suggestions and ideas are highly appreciated. >> -- >> Chiranga Alwis, >> Software Engineering Intern, >> +94 77 5930497 >> +94 77 6368208 >> > > -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: [email protected] <[email protected]> mobile: +94 (0)71 56 91 321
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
