Oracle® Retail Integration Bus Service-Oriented Architecture Enabler Tool Guide Release 19.0 F22952-01 |
|
![]() Previous |
![]() Next |
Creating Web services with different implementations is a three-step process, as described below.
Note: For creating an implementation class, interface classes are required. |
Generate Web services with the default implementation as follows:
Provide the Service Definition Library XML file and click Generate Stub to create a zip file.
The zip file contains a jar file with the interface classes for the Web services. The name pattern of the jar file is <appName>-service-ejb.jar.
For example, if the application name in ServiceDef is rms, the jar file name is rms-service-ejb.jar.
The jar file also contains a properties file named ServiceProviderImplLookupFactory.properties. This file contains the name of the Web service interface and the class implementing the Web service.
Implement the interfaces and create the implementation classes. The classes can be packaged in a jar file. Upload the jar file while creating the final ear file.
When using the Service Implementation Jar File option to upload the jar containing the implementations, the default service implementation jar is not included in the .ear file. Rather, the jar file provided by the user is included. When the Web service is invoked, the service implementation provided by the user is invoked.