Gregor Zeitlinger

> You can always explicitly extract the Baggage from any given Context instance via `Baggage.fromContext(context)`. Does that work for you? Yes, that works (`System.out.println(Baggage.fromContext(extractedContext));`) - but it doesn't help me...

That would be a nice utility function on top - but this is not what this ticket is about. In the example, I would suggest that `serverSpan.makeCurrent()` should activate `extractedContext`...

Another solution would be to let the `extract` method activate the context - or make it the the `extractAsCurrent` and deprecate `extract`.

Thanks for all the feedback - and sorry for not making a better example. I really liked [this example](https://github.com/open-telemetry/opentelemetry-java/issues/4214#issuecomment-1053923191) to demonstrate the problem with the current API. As pointed out,...

OK, created an [issue](https://github.com/lightstep/lightstep-tracer-java/issues/223).

This feature is described [here](https://github.com/zalando/opentracing-toolbox/blob/main/opentracing-proxy/README.md#example). Maybe a cross-link would have helped you? If so, where? A PR is highly welcome, BTW :smile:

I've now created a a fork at https://github.com/klinq/klinq-jpaspec.

@zouyx not sure I understand this PR correctly. Is this about changing the operation name to be something more meaningful than `GET`?

Fixes #143

it looks like this is similar to `/review-statistics`. Could you just use that?