Hi, what if we populate the carbonContext upon receiving the context. This is the exact thing that happens in servletTransport (CarbonContextCreator).
The context information get lost due to spawning of a another thread. The other workaround would be to set the existing CarbonContextDetails (taken from the front-end side) to the messageContext, since the getCurrentContext looks at other scopes first before retrieving from the thread local. I think prabath did something similar to this , to restore missing headers. (with localTransport) All the above things should be only applied after localTransport check. just my thoughts, --Pradeep _______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
