The following figure shows how to develop Web Services starting from SEI, when you generate Java sources with the cjwsgen command from a compiled Web Service Implementation Class:
Figure 2-4 Developing Web Services starting from SEI (When using the cjwsgen command)
- Executing the cjwsgen command
There are cases when a Web Services implementation class is created as POJO or created based on EJB. In both the cases, if you specify the -wsdl option when executing the cjwsgen command, you can generate a WSDL or check annotation errors. In such cases, do not change the generated WSDL.
For the cjwsgen command, see 14.3 cjwsgen command.
- Creating a DD
Create web.xml and application.xml. Code the Web Service-specific information in web.xml. For creating web.xml, see 3.4 Creating web.xml.
- Creating an EAR file
Create an EAR file containing the created file. For creating EAR files, see 3.5.3 Creating EAR files.
- Deploying and starting the EAR file
Deploy the created EAR file and start the file as a J2EE application (Web Services). For details on the import and start commands of J2EE applications, see cjimportapp (Importing J2EE applications) and cjstartapp (Starting J2EE applications) in the uCosminexus Application Server Command Reference Guide.
For the method to deploy (import) J2EE applications by using the management portal, see 12.3.3 Importing J2EE applicationsin the uCosminexus Application Server Management Portal User Guide.
For the method to start J2EE applications by using the management portal, see 12.3.1 Starting J2EE applications in the uCosminexus Application Server Management Portal User Guide.
The JAX-WS engine dynamically generates the JavaBeans class (stub) when you start a J2EE application (Web Services).
For the examples of developing the Web Services starting from SEI, see the following sections:
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.