+1 for the core API cleanups. We should define one stable way to do things. People try out different different alternatives is a given method fails. Hence as for now there are separate variants for doing one task via the core APIs. Also as Amila mentioned people get confused when there is more than one method.
thanks, On Wed, Jun 6, 2012 at 7:12 AM, Pradeep Fernando <[email protected]> wrote: > On Tue, Jun 5, 2012 at 11:51 PM, Senaka Fernando <[email protected]> wrote: > > Hi Amila, > > > > There are some aspects of the API that originally had a purpose, but > > gradually started getting used in different ways, and there also were > some > > alternatives introduced and it seems that people misunderstood the > > intentions. We now have a much cleaner classpath, and we should deprecate > > these redundant methods and cleanup the API. Azeez and I discussed about > it, > > but nobody actually took the initiative to go ahead and clean this up. > > > > This can be considered a required aspect since Carbon 4.0.0 is a major > > release and its a good time to agree and finalize a decent API which will > > also become a part of our SPI for Tenants. So, I'm totally +1 if you are > > interested in taking the initiative to give this a start at least by > > reducing one method at a time. > > My fault i would say. I was the assigned person. Had some other work. > If amila is not going to do this, will work on it shortly. > > > --Pradeep > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
