This is the crucial part of the stacktrace: Caused by: : WFLYEJB0442: Unexpected ErrorĪt .ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:185)Īt .ee.(BasicComponent.java:161) Ĭaused by: java.lang. It appears like as long as any other modules list jackson as their dependency in their respective module.xml, it just simply doesn't get excluded, and EAP can't be arsed to even throw a warning about it.Įdit : When upgrading from EAP 7.0.0 to 7.1.0, things broke again, owing to updated Jackson jars. I ran into the exact same problem with Jackson, and I got it to work in my EAP 7 using this jboss-deployment-structure.xml : I have found a similar question JBoss 7 Classloader - Exclude Module Implementation but it didn't help me. Core annotations used for value types, used by Jackson data binding package. \jboss-eap-7.0\modules.\jboss-eap-7.0\modules\system\layers\base)) Hi All, Im new to maven, Im getting a when I run the command from the tutorial: mvn -PautoInstallPackage clean install Here is a log of the the errors: ERROR ERROR Some problems were encountered while processing the POMs: ERROR U. Loader (finder: local module finder (roots: ".jackson-databind:main" from local module īut it seems that JBoss uses the delivered module instead of the provided dependency. So, if you encounter a case where this looser invariant is violated (upgrading of core components to the next minor version breaks extension modules of current minor version), you should report this. To solve my issue I have created a jboss-deployment-structure.xml file which is contained in my war deployment. Note that Jackson core components (annotations, streaming, databind) MUST have same minor version. I am trying to use a newer version of Jackson as JBoss 7 EAP delivers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |