This is not related to interceptors, this is related to all single deltaspike module from core (BeanManagerProvider) to Data or JSF ones (mainly cause all modules rely on this provider). So overall @Priority does not solve the issue. What is weird is that weld/wildfly changed the behavior of CDI.current to no more align initial context lookup and CDI.current which looks like a big bug to me.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mar. 5 mars 2024 à 20:13, Thomas Frühbeck <t.fruehb...@gmail.com> a écrit : > Everything reverted, reason once again: Priority! > > DeltaSpikeProxyInterceptorLookup#resolveInterceptors fails because it has a > different BeanManager context! > Will this mean, that all DS interceptor-related logic now needs/requires(!) > Priority annotation? > PR sent. > > Am Sa., 2. März 2024 um 17:44 Uhr schrieb Thomas Frühbeck < > t.fruehb...@gmail.com>: > > > I built a Weld-only test for Partial-Bean-Interceptor. > > > >> > >> >
