JavaCreating SOAP Web Services with JAX-WS

Creating SOAP Web Services with JAX-WS content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.

Creating SOAP Web Services with JAX-WS

SOAP web service depends upon a number of technologies (such as UDDI, WSDL, SOAP, HTTP) and protocol to transport and transform data between a service provider and the consumer. Though it may seem overwhelming at first, with so many complex technologies intermingling together in a perfect symphony, creating SOAP web service in Java is actually pretty simple. One can almost overlook the intricacies of creating SOAP Web Service and focus on the business logic while Java takes care of the most on behalf of the programmer. Without delving into the core of SOAP technology lets get our hands dirty in creating one.

SOAP Request/Response
Fig 1: SOAP Request/Response

Writing SOAP Web Service from Scratch in Java EE7

Suppose, a web service producer/server provides a web method to display a list of products, and the client/consumer is a simple swing desktop application that wants to display the list of products in a table format. Thus our project structure can be illustrated as in Fig 2.

Hypothetical scenario demonstrating SOAP web service usage
Fig 2: Hypothetical scenario demonstrating SOAP web service usage

Creating Web Service Producer

The Web Service producer in the example has a project structure and three classes as follows:

Project structure of SOAP web service producer
Fig 3: Project structure of SOAP web service producer

1) This class represents the Product entity. Except for the annotations used, this class is nothing more than a simple POJO. This class actually maps to a table in the database. For a class to be an entity, it has to be annotated @Entity. Persistence provider (here, EclipseLink is used as a persistence provider, which comes bundled with Glassfish) recognizes it and transforms it into an entity and not just a simple POJO. @Id defines the unique identifier or primary key of the relation. @GeneratedValue represents that the unique identifier is auto generated by the database. Unique id generation may be done in various ways defined through ‘strategy’. @NamedQuery defines a static query, which in our case is used to retrieve products from the database. 
package org.mano.entity;
//...import statements
@NamedQuery(name="Product.getAllProducts", query="SELECT p FROM Product p")
public class Product implements Serializable { 
       private static final long serialVersionUID = 1L;
       @Id @GeneratedValue(strategy=GenerationType.AUTO)
       private Long id;
       private String name;
       private String composition;
       private String type;
       private Integer quantity;
       private String company;
       private String attribute;
       private Float price;
       //...constructors, getters and setters  

2) This is an EJB class annotated @Stateless and contains the main business logic (e.g. getAllProducts()). Observe that there is no ‘new’ object created for EntityManager. Since there can be only one entity instance of EntityManager with the same persistent identity, we delegated the responsibility of creating the EntityManager object to the container, i.e. app server with annotation @PersistenceContext. The ‘unitName’ in @PersistenceContext is the same name that is used in Persistence.xml (<persistence-unit name=”ProductSOAPServer” transaction-type=”JTA”>). 
package org.mano.ejb;
//...import statements
public class ProductEJB {
       private EntityManager entityManager;           
       public List<Product> getAllProducts(){
             TypedQuery<Product> query = entityManager.createNamedQuery("Product.getAllProducts",Product.class);
             return query.getResultList();

The above two classes have nothing to do with Web Service per se, they are just necessary supporting classes for the project. The class described below is the interface to the world, real deal, our Web Service class

3) With the annotation @WebService any POJO becomes a Web Service. That’s it. Since we will be fetching data from the database we can simply use the EJB class (ProductEJB) as a controller or service provider of the database. Also EJB is a container managed, Like EntityManager, we do not use ‘new’ to create the ProductEJB object, a simple @EJB annotation is good enough.  
//...import statements
public class ProductWS {
       ProductEJB productEJB;
       public List<Product> getAllProductDetails(){
             return productEJB.getAllProducts();
       public List<String> getAllProductNames(){
             List<Product> list=productEJB.getAllProducts();
             List<String> productNames = new ArrayList<>();
             for(Product p:list){
             return productNames;

<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.1"  
       <persistence-unit name="ProductSOAPServer" transaction-type="JTA">        

Note: The content of Persistence.xml is mostly auto generated (at least in Eclipse or Netbeans). There is a subtle aspect; observe that we have used – transaction-type=”JTA” and <jta-data-source> jdbc/mysqldsn </jta-data-source>. For this you have to configure Glassfish and create a MYSQL JDBC pool from the admin console of Glassfish. Please refer connector/j usage…glassfish-config on how to configure MYSQL JDBC Pool and use transaction type as JTA.

Testing Web Service without a Client

Once the Web Service producer is created we can test whether the Web Service is running properly or not without writing a client/consumer application. Observe that there is a function named getAllProductNames in We shall call this function and observe the output. The simplest way to do this is to:

  • Run the project in the application server (in this case Glassfish). 
  • Open the admin console: http://localhost:4848
  • Click on Applications from Common Task, then click on your project from Applications
  • Click on View Endpoints from the Modules and Components list
  • Click on Tester link (there are subsequent steps, which are self-explanatory) to test the Web Service
  • You may also click the WSDL link to see the XML (this file is used by the wsimport to create Web Service client files, as we’ll see down the line).

Observe that following XML request and response are actually created while we test – getAllProductNames. So that claim of ‘data exchange’ through XML in SOAP is true after all 🙂

SOAP Request  
<?xml version="1.0" encoding="UTF-8"?><S:Envelope 
xmlns_S="" xmlns:SOAP-
        <ns2:getAllProductNames xmlns_ns2=""/>
SOAP Response  
<?xml version="1.0" encoding="UTF-8"?><S:Envelope 
xmlns_S="" xmlns:SOAP-
        <ns2:getAllProductNamesResponse xmlns_ns2="">

Creating Web Service Consumer

We have tested the Web Service without writing a client app. Now create a simple Java application, which we shall use as a Web Service client or consumer. Thus, the Web Service consumer project has the following structure and files.

Project structure of SOAP web service Consumer
Fig 4: Project structure of SOAP web service Consumer

1) Web Service client files: Web Service client files can be auto generated with the help of wsimport as follows.

  • Create a directory named src. We shall import the Web Service client files into this directory.
    • Wsimport can be found in jdk…/bin directory. Use wsimport to import the necessary wWeb Service client files. wsimport generates the necessary java classes from the WSDL link. Where to find the WSDL link? Check out the section above – Testing Web Service without client. Type the following in the command line interface with the WSDL. In my case:

wsimport -keep -s src http://localhost:8080/…/ProductWSService?wsdl

  • The following java files will be created in src/org/mano/ws directory.

Files generated by wsimport
Fig 5: Files generated by wsimport

  • Observe the directory hierarchy (in my case org/mano/ws). Create a package (according to the same, in the client project and copy-paste the java files. Now you are ready to use Web Services in your client project. 

2) This is the client interface where products are displayed in a table format. The class uses javax.swing.JTable to display the list. The product list is fetched with the help of following code.

ProductWSService webService = new ProductWSService();
ProductWS productWS = webService.getProductWSPort();
products = productWS.getAllProductDetails();

//... import statements

public class Main extends JFrame {

       private static List<Product> products = new ArrayList<>();
       private JTable table;

       public Main() {
             super("List of Products");
             setSize(400, 400);
             setLayout(new BorderLayout(5, 5));
             ProductWSService webService = new ProductWSService();
             ProductWS productWS = webService.getProductWSPort();
             products = productWS.getAllProductDetails();
             table = new JTable();
             add(new JScrollPane(table), BorderLayout.CENTER);

       private void populateTable() {
             String columnNames[] = { "ID", "Name", "Composition", "Attribute",
                           "Company", "Quantity", "Type", "Price" };
             DefaultTableModel dataModel = new DefaultTableModel(columnNames,
             int row = 0;
             for (Product p : products) {
                    dataModel.setValueAt(p.getId(), row, 0);
                    dataModel.setValueAt(p.getName(), row, 1);
                    dataModel.setValueAt(p.getComposition(), row, 2);
                    dataModel.setValueAt(p.getAttribute(), row, 3);
                    dataModel.setValueAt(p.getCompany(), row, 4);
                    dataModel.setValueAt(p.getQuantity(), row, 5);
                    dataModel.setValueAt(p.getType(), row, 6);
                    dataModel.setValueAt(p.getPrice(), row, 7);

       public static void main(String[] args) throws Exception{
             new Main();


Note: Make sure that Glassfish with the Web Service producer is still running; otherwise the client/web service consumer application will not work. Also note that I have already inserted some dummy data in to the database. You may use SQL to insert some dummy product details as follows:

INSERT INTO product_tbl (ID, NAME, COMPOSITION, TYPE, QUANTITY, COMPANY, ATTRIBUTE, PRICE) VALUES (1, ‘Levalon’, ‘Silymarin’, ‘TAB’, 10, ‘Brown & Burk’, ’70mg’, 45.60);

Now, run the client application from the Eclipse/ Netbeans/ command line; you’ll get the following output.

Client application output: Product details displayed in JTable.
Fig 6: Client application output: Product details displayed in JTable.


Creating a SOAP web Service producer/consumer is pretty simple. However, looks can be deceiving, there are lots of things going on behind the scene obviously not as simple as they seem. Thanks to Java and its tools, programmers can ignore the intricacies most of the time and enjoy creating SOAP Web Services.

Get the Free Newsletter!

Subscribe to Developer Insider for top news, trends & analysis

Latest Posts

Related Stories