withRequestContext always creates new service context

hfour / h4bff

H4's backend & frontend framework :cupid::wrench: https://hfour.github.io/h4bff/

MIT License

7 stars 2 forks source link

withRequestContext always creates new service context #40

Closed gphfour closed 5 years ago

gphfour commented 5 years ago

I noticed that RequestContextProvider.withRequestContext always creates new service context when invoked. This could be an issue when having nested calls, because of the multiple service context that will be created, which will lead to multiple transactions etc. I guess, we should reuse the same service context all the way.