I'm using the CXF's wsdl2java (through maven codegen plugin) to generate sources from wsdl (top-down) of a jax-ws web service.
Everything is fine till I have to deploy on WebSphere Application Server 7.
So, I made some adjustments according to various documentation found on the internet.
Now my deployed jax-ws (with frontEnd forced to 2.1) works fine.

The problem now is that I don't see any trace of the web service contained in my web module from the WAS admin concole (nor client, nor provider... nothing at all).

This situation prevents me to apply Policy Sets and configure WS-Security from the admin console.

My questions are:

  • what does prevent a working web service to be shown in the admin console?
  • if I cannot see it in the admin console: how to configure policy sets without the console?
有帮助吗?

解决方案

Sadly, if you are using a 3rd party JAX-WS library on WebSphere, neither the client nor the provider will not show up in the admin console, and you won't be able to configure it to use the WS-Security and other stuff that comes with WAS.

Read the official doc here.

许可以下: CC-BY-SA归因
不隶属于 StackOverflow
scroll top