Transaction in ContainerRequestFilter?

[famod]

We are using reasteasy-reactive imperatively and we have a JwtTokenExtractor implements ContainerRequestFilter that "initializes" a @RequestScoped bean (named AuthContext) with info from the token. For that it needs to access the database.
Currently the DB access is done without a transaction which is (even for read operations) not a good practice, AFAIK.
We could start a transaction for just the read operation, but IMO it would be more efficient if there weren't two transactions per REST call.
Is there a good way to do that? Btw, our Controller classes (usually named "Resource" classes in Quarkus) are already @Transactional.

Thanks!

[famod]

I ended up converting this filter to a CDI interceptor that takes part in the controller transaction automatically.

The alternative would have been to start a transaction manually in a ContainerRequestFilter and commit it in a ContainerResponseFilter.
Or if two transactions are not a problem, simply annotating the filter with @Transactional could also do the trick (haven't tried).

Thanks @geoand for the support!