Ticket as PDF attached :-) Am Mo., 11. März 2024 um 21:10 Uhr schrieb Thomas Andraschko < andraschko.tho...@gmail.com>:
> Cant open the link :/ > > Thomas Frühbeck <t.fruehb...@gmail.com> schrieb am Mo., 11. März 2024, > 21:03: > > > Now it seems fixed: Wildfly's BDAs are isolated, no visibility inside DS > of > > outside Beans/Interceptors/... > > Details see: https://issues.redhat.com/browse/WFLY-19111 > > Kinda interresting read - no spec violation by raw words - but I don't > > quite get the point :-/ > > > > Am So., 10. März 2024 um 15:20 Uhr schrieb Thomas Frühbeck < > > t.fruehb...@gmail.com>: > > > > > Now issue created successfully: > > > https://issues.redhat.com/browse/WFLY-19111 > > > > > > Am Sa., 9. März 2024 um 17:18 Uhr schrieb Thomas Frühbeck < > > > t.fruehb...@gmail.com>: > > > > > >> Follow-Up: I think I successfully created a 2-module war project > > >> reproducing the problem. > > >> Tried to create a bug report on Wildfly - permission denied > > >> :-/ > > >> > > >> Am Sa., 9. März 2024 um 13:29 Uhr schrieb Romain Manni-Bucau < > > >> rmannibu...@gmail.com>: > > >> > > >>> We can but wonder if it does not depend on wildfly version too but > > >>> ultimagely we could detect it is wildfly and not capture the same BM. > > >>> For standalone case it misses a web-inf/classes global BM so back to > > the > > >>> BDA issue. > > >>> By reflection you can always lookup the right one using CDI impl - > > >>> forcing > > >>> caller class directly - but not sure it is good. > > >>> > > >>> > > >>> > > >
