Troubleshooting Web Services issues
WSDL generation problems during deployment
When deploying JAX-WS Web Services without associated WSDL, the application server will automatically generate the WSDL for the service. With Axis2 as the JAX-WS provider, the application server uses Sun's
wsgen tool to generate the WSDL. Sometimes
wsgen can fail to generate the WSDL (for example, because of invalid annotations). In most of such cases, the output of the
wsgen tool will be logged to the
geronimo.log file. However, in some cases the output might not get logged and it might be necessary to enable extra logging to see the full output of the
wsgen tool. To enable full logging of the
wsgen tool add the following line to server-log4j.properties file:
The output of wsgen will appear in the
AccessControlException when deploying Web Services using CXF
When deploying JAX-WS Web Services using CXF you might see the following exception:
As per JSR-109 specification application servers are supposed to block publishing new Web Service endpoints via the Endpoint API. However, this can be disabled by setting the org.apache.cxf.jaxws.checkPublishEndpointPermission system property to false. For example, start the server after setting the following property:
Accessing Web Service by certificate using Web Service client
For the Web Service client, while using client-cert, you might need to ask the server to add your certificate to the trusted key store in Geronimo server. In the meanwhile, you need to get the server's certificate, and then add it into your local key store(Geronimp Administration Console can be used to export the server's certificate).
You also need to set the following properties before starting the server.