-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WildFly broken since switched to metosin/muuntaja #300
Comments
@ikitommi sounds like it might be a bug in muuntaja? |
Hi. Muuntaja depends on newer version on Jackson than WildFly ships with, causing the issue. Quick fix: https://stackoverflow.com/questions/37591081/wildfly-10-deploy-an-application-with-newer-version-of-jackson Real fix should be applied in Muuntaja itself: metosin/muuntaja#53 |
Could you try with |
Hi, many thanks for the quick responses! @ikitommi I can confirm that replacing I would assume that all other referenced WildFly versions work as well due to the rectified Jackson dependency, but would be happy to try them if you would like me to? |
Hi, pushed out |
Thanks for the quick turnaround, just pushed out a new template with the updated version. 👍 |
It appears as though WildFly has been broken by changes from b1fe4e3 (switched to metosin/muuntaja )...
(Please note I've abbreviated the stack trace below.)
As a temporary measure I have undone the changes from b1fe4e3 in my project's middleware namespace (essentially switched back to using
ring.middleware.format/wrap-restful-format
).Tested against the following versions:
Stock deployment (deployed as WAR) using OpenJDK 1.8.0_131 on Debian Stretch, e.g. http://forgezilla.com/installing-wildfly-10-on-debianubuntu/
Can reproduce using:
Then upload WAR to
/path/to/wildfly/standalone/deployments
.The text was updated successfully, but these errors were encountered: