+1 to explicitly set the property in the profile since it has some negative perf impacts and the system property can not be sufficient - until we also check the actual env.
Can also mean we lookup the beans less often at runtime and more in postconstructs or just use plain injects (don't recall why it was not the case). 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 lun. 18 mars 2024 à 09:21, Thomas Andraschko <andraschko.tho...@gmail.com> a écrit : > Can we just set this property based on the profiles for our tests? > This is probably also required for payara users, we have to add it to the > docs then of course. > > Am So., 10. März 2024 um 14:49 Uhr schrieb Thomas Frühbeck < > t.fruehb...@gmail.com>: > > > We have already discussed the problem of interceptorLookup for > PartialBean > > on Wildfly. > > IMHO due to subdeployment CL-visibilty issues (not flat!) the > interceptors > > in jar A are not visible in jar DS-partial-bean-impl. > > > > A possible solution for this can be: > > BeanMangerProvider#getBeanManager(): extend decision on lookup strategy > > like > > private static boolean useDelegateLookup() > > { > > return CoreBaseConfig.BeanManagerIntegration.DELEGATE_LOOKUP > > && System.getProperty("jboss.server.name") == null; > > } > > > > Then all tests in partial-bean-impl -P wildfly-build-managed run > > successfully! > > > > Another issue that could be resolved this way: TransactionStrategy lookup > > in data-impl: > > Instead of @Priority workaround > > - activate ContainerMangedTxStrategy in beans.xml > > - and change Injection of TransactionStrategy in > TransactionalQueryRunner > > like: > > protected Object executeTransactional(final QueryBuilder builder, > final > > CdiQueryInvocationContext context) > > { > > TransactionStrategy strategy = > > BeanProvider.getContextualReference(TransactionStrategy.class); > > > > will also work fine! > > > > Just to show the massive impact of the identified (supposed?) bug in > > Wildfly subdeployment class visibility. > > > > First step: your feedback on the proposed (temporary?) fix on > > abovementioned change in BeanManagerLookup > > :-/ > > >
