When you're developing a Java control, you can quickly generate a JWS (web service) file with which to test the control. The generated JWS includes methods that are designed to call methods of your control. The generated file is also conversational so that it can support your control's interface even if it is asynchronous.
While the generated file is obviously not a substitute for actual testing, it does provide an easy to find out if your code works as you expect.
To Generate a Test JWS File
WebLogic Workshop will open the newly generated JWS file in Design View. The generated file will include methods that call your control's methods. Where your control's methods have return values, those values will be returned by the test file's methods.
In many cases, the template you created can be run as generated. However, in some cases you may need to make a few changes before using it to test.
The test JWS file does not include code to handle your control's callbacks. The test interface can receive the request, but it cannot respond to it because it does not implement the callback interface set by the service. To test callbacks, the callback handlers must be tested from a client that implements the callback interface. To do this you might create callbacks within the test JWS, then call these from your control's callback handlers.
This starts the web service's conversation.
When you are finished testing, click finishTestDrive to finish testing.
Samples
None.
None.