On Wed, Jul 17, 2013 at 6:17 PM, Sameera Jayasoma <[email protected]> wrote:
> Hi devs, > > Looks like there is an inconsistent API change in CarbonContext. Recently > CarbonContext.getThreadLocalCarbonContext() method was introduced to get > the CarbonContext object from the running thread. Now every thread in the > system should have an associated CarbonContext object. This is the correct > behaviour. But the method name is inconsistent with the existing API. > > CarbonContext.getCurrentContext() method still has old implementation. > Due to consistency reasons we are getting rid of the > getThreadLocalCarbonContext() method and refactor the code base to use > getCurrentContext method. > Quick question, so are we going to refactor the getCurrentContext() to give priority to thread local instead of message context and configuration context? We did this change a while back during stratos 1.6 release and bad things happened after a while, refer to thread "[Dev] UserRegistry sends null to JDBCAuthorizationManager". Please ignore if I am saying something that's unrelated ... > Thanks, > Sameera. > > -- > Sameera Jayasoma, > Architect, > > WSO2, Inc. (http://wso2.com) > email: [email protected] > blog: http://sameera.adahas.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > > Lean . Enterprise . Middleware > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Thanks, Shariq. Phone: +94 777 202 225
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
