Stéphane Épardaud
Stéphane Épardaud
@geoand didn't you work on logging http requests in RR in the past? I can't find mention of it in https://quarkus.io/guides/resteasy-reactive
https://github.com/quarkusio/quarkus/issues/22213 was the issue. Would this sort of logging solve your use-cases? I'm asking all the +1 people.
That's a good idea 👍
IIRC we did not include `merge` by design, to avoid people using it too much and running into issues. Right, @Sanne ?
I don't think we promote things like that, with entities leaking out of transactions. In particular, we advise people to put `@Transactional` on REST endpoints, or equivalent other entry points.
`merge` has so many issues with its definition on how exactly things are merged, and tends to lure people into using entities as DTOs (because it's so easy to merge...
On the other hand, I still feel like writing `getEntityManager().merge(a);` is not an impossible thing to ask of "advanced users". I'm tempted to leave this as is…
Jakarta Data is using `StatelessSession` as you mention, so there are no attached entities, and as such, `merge` is never needed or relevant. We could definitely add a section about...
Assuming a blocking endpoint, but this might be better done using a reactive endpoint, if you can use Hibernate Reactive: ```java @Inject OrderMicroService orders; @Inject Mailer mailer; @POST public void...
Well, that's a relief that what I wrote makes sense, because I keep wondering if I'm missing the point about `merge` :) One more thing I'd mention against using `merge`:...