I have a Java 8 interface for managing instances read from the DB, e.g. in a JSF datatable. public interface Manager<T> extends Serializable… Show more
We are trying out Agroal and could not yet get it working as a default DataSource. We added the extension <extension module="org.wildfly.extension.datasources-agroal"/> and then replaced the default datasources subsystem configuration with what we believe is the Agroal equivalent <subsystem xmlns="urn:jboss:domain:datasources-agroal:1.0"> … Show more
If you're using WF 14, I would recommend against using Agroal. I switched to it in a couple applications and had to revert to the old datasources subsystem due to a nasty bug in the version of Agroal shipped in WF 14. See WFLY-11037 and AG-94. The issue should be fixed in WF 15, or you could try upgrading the Agroal JARs in 14 by hand, I suppose.
I have an UI + REST backend pair that deploy OOTB on a WF11. I tried dropping them into a fresh WF14 but end up with 11:32:06,282 ERROR [APP_SPECIFIC] (default task-2) Uncaught exception: javax.ws.rs.client.ResponseProcessingException: javax.ws.rs.ProcessingException: RESTEASY008200: JSON Binding deserialization error… Show more
I just encountered this problem myself. I'm guessing that for the JAX-RS Client, RestEasy just auto adds any provider it finds using ServiceLoader. Which is a problem since the JSON-B provider is still present even though the "prefer Jackson" flag is set, and that flag doesn't seem to have any effect on Clients. The fix that worked for me was to…