Prisca MOINE The Road to OSS/J SOA

Netbeans offers a web service testing web interface, browse URL: http://localhost:8080/Service/?Tester. But it only works when parameter and return types are simple Java types.

But this is not the case here. Another solution is to create a specific client allowing to handle with complex types, more precisely a Java client and a JAX-WS tool. To that purpose, the only requirement is the URL of the WSDL file describing the service to test. This service description is used by the wsimport tool to generate client web service artifacts;

The client retrieves service port from wsdl file, then it can invoke successively different methods exposed.

Note that the 'JVTTroubleTicketservantService' class is unrecognized by Netbeans because it is a JAX-WS generated class. After the needed classes have been retrieved from the service description during 'wsimport' execution, there no problem for the client to compile.

Compiling the client, meaning wsimporting artifacts from service WSDL description, building and running it, can be carried out by adding following ant targets:

Execute these compile-client and then run-client targets. This will test the exposed methods from the web service. With just a few manipulations, you have just created a web service Java client with the JAX-WS 'wsimport' tool.

Now the TroubleTicket application has became a WS, the JavaEE Service Engine has registered the new endpoint. Let's begin with the core of the first prototype : the migration of a TroubleTicket system into OpenESB.