Bhakti Mehta's Blog

Web Services and XML Archives

Rehash of WS Reliable Messaging (WS-RM) in Metro 1.0 and what's next

• WS-ReliableMessaging specification
• WS-RM Policy Assertion

• Web Services ReliableMessaging Policy Assertion (WS-RM policy ver 1.1)
• Web Services Reliable Messaging ver 1.1

Obtaining and analyzing thread dumps

I usually get the java process id using jps

Control Break/ kill  options

On UNIX platforms you can send a signal to a program by using the kill command. This is the quit signal, which is handled by the JVM. For example, on Solaris you can use the command kill -QUIT process_id,
where process_id is the process number of your Java program.

Alternatively you can enter the key sequence <ctrl>\ in the window where the Java program was started. Sending this signal instructs a signal handler in the JVM, to recursively print out all the information on the threads
and monitors inside the JVM.
To generate a stack trace on Windows platforms, enter the key sequence <ctrl><break> in the window where the Java program is running, or click the Close button on the window.

Byron Nevins has also pointed in his blog how to obtain thread dumps in Glassfish.

TDA
This is a great utility I found for analyzing thread dumps.

I especially liked the ability to filter the threads display to be able to ignore e.g. idle threads.. Also as you can see in Fig 1 The three pane view is really helpful

Fig 1 : Using TDA to analyze thread dumps

Update to Developing Webservices using Glassfish AS 9.1 and JDK 6

In the previous  blog  we tried running glassfish-samples using Glassfish v2  using JDK 6.
We walked through what was different when trying with JDK 6 and I mentioned to use a temporary
work-around of putting javaee.jar in $AS_HOME/lib/endorsed..
However this bug is now fixed since Glassfish v2 b31 .

The latest Glassfish v2 installs webservices-api.jar in $AS_HOME/lib/endorsed. and hence we do not need to put javaee.jar there.

Install JDK 6 from http://download.java.net/jdk6/binaries/

Install  GlassFish v2

You can install  the latest nightly or the latest promoted v2 build from https://glassfish.dev.java.net/public/downloadsindex.html
Follow these instructions to unbundle and configure glassfish .

1. Check the following file where AS_HOME is the location where Glassfish is installed

   <$AS_HOME>/config/asenv.conf for AS_JAVA

2. Modify  $AS_JAVA to point to JDK 6 if that is not already set

   AS_JAVA="location of JDK 6" 

1. Run :

    java -jar javaee5-samples-installer-1.0-b09.jar

2. Edit : <location of samples>/bp-project/build.properties to point to $AS_HOME for e.g

      javaee.home="location of Glassfish"

4. Check the java version on the client side
   

      /usr/glassfish-samples/javaee5/webservices %java -version
      java version "1.6.0-rc"
      Java(TM) SE Runtime Environment (build 1.6.0-rc-b104)
      Java HotSpot(TM) Client VM (build 1.6.0-rc-b104, mixed mode, sharing)

/usr/glassfish/bin %$AS_HOME/bin/asadmin* start-domain domain1

1. /usr/glassfish-samples/javaee5/webservices/hello-jaxws %ant

This is how the output looks like on the client side

/usr/glassfish-samples/javaee5/webservices/hello-jaxws %ant

Buildfile: build.xml


init:


compile-deploy-service:

     [echo] /usr/glassfish


get-artifacts-unix:

     [exec] parsing WSDL...




     [exec] generating code...


get-artifacts-windows:


get-artifacts:


compile-client:

    [javac] Compiling 1 source file to /usr/glassfish-samples/javaee5/webservices

hello-jaxws/build


run-client-unix:

     [exec] Hello result = Hello Administrator!


run-client-windows:


run-client:


all:


BUILD SUCCESSFUL

Total time: 13 seconds

Please note:
As seen in the following sample.
Clients should set the fololowing property to run with JDK 6

 <sysproperty key="java.endorsed.dirs" value="${javaee.home}/lib/endorsed"/> 

The solution is to copy $AS_HOME/lib/endorsed/webservices-api.jar to $JAVA_HOME/jre/lib/endorsed.

Neither jvmargs nor sysproperty will work in this case
because by the time ant loads this class it would have already loaded the 2.0 classes
and we did not get the chance to override the 2.0 classes with 2.1 classes.

Developing Webservices using Glassfish AS 9.1 and JDK 6

This blog will show how to develop, run and deploy JAX-WS  based webservices with Glassfish v2 Milestone 3 build using JDK 6.
It will demonstrate step by step instructions using the hello-jaxws sample from the following glassfish-samples.

What is different when trying with JDK 6?

JDK 6.0 has  JAXB/JAX-WS 2.0 versions of the apis.
In the latest Glassfish v2 we are integrating the implementation classes compliant with JAXB/JAX-WS 2.1 versions
of the apis which are present in  javaee.jar .

So when we run with Glassfish and JDK 6.0 (without putting anything in the <AS HOME>/lib/endorsed directory),
the APIs/Annotation classes for JAX-WS 2.0 and JAXB 2.0 will be picked up instead of JAX-WS 2.1 and JAXB 2.1.

To avoid this we need to use the endorsed standards to override the 2.0 apis by putting javaee.jar in $AS_HOME/lib/endorsed.
This is a temporary workaround for now and this issue will be fixed soon.

Steps to run the sample with JDK 6

Install JDK 6 from http://download.java.net/jdk6/binaries/

Install  GlassFish v2 Milestone 3

Install  from https://glassfish.dev.java.net/public/downloadsindex.html
Follow these instructions to unbundle and configure glassfish .

1. Check the following file where AS_HOME is the location where Glassfish is installed

   <$AS_HOME>/config/asenv.conf for AS_JAVA

2. Modify  $AS_JAVA to point to JDK 6 if that is not already set

   AS_JAVA="location of JDK 6" 

1. Run :

    java -jar javaee5-samples-installer-1.0-b08.jar

2. Edit : <location of samples>/bp-project/build.properties to point to $AS_HOME for e.g

    javaee.home="location of Glassfish"

3. Check the java version on the client side
   

    /usr/glassfish-samples/javaee5/webservices %java -version
          java version "1.6.0-rc"
          Java(TM) SE Runtime Environment (build 1.6.0-rc-b104)
          Java HotSpot(TM) Client VM (build 1.6.0-rc-b104, mixed mode,   sharing)

1. mkdir -p $AS_HOME/lib/endorsed

2. mv $AS_HOME/lib/javaee.jar $AS_HOME/lib/endorsed

/usr/glassfish/bin %$AS_HOME/bin/asadmin* start-domain domain1

1. Modify <location  of samples>/javaee5/webservices/hello-jaxws/build.xml to point to
   $AS_HOME/lib/endorsed/javaee.jar in classpath. Currently the samples point to j2ee.jar in the build.xml
Replace references of j2ee.jar with location of javaee.jar


<path id="classpath">
    <pathelement location="${javaee.home}/lib/endorsed/javaee.jar"/>
    <pathelement location="${classesdir}"/>
</path>

and
 <target name="compile-deploy-service" depends="init">
     <mkdir dir="${classesdir}"/>
     <echo message="${javaee.home}"/>
     <javac
         srcdir="./src"
         includes="endpoint/**"
         destdir="${autodeploydir}"
         classpath="${javaee.home}/lib/endorsed/javaee.jar"
     />
...
</target>



2. Run:

   /usr/glassfish-samples/javaee5/webservices/hello-jaxws %ant

/usr/glassfish-samples/javaee5/webservices/hello-jaxws %ant

Buildfile: build.xml


init:


compile-deploy-service:

     [echo] /usr/glassfish


get-artifacts-unix:

     [exec] parsing WSDL...




     [exec] generating code...


get-artifacts-windows:


get-artifacts:


compile-client:

    [javac] Compiling 1 source file to /usr/glassfish-samples/javaee5/webservices

hello-jaxws/build


run-client-unix:

     [exec] Hello result = Hello Administrator!


run-client-windows:


run-client:


all:


BUILD SUCCESSFUL

Total time: 13 seconds

WS-Reliable Messaging and Session Support (Part2)

Technorati:WSIT Tango

WS Reliable Messaging and Session Support (Part1)

@WebService(endpointInterface="rmdemo.server.RMDemo")

public class RMDemoImpl {

....

}

private final HashTable<String,String> sessionTable = 

    new HashTable<String, String>();

  @Resource
  private javax.xml.ws.WebServiceContext context;

  private String getSessionId() {
       return (String)context.getMessageContext()
      .get("com.sun.xml.ws.sessionid");
  }

 private String getSessionData() {
      String id = getSessionId();
      String ret = sessionTable.get(id);
      return ret!= null ? ret : "";
  }

  private void setSessionData(String data) {
       sessionTable.put(getSessionId(), data);
  }

  @WebMethod
  public void addString(String s )
      setSessionData(getSessionData() + " " + s);

  } 

  @WebMethod
  public String getResult() {
       return getSessionData();  

  }

JAXB 2.0 and JAX-WS 2.0 are a part of Mustang (JDK 6.0)

Delivering Web Services is one of the primary themes for Mustang (Java SE 6). Our goal is that JSE will provide reasonable support for ease of development for the web services stack. This will primarily be client-side focused with a lightweight server to support callbacks. The main specifications are the Java Architecture for XML-Web Services (JAX-WS) 2.0 (formerly known as JAX-RPC) and Java Architecture for XML Binding (JAXB) 2.0.

JSR 224 is defining JAX-WS 2.0. This is a major update since the JAX-RPC 1.0 specification incorporating new specifications and updates to existing standards. JAX-WS 2.0 now delegates the databinding related tasks to JAXB 2.0.

JSR 222 is defining JAXB 2.0. It adds significantly to JAXB 1.0, including 100% XML schema support, the binding of Java classes to XML schema, the meeting of data binding requirements for JAX-WS 2.0, and schema evolution support. A flexible binding allows an application to bind only parts of an XML document (relevant to the application) to Java.

Mustang has the webservices features integrated as of b40. You can try the latest snapshot from https://mustang.dev.java.net/

We are fixing and integrating bugs on a regular basis. Please let us know about your bugs, you can file them at
http://bugs.sun.com/bugdatabase/index.jsp

There are 4 new scripts added in the jdk6.0/bin which are as follows xjc, schemagen , wsimport and wsgen
To run the JAXB schema compiler you can invoke the xjc as

/path/to/jdk6.0/bin/xjc foo.xsd -p test.foo

Similarly to invoke the schema generator to generate schemas from Java sources

/path/to/jdk6.0/bin/schemagen Foo.java

To generate portable artifacts from wsdls and external jaxws or jaxb binding files you can use wsimport

/path/to/jdk6.0/bin/wsimport stock.wsdl -b stock.xml -b stock.xjb

To generate portable artifacts from Java sources you can use wsgen

/path/to/jdk6.0/bin/wsgen example.Stock

Javadocs for jdk6.0
The javadocs are located at
http://www.java.net/download/jdk6/doc/api/

Forums
http://forums.java.net/jive/forum.jspa?forumID=25

List of Committed bugs in the latest snapshot release
https://mustang.dev.java.net/MustangCommittedBugs.html

More information on JAXB and JAXWS

* JAXB
* JAXWS

This work is licensed under a Creative Commons License.