You can use JDeveloper's TCP Packet Monitor to produce a log from running a web service stub. Then you can use a WS-I compliant analyzer that you have downloaded and registered with JDeveloper to check whether the web service complies with WS-I standards. Because you are running the analyzer against a stub to the web service, discovery, description and messages of the service are reported on.
First you have to run a stub or proxy to the web service with the TCP Packet Monitor running. When the packet monitor is stopped, the log file is created. The next step is to analyze the log file against a set of standard assertions.
Note: If you are working within a firewall, make sure that JDeveloper's proxy server exceptions do not include the IP address of the machine the web service is running on. For more information, see Proxy Settings and JDeveloper.
To create and analyze a log of a web service:
_endPointvariable in the generated stub. For more information, see Analyzing Web Services Running in the Embedded Server.
wsi-log.htmlfiles are created and listed in the navigator, and
wsi-log.htmlis opened in JDeveloper.
wsi-log.xmland choose Analyze WS-I Log File from the context menu. The WS-I Analyze Web Service wizard opens.
wsi-report.htmlis displayed in JDeveloper.
There are a number of reasons why you may find you have problems when performing an analysis of a web service. Some of these are outside the scope of the JDeveloper documentation, but there are two issues you might come across.
If you are haven't made any changes to the generated web service, or when you are certain that any changes you have made should not have affected the working of your web service you may still find that errors are reported. This is because because web services developed for deployment on SOAP servers or as Oracle J2EE 1.3 compliant web services are generated to conform to earlier standards. Only JAX-RPC web services are fully compliant with WS-I standards.
This can happen when the WSDL for an external web service has an
endpoint that contains the machine name in upper or mixed case, and the
stub generated by JDeveloper has the
with the machine name in lower case. This is similar to the case
discussed in Analyzing Web
Services Running in the Embedded Server. The workaround is to import
the WSDL into JDeveloper so that it is listed in the navigator, then
edit the WSDL so that the machine name is lower case. Then you can
generate the stub and run it with the TCP packet monitor running.
To import the WSDL into the navigator:
The Discovery section of
wsi-report.html reports on the
REGDATA artifacts that are used by web services you locate in a UDDI
registry. If you have created a report of a web service that you have
not located using a UDDI registry, then it all the
in this section of the report will be missing.
Analyzing Web Services
Using the TCP Packet Monitor
Copyright © 1997, 2004, Oracle. All rights reserved.