Whilst it does not address what the original problem was caused by, I have solved this by adding a Jackson Mixin within the web module to rename/suppress the fields concerned. JBoss descriptor I've tried below, makes no difference. I'm going to refactor the code to remove the annotations from the JPA entities, but really it would be good to find a coherent solution, as there are several other apps to migrate. The app is structured as 3 maven modules - war, ejb (jar) & the ear container. However, this doesn't seem to be the problem, otherwise the web module annotations would be ignored as well ? E.g.: Jackson annotations ignored after deployment to JBOSS I'm aware that JBoss ships with Jackson 1.x as an internal module. I've tried every permuation of jboss-deployment-structure.xml to no avail (see below). So responses come back with different field names for some objects in JBoss which trips up our user interface. In JBoss I see Jackson2 annotations etc are being ignored in the ejb module - (they are applied to JPA entities only), but are being applied in the web module. The web interface consumes/produces JSON - so am using Jackson2 with Spring 3 MVC MappingJackson2HttpMessageConverter to handling (de)serialisation in a simple controller class. It currently works fine in Glassfish 3 & WAS. I am migrating a web app from Websphere 7 (JEE5) to JBoss EAP 6.2.0 (JEE6).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |