JBossWS uses WildFly as its target container. The following examples focus on web service deployments that leverage EJB3 service implementations and the JAX-WS programming models. For further information on POJO service implementations and advanced topics you need consult the user guide.
- Developing web service implementations
- The service implementation class
- Deploying service implementations
- Consuming web services
- Creating the client artifacts
- Constructing a service stub
- Resolving dependencies and running the client
- Maven archetype quick start
JAX-WS does leverage annotations in order to express web service meta data on Java components and to describe the mapping between Java data types and XML. When developing web service implementations you need to decide whether you are going to start with an abstract contract (WSDL) or a Java component.
If you are in charge to provide the service implementation, then you are probably going to start with the implementation and derive the abstract contract from it. You are probably not even getting in touch with the WSDL unless you hand it to 3rd party clients. For this reason we are going to look at a service implementation that leverages JSR-181 annotations.
|Even though detailed knowledge of web service meta data is not required, it will definitely help if you make yourself familiar with it. For further information see|
When starting from Java you must provide the service implementation. A valid endpoint implementation class must meet the following requirements:
- It must carry a javax.jws.WebService annotation (see JSR 181)
- All method parameters and return types must be compatible with the JAXB 2.0
Let's look at a sample EJB3 component that is going to be exposed as a web service.
Don't be confused with the EJB3 annotation @Stateless. We concentrate on the @WebService annotation for now.
The method parameters and return values are going to represent our XML payload and thus require being compatible with JAXB2. Actually you wouldn't need any JAXB annotations for this particular example, because JAXB relies on meaningful defaults. For the sake of documentation we put the more important ones here.
Take a look at the request parameter:
|If you have more complex mapping problems you need to consult the JAXB documentation.|
Service deployment basically depends on the implementation type. As you may already know web services can be implemented as EJB3 components or plain old Java objects. This quick start leverages EJB3 components, that's why we are going to look at this case in the next sections.
Simply wrap up the service implementation class, the endpoint interface and any custom data types in a JAR and drop them in the deployment directory. No additional deployment descriptors required. Any meta data required for the deployment of the actual web service is taken from the annotations provided on the implementation class and the service endpoint interface. JBossWS will intercept that EJB3 deployment (the bean will also be there) and create an HTTP endpoint at deploy-time.
jar -tf jaxws-samples-retail.jar
|If the deployment was successful you should be able to see your endpoint in the application server management console.|
When creating web service clients you would usually start from the WSDL. JBossWS ships with a set of tools to generate the required JAX-WS artifacts to build client implementations. In the following section we will look at the most basic usage patterns. For a more detailed introduction to web service client please consult the user guide.
The wsconsume tool is used to consume the abstract contract (WSDL) and produce annotated Java classes (and optionally sources) that define it. We are going to start with the WSDL from our retail example (ProfileMgmtService.wsdl). For a detailed tool reference you need to consult the user guide.
Let's try it on our sample:
- As you can see we did use the -p switch to specify the package name of the generated sources.
|ProfileMgmt.java||Service Endpoint Interface|
|Customer.java||Custom data type|
|Discount*.java||Custom data type|
|ObjectFactory.java||JAXB XML Registry|
|package-info.java||Holder for JAXB package annotations|
Basically wsconsume generates all custom data types (JAXB annotated classes), the service endpoint interface and a service factory class. We will look at how these artifacts can be used the build web service client implementations in the next section.
Web service clients make use of a service stubs that hide the details of a remote web service invocation. To a client application a WS invocation just looks like an invocation of any other business component. In this case the service endpoint interface acts as the business interface. JAX-WS does use a service factory class to construct this as particular service stub:
- Create a service factory using the WSDL location and the service name
- Use the tool created service endpoint interface to build the service stub
- Use the stub like any other business interface
In order for successfully running a WS client application, a classloader needs to be properly setup to include the JBossWS components and its required transitive dependencies. Depending on the environment the client is meant to be run in, this might imply adding some jars to the classpath, or adding some artifact dependencies to the maven dependency tree, etc. Moreover, even for simply developing a client, users might need to resolve proper dependencies (e.g. to setup their IDE).
Below you find some options for resolving dependencies and running a WS client using the JBossWS libraries:
The JBossWS project is composed of multiple Maven artifacts that can be used to declare dependencies in user Maven projects. In particular, the org.jboss.ws.cxf:jbossws-cxf-client artifact can be used for getting the whole JBossWS client dependency. Users should simply add a dependency to it in their Maven project.
If you're running the client out of container, It's also recommended to properly setup JAXWS implementation endorsing, to make sure you use the JBossWS implementation of JAXWS API instead of relying on the implementation coming with the JDK; this is usually done by copying the org.jboss.ws.cxf.jbossws-cxf-factories (JBossWS-CXF stack) jar into a local directory (e.g. project.build.directory/endorsed) and then using that for compiling and running sources, for setting the java.endorsed.dirs system property into the maven-surefire-plugin, etc:
|Endorsing of JAX-WS api jar is used to force a API level different from the one included in the JDK. E.g. JAXWS 2.2 on JDK 1.6, or JAXWS 2.1 on JDK 1.7, etc. So, depending on your environment, it might not be strictly required.|
|Endorsing is deprecated in JDK 1.8 and will be removed in future JDK version. If you can't rely on endorsing with your JDK version, be sure JBossWS components (in particular org.jboss.ws.cxf:jbossws-cxf-factories) come before jars of any other JAX-WS implementation in your classpath.|
An interesting approach for running a WS client is to leverage JBoss Modules, basically getting a classloading environment equivalent to the server container WS endpoints are run in. This is achieved by using the jboss-modules.jar coming with WildFly as follows:
The client.jar is meant to contain the WS client application and include a MANIFEST.MF file specifying the proper Main-Class as well as JBoss Module dependencies, for instance:
Finally, users can of course setup their application classpath manually (e.g when compiling and running the application directly through javac / java command or using Ant). As for the Maven project approach mentioned above, properly setting java.endorsed.dirs system property is also required.
A convenient approach to start a new project aiming at providing and/or consuming a JAX-WS endpoint is to use the JBossWS jaxws-codefirst Maven Archetype. A starting project (including working build and sample helloworld client and endpoint) is created in few seconds. It's simply a matter of issuing a command and answering to simple questions on the desired artifact and group ids for the project being generated:
The generated project includes:
- a sample HelloWorld code-first POJO endpoint
- an integration test that gets the WSDL contract for the above service, builds up a client and invokes the endpoint
- a pom.xml for creating a war archive; the project has proper WS component dependencies and uses both wsprovide and wsconsume maven plugins for generating the contract for the code-first endpoint and then generating the client stubs for such contract
- a plugin for deploying the archive on WildFly.
The project is built and tested by simply running:
The build processes the various plugins and calls into the JBossWS tools to generate all the required classes for building the deployment archive and client. The user can test the sample, have a look at the project structure and then either trash the sample endpoint and testcase and replace them with his own components, or modify them step-by-step to achieve what he needs.