Carl-Erik Kopseng

Greenhorn
+ Follow
since Dec 11, 2010
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Carl-Erik Kopseng

Of course this is way too late to be of use, but in my case the problem was solved by simply switching to IBM's version of the JFRE. Running the app with Sun's jdk produced the error above, but switching to IBM JRE 1.6 solved the problem. IBM obviously likes to keep things within the family
A CXF JAX-RS application I have uses the Jackson library to marshal POJOs to JSON. This works for the most part, but the other day it failed with a NPE when marshalling a deeply nested object into JSON.

After some investigation I found out that Jackson was included in Glassfish 3 (through Jersey) and after removing jackson-core-asl.jar, jackson-jaxrs.jar, jackson-mapper-asl.jar and jackson-xc.jar from the /modules directory of GF everything worked beautifully. I guess that Jackson 1.7.1 (included in GF3) had some bug that was fixed in the version shipped with my application (1.8).

Now the question is, why did I even have to do this in the first place? I would have thought libraries that are included in my war files should take presedence over any libraries in Glassfish's /modules directory.

Is there a cleaner way to do this than removing jars from the app server? Maybe there are other applications that depend on these jars ...

On a side note, the problem still exists with our GF2 container, but I cannot find any jackson libraries in the /lib folder (there is no /modules folder like in GF3). Any clues on where Jackson might be hiding in GF2 (if at all)?

(This has also been posted at SO, but I got very little response, so that is why I am reposting here)
12 years ago