Ladislav Thon
Ladislav Thon
Feel free to continue in this issue.
I would call the method `getInjectionTarget()`, not `getInjectedTarget()`. When it comes to the transformer API, there are more options. We could introduce some way through which a transformer implementation would...
> > I would call the method `getInjectionTarget()`, not `getInjectedTarget()`. > > I wouldn't because then a caller could expect the `jakarta.enterprise.inject.spi.InjectionTarget` to be returned which is not the case....
That's reasonable. (One might ask what have annotations to do with any of this, but the return type of the method has been `AnnotationTarget` anyway.) (`getActualTarget()`, anyone? :-) )
Haha good idea! :laughing:
This is because the annotation transformer in `SingletonToApplicationScopedTestBuildChainCustomizerProducer`: 1. doesn't look into the annotation overlay for the `@Produces` annotation, but directly into Jandex; 2. always runs _before_ the annotation transformer...
> the expectation is that there would be identity propagation This boils down to propagating the CDI request context (because `SecurityIdentityAssociation` is `@RequestScoped` and `SecurityIdentityProxy`, which is a bean with...
CC @mkouba @manovotn
The nice thing about serial execution is that you get pipelining semantics out of the box (since WebSocket guarantees ordering). That is, a client can send multiple messages, and they...
Not necessarily saying a config switch, that would be extremely coarse grained. I'm not exactly sure what a good granularity would be. The endpoint might work well: `@WebSocketEndpoint(path = "/foo",...