I am running a test on Ubuntu with Oracle Java 7 Update 3. According to the release notes it has JAXB-2.2.4 included with it.
/home/ubuntu# update-alternatives --config java
There is only one alternative in link group java: /usr/lib/jvm/java-7-oracle/bin/java
Nothing to configure.
The machine says it has JAXB-2.2.4 on it:
$ wsimport -version
JAX-WS RI 2.2.4-b01
$ java -version
java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b04)
Java HotSpot(TM) Client VM (build 22.1-b02, mixed mode)
However when I run my app which uses JAX-RS and marshalls some objects with JAXB I get the following error:
Apr 05, 2012 10:45:50 AM com.sun.jersey.api.json.JSONConfiguration natural
SEVERE: NATURAL JSON notation configured, but JAXB RI 2.1.10 not found. For the
recent builds to get this working correctly, you need even at least JAXB version
2.1.12. Please add it to your classpath!
Apr 05, 2012 10:45:50 AM com.sun.jersey.core.spi.component.ProviderFactory __get
ComponentProvider
SEVERE: The provider class, class com.marketchorus.rest.config.JAXBContextResolv
er, could not be instantiated. Processing will continue but the class will not b
e utilized
java.lang.RuntimeException: NATURAL JSON notation configured, but JAXB RI 2.1.10
not found. For the recent builds to get this working correctly, you need even a
t least JAXB version 2.1.12. Please add it to your classpath!
On the server side I got that same error initially so I installed metro-2.2-standalone into tomcat which fixed the issue. (Even though it was running in java 7).
On a windows client I was forced to add JAXB-2.2.5 api, impl, and jsr173 jars to my endorsed java directory to make it work (with Java 7 update 3 there as well).
When I try to do the jaxb trick under ubuntu I put the files under /usr/lib/jvm/java-7-oracle/jre/lib/endorsed I get a different error:
ERROR 10:55:44.694 taskScheduler-1 org.springframework.scheduling.support.TaskUt
ils$LoggingErrorHandler - Unexpected error occurred in scheduled task.
javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.MXParser
Factory not found
I am initializing the JAX-RS/JAXB code in my class as follows:
config = new DefaultClientConfig();
config.getFeatures().put(JSONConfiguration.FEATURE_POJO_MAPPING, Boolean.TRUE);
config.getClasses().add(JAXBContextResolver.class);
client = Client.create(config);
service = client.resource(UriBuilder.fromUri(proc.getUrl()).build());
I tried to compile it with source=1.7 and target=1.7 as it was still set for 1.6 and I was thinking maybe it was assuming the old version from the early 1.6 releases which was too old but that doesn’t solve the problem either.
I ran @andih’s test program and I still get the error. I am starting to think it is a VM issue:
ubuntu@ip-10-202-155-29:~/test$ java -cp jersey-client-1.12.jar:jersey-core-1.1
2.jar:jersery-fastinfoset-1.12.jar:jersey-json-1.12.jar:. TestNaturalJson
Apr 23, 2012 10:17:21 AM com.sun.jersey.api.json.JSONConfiguration natural
SEVERE: NATURAL JSON notation configured, but JAXB RI 2.1.10 not found. For the
recent builds to get this working correctly, you need even at least JAXB version
2.1.12. Please add it to your classpath!
Exception in thread "main" java.lang.RuntimeException: NATURAL JSON notation con
figured, but JAXB RI 2.1.10 not found. For the recent builds to get this working
correctly, you need even at least JAXB version 2.1.12. Please add it to your cl
asspath!
at com.sun.jersey.api.json.JSONConfiguration.natural(JSONConfiguration.j
ava:447)
at TestNaturalJson.main(TestNaturalJson.java:6)
ubuntu@ip-10-202-155-29:~/test$ java -version
java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b04)
Java HotSpot(TM) Client VM (build 22.1-b02, mixed mode)
Looking back at the endorsed solution with JAXB-2.2.5 RI I installed the files:
jaxb-api.jar
jaxb-impl.jar
jsr173_1.0_api.jar
into the:
/usr/lib/jvm/java-7-oracle/jre/lib/endorsed
Directory. When I do that I get the above error from Spring the MXParser error. The wierd thing here is under windows this works, but not on Ubuntu. When I run @andhi’s test program below with the endorsed setup I get OK instead of the error. But for some reason it looks like Spring under Ubuntu isn’t picking up the JSR173 jar file that is installed in the endorsed dir (which is the STAX implementation).
Well I appreciate all the comments on here, but no one managed to solve my problem, so I worked around it as follows. I installed Metro-2.2 into Tomcat 7. Then since my app is a Spring command line App I built a war out of it so it could run in the tomcat container. This involved putting all my libraries for my app in WEB-INF/lib my configuration files in WEB-INF/classes. In the WEB-INF dir I put a web.xml file that looks like this:
index.jsp is empty as there is no web facing component to this app. The spring-config parameter is my top level spring config file that would get loaded from the command line. My ant build then builds a war out of this app, and it runs great. So still not sure why my endorsed files in the jvm didn’t work as using the verbose:class flag as suggested showed them getting loaded, but by using tomcat as the container and loading the classes I need there, Jersey is happy and all the issues have gone away. Thanks again for all the help on this issue.