Creating a JAX-WS-Based EnterpriseOne Consumer Business Service Using JDeveloper 12c or JDeveloper 11g
You use OMW to create a new business service object, and then open the business service object in JDeveloper from OMW. Before you create the business service, ensure that the target JAX-WS web service for which the JAX-WS-based EnterpriseOne client business service is being developed is up and running and its WSDL URL is accessible.
A JAX-WS based EnterpriseOne Consumer business service reference implementation, JRH90I34, is provided for you to use as a model for creating a custom JAX-WS based consumer business service.
If you are using JD Edwards EnterpriseOne Tools Release 9.2 with JD Edwards Enterprise One Applications Release 9.0 or 9.1, and you plan to generate a web service based on the JAX-WS standard, it is important to consider your current consumption of the service. While the services function in the same manner, whether deployed as JAX-RPC or JAX-WS, there are some important caveats:
The service wsdl for a service generated as JAX-WS differs from the same service wsdl generated as JAX-RPC.
If you currently interact with these services from an external system you may need to make changes to those systems before switching to JAX-WS.
For prepackaged integrations that use internal consumer services, you may need to maintain a JAX-RPC based deployment for them to function correctly.
See the specific EnterpriseOne applications guide for your integration to view the supported BSSV deployment options.
See the technical paper, "Understanding the Impact of JAX-WS", on My Oracle
Support (Doc ID 1488986.1) https://support.oracle.com/rs?type=doc&id=1488986.1
for additional information about the implications of the JAX-WS build
option.