The Web Services Explorer supports the following Web browsers:
- Microsoft® Internet Explorer 6.0 or higher
- Mozilla 1.2.1 or higher
- Firefox 1.0 or higher
If you are launching the WORF test environment outside the workbench using Mozilla, a Mozilla version of at least 1.3.1 is recommended. Output from invoking your web service as well as description files may not be rendered correctly in earlier versions of the Mozilla browser.
Problem: When a remote server is created using the stub runtime the EAR will not get published.
Cause: The Web service wizard has no way to find out whether a server can be started or not.
Solution: In any perspective where the Servers view is available, right-click the remote server and select Add and Remove Projects. Select the project and add it to the server.
Problem: If you attempt to run the Web service wizards on and EAR that contains a J2EE application client project with the Install service on server option selected, or an EJB project that does not contain an EJB, the wizard will not allow you to generate the Web service.
Cause: The Web service wizards perform a check to ensure that they can consume the type of project selected on page three of the wizard. If they cannot, the wizard prevents you from continuing.
Solution: If you cancel out of the wizard and rerun with Install service on server not selected, or add an EJB to the EJB project, you will be able to progress in the wizard.
Problem: You may get a handshake error such as "Error opening socket: javax.net.ssl.SSLHandshakeException: unknown certifcate" when using tools such as the Web service wizards or the Web Services Explorer to access resources like WSDL documents, Web services and UDDI private registries hosted on WebSphere® Application Server https endpoints.
Cause: This occurs because WebSphere Application Server uses a security certificate for negotiating secured connections that other JRE-based applications do not normally share.
IWAB0014E Unexpected exception occured. java.lang.NullPointerException at org.eclipse.jst.ws.internal.consumption.ui.wsrt.WebServiceRuntimeExtensionUtils2.getAllServerFactoryIdsWithRuntimes(Unknown Source)Do not delete the server runtime after you have created a server. Delete the server first if you need to delete a server runtime. Also, do not use the same workspace if you have added or removed server adapters (such as by clicking on the "Don't see your server listed? Click here" link in the Server > Installed runtimes preference page).
For example, if the bean method name is BodyMassIndex, the Axis deployment descriptor operation name would be bodyMassIndex (where 'b' is lowercase) to make it follow standard Java naming conventions.
There are two possible solutions:When deploying a Web service client to an EJB project, the proxy configuration page will include a combo box that lets you pick which EJB this Web service client will be scoped to. This is a requirement defined by JSR-109 where the component-name of a component-scoped-refs element must match the ejb-name of an EJB in the module.
When there is at least one EJB in the project, no errors will occur. However, if there are no EJBs in the project, the combo box in the proxy configuration page will be editable and have a default value equal to the service name from the WSDL suffixed by "EJB". Furthermore, the client wizard will display a warning dialog indicating that the deployment is incomplete because the Web services client is not scoped to an existing EJB. The user can fix this by creating an EJB with the same name as the component-name used in webservicesclient.xml.
However, if you choose to abort the client creation by canceling out from the wizard, the wizard will not remove the incomplete component-scoped-refs from webservicesclient.xml. You should remove the incomplete component-scoped-refs manually before redeployment.
E_fatalError (10500) Serious technical error has occurred while processing the request. : Fault code=Client Fault string=Client Error Fault actor=null Detail=null DispositionReport: ErrCode=E_fatalError ErrInfoText=E_fatalError (10500) Serious technical error has occurred while processing the request.
If a complex type used in a Web service becomes significantly large a problem may occur in displaying the input form for it in the Web Services Explorer. This problem would become apparent when trying to fill in an input form for a Web service in that some of the deepest nested fields would be missing. There are certain other side effects of not filling in the entire input form that you might see. If elements from the part of the form not displayed are required, this would cause the Web Services Explorer validator to produce an error.
This problem will only occur when using a significantly nested complex type. Given that the form is not correct, the only way to invoke the service correctly is by filling in the part of the form that does appear and switching to the source view. At this point you would need to consult the XSD that describes the complextype and enter the raw data by hand. Make sure to invoke from this page and do not flip back to the form page as data may be lost.
When Using a version 9.1 DB2® project and the Axis SOAP engine there is a problem with the DQX DADX scenario in the Web Services Explorer. When testing the Web service using the Web Services Explorer you are given the option of using one of three bindings: SOAP, HTTP GET and HTTP POST. If you choose Get or Post and try and invoke execute/execute query operation from the Web Services Explorer you will get the following error:
IWAB0135E An unexpected error has occurred. IOException Server returned HTTP response code: 400 for URL:
This is a limitation of the Web Services Explorer, not the Web service. Test the Web service usig the SOAP binding.
This warning is a false alarm. More details can be found at: http://www.ibm.com/support/docview.wss?rs=636&context=SSCVRP&q=&uid=swg21051601&loc=en_US&cs=utf-8&lang=en+en
Note that this error does not apply to WebSphere Application server 6.x.The preferences found on the
page will not be effective immediately after importing them from a .epf file. You must shut down and restart the workspace for the preferences to take effect.When launching the Universal Test Client from the Web Services wizard, the JNDI Provider URL is set to the default WebSphere port of 2809. If you have changed the port number, you would not be able to search the JNDI directory. If you try to access the JNDI directory, you will get the following error: IWAD0403E Could not construct the JNDI tree: Caught CORBA.COMM_FAILURE when resolving initial reference=WsnNameService
When generating a Web service or Web service client using Ant on the command line, and the target runtime supports EAR association, the created project will not be associated with the EAR project. This occurs if the EAR is initially empty, or when the EAR does not exist in the workspace at all. This results in validation errors against the EAR because it must have at least one associated module. The errors, which are seen in the wsgen.txt output file, looks like the following:
[wsgen] *** ERROR ***: Thu Sep 28 15:11:14 EDT 2006 org.eclipse.emf.common.util.WrappedException: org.xml.sax.SAXParseException: cvc-complex-type.2.4.b: The content of element 'application' is not complete. One of '{"http://java.sun.com/xml/ns/j2ee":display-name, "http://java.sun.com/xml/ns/j2ee":icon, "http://java.sun.com/xml/ns/j2ee":module}' is expected.
There are a couple of solutions to this issue. Since the error messages do not actually affect the Web service code generation, they can be ignored, but the you will have to manually associate the project with the desired EAR project afterwards. Alternately, before generating the Web service or Web service client, ensure the target project and EAR already exists in the workspace, and ensure the project is already associated with the EAR project.
In the Create ,test and validate a WS-I compliant Web Service Cheat sheet and Create a Web Service from a WSDL file CheatSheet, if you are using the HelloService.wsdl file from the wsad_install/wstools/eclipse/plugins/com.ibm.etools.cs.wsdl.content_ver/examples, please modify the service port location according to the different run-time environment as follows: location="http://localhost:9080/HelloWorldSample/services/Hello_Port"
If you are importing your own wsdl file, make sure that the location is set properly according to the run-time environment selected as mentioned above.