The jaxws-retail
quickstart is a working example of a simple web service endpoint.
What is it?
The jaxws-retail
quickstart demonstrates the use of JAX-WS in WildFly Application Server as a simple profile management application. It also demonstrates usage of wsconsume to generate classes from WSDL file.
System Requirements
The application this project produces is designed to be run on WildFly Application Server 12 or later.
All you need to build this project is Java 8.0 (Java SDK 1.8) or later and Maven 3.3.1 or later. See Configure Maven to Build and Deploy the Quickstarts to make sure you are configured correctly for testing the quickstarts.
Use of WILDFLY_HOME
In the following instructions, replace WILDFLY_HOME
with the actual path to your WildFly installation. The installation path is described in detail here: Use of WILDFLY_HOME and JBOSS_HOME Variables.
Start the WildFly Standalone Server
-
Open a terminal and navigate to the root of the WildFly directory.
-
Start the WildFly server with the default profile by typing the following command.
$ WILDFLY_HOME/bin/standalone.sh
NoteFor Windows, use the WILDFLY_HOME\bin\standalone.bat
script.
Install the Quickstart Parent Artifact in Maven
This quickstart requires the quickstart-parent
artifact to be installed in your local Maven repository. To install it, navigate to your QUICKSTART_HOME directory directory and run the following command.
$ cd QUICKSTART_HOME
$ mvn clean install
Build and Deploy the Quickstart
-
Make sure you start the WildFly server as described above.
-
Open a terminal and navigate to the root directory of this quickstart.
-
Type the following command to build the artifacts.
$ mvn clean package wildfly:deploy
This deploys the jaxws-retail/service/target/jaxws-retail-service.war
to the running instance of the server.
You should see a message in the server log indicating that the archive deployed successfully.
Server Log: Expected Warnings and Errors
You will see the following errors and warnings in the server log. These messages come from the jaxws-tools-maven-plugin
plugin that generates source files based on the WSDL. You can ignore these warnings.
[INFO] Could not find log4j.xml configuration, logging to console.
[INFO]
[INFO] TODO! Cheek SOAP 1.2 extension
[ERROR] log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils).
[ERROR] log4j:WARN Please initialize the log4j system properly.
[ERROR] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
You might also see the following errors if your Linux environment defines a BASH_FUNC_scl() function. You can ignore these errors.
[ERROR] /bin/sh: scl: line 1: syntax error: unexpected end of file
[ERROR] /bin/sh: error importing function definition for `BASH_FUNC_scl`
Access the Application
You can check that the Web Service is running and deployed correctly by accessing the following URL: http://localhost:8080/jaxws-retail/ProfileMgmtService/ProfileMgmt?wsdl. This URL will display the deployed WSDL endpoint for the Web Service.
Run the Client
-
Make sure you Install the Quickstart Parent Artifact in Maven.
-
Verify that the service is deployed properly.
-
Open a terminal and navigate into the client directory of this quickstart.
$ cd client/
-
Type this command to run the client.
$ mvn exec:java
-
You should see the following output in the client console.
Jay Boss's discount is 10.00
Undeploy the Quickstart
When you are finished testing the quickstart, follow these steps to undeploy the archive.
-
Make sure you start the WildFly server as described above.
-
Open a terminal and navigate to the root directory of this quickstart.
-
Type this command to undeploy the archive:
$ mvn wildfly:undeploy
Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse
You can also start the server and deploy the quickstarts or run the Arquillian tests in Red Hat JBoss Developer Studio or from Eclipse using JBoss tools. For general information about how to import a quickstart, add a WildFly server, and build and deploy a quickstart, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts.
This quickstart is dependent on a WSDL file that is included in the jaxws-retail-service
project, so it deploys and runs differently in JBoss Developer Studio than the other quickstarts.
When you import this project into JBoss Developer Studio, you see 17 errors. These Java Problems
are because these classes are not included in this project. Instead, they are defined in and generated from the jaxws-retail-service/src/main/webapp/WEB-INF/wsdl/ProfileMgmtService.wsdl
WSDL file. You can ignore these errors.
This quickstart requires that you build the parent project, deploy the service, and then run the client.
-
To build the parent project, right-click on the jaxws-retail project and choose Run As –> Maven install.
-
To deploy the service:
-
Right-click on the jaxws-retail-service project and choose Run As –> Maven install.
-
In the jaxws-retail-service project, select the target/generated-sources/wsconsume folder and choose Build Path –> Use as Source Folder.
-
Right-click on the jaxws-retail-service project and choose Run As –> Run on Server.
-
Select the JBoss EAP server and click Finish.
-
You should see the following message in the Console tab:
WFLYSRV0010: Deployed "jaxws-retail-service.war"
-
You also see the "404 - Not Found" error in the application window. This is because there is no user interface for this quickstart. You can ignore this error.
-
-
To run the application:
-
To access the application, right-click on the jaxws-retail-client project and choose Run As –> Java Application.
-
Choose the Client class and click OK.
-
Review the output in the console window. You should see the following message:
Jay Boss's discount is 10.00
-
-
To undeploy the project, right-click on the jaxws-retail-service project and choose Run As –> Maven build. Enter
wildfly:undeploy
for the Goals and click Run.
Debug the Application
If you want to debug the source code of any library in the project, run the following command to pull the source into your local repository. The IDE should then detect it.
$ mvn dependency:sources
Note
|
You will see the following informational messages. This is because the source files for this JAR are not available in the Maven repository.
|