Glen, Sanjiva If a tree falls in a forest and no one is around to hear it, does it make a sound? http://en.wikipedia.org/wiki/If_a_tree_falls_in_a_forest
If you remove all sign of it from axis2.xml, I don't think it matters whether its there or not. Most users will never see any more than that. Paul On 3/23/07, Sanjaya Karunasena <[EMAIL PROTECTED]> wrote:
On Friday 23 March 2007 10:35, Deepal Jayasinghe wrote: > > Not only do I not mind it but can you please also remove the entire > > concept? AFAIK we have *never* found a need for the "locked" vs. > > "unlocked" concept .. so let's just dink it. YAGNI and all that. > > I am -1 on removing locked attribute , it has many usecases though we > are not suing that inside Axis2 codebase. External parties will find it > very useful , I remember at the last apacheCon I heard from one of user > that he is using locked attribute in his applications. > > Thanks > Deepal > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] If I have correctly understood the rational here, locked attribute will allow me to have a setting across the server which cannot be changed by the users. Meaning, by the services.xml. Yes, that will have valid use cases. But what are the real use cases for having that attribute available in services.xml? Thanks Sanjaya --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
