views:

411

answers:

1

I want to upgrade my jaxws to 2.2 (jdk1.6 comes bundled with jaxws 2.1). My jdk is (I did not install public jre):

java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode)

In jaxws' own doc they explain how to do it:

One way to fix this is to copy jaxws-api.jar and jaxb-api.jar into JRE endorsed directory, which is $JAVA_HOME/lib/endorsed (or $JDK_HOME/jre/lib/endorsed)

But I am not sure this is having any effect in my installation. For starters I have only defined %JAVA_HOME%. And folder $JAVA_HOME/lib/endorsed is inexistant, so I created and copied the two jars. But if I do (wsgen is a tool from jaxws)

wsgen -version

I still get: JAX-WS RI 2.1.6 in JDK 6

I also tried creating folder JAVA_HOME\jre\lib\endorsed (notice that in the doc they say JDK_HOME, but as I only have JAVA_HOME I used this path). Still same wsgen output.

My questions are:

  1. What is the difference between JAVA_HOME and JDK_HOME in the doc page? anything significant or just two ways to refer to JAVA_HOME ?
  2. Is 'wsgen -version' a valid way to check jaxws version that is used or this always calls the exe in the original jdk, but it does not mean endorsed jars will be used?
  3. Anyone knows very detailed steps to install jaxws2.2 in a jdk.16?

I found this post that has some hints about what I am seeing I think

A: 

It isn't tied to your environment variables. %JAVA_HOME% is just shorthand in the documentation that doesn't know where you installed Java or what version of Java you installed.

%JAVA_HOME% refers to a JRE (the regular runtime a non-developer would have). %JDK_HOME% refers to the rood directory of a JDK, a Java Development Kit, something a developer would use.

More than that, you have to know when you run wsgen where it is being run from, and the the corresponding JVM is configured with an endorsed directory that contains the jars.

Yishai
no matter where wsgen is being run, as I have JAVA_HOME%\bin in the path. So the wsgen.exe will always be the one in there. But I hoped it would load the jars in the endorsed dir or something
raticulin