You can call an external web service from a WebLogic Workshop web service using a Web Service control. A Web Service control provides an interface to another web service, allowing you to invoke the methods and handle the callbacks of the target web service. In addition, through a Web Service control you can customize how you interact with the target web service using XML maps to shape XML message, buffers to support asynchrony, and so on. The other web service can be one developed with WebLogic Workshop or any web service for which a WSDL file is available.
Note: You should not use a Web Service control to invoke a web service that resides in the same application. Invoking a web service via a Web Service control means marshalling the method parameters into a SOAP message on the calling end and unmarshalling the SOAP message on the receiving end, then again for the method return value. This is very inefficient when the invocation is local. You would usually be tempted to invoke one web service from another if the called web service included business logic you want to access from the calling web service.
In general, you should place business logic in custom Java controls instead of in web services. This allows you to access the business logic from various contexts in the application (web services, other controls, page flows) without incurring the cost of data marshalling and unmarshalling. Web Service controls should only be used to invoke web services that are truly external to your application.
To learn more about Web Service controls, see Web Service Control.
To learn more about built-in controls, see Using WebLogic Workshop Built-In Controls.
To Add a Web Service Control to Access to Another Web Service
The control you have added is displayed in Design View on the right side of your web service. To learn how to use the control once it has been added to your web service, see Working with Built-In Controls.
How Do I: Use a WebLogic Server Web Service?