Thanks Daniel for your response. The cxf-bundle is in active state and after i refresh the bundle i didn't see any of the following wss4j imports being resolved and these are supplied(exported) by wss4j-1.6.4.jar.
org.apache.ws.security; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.action; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.components.crypto; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.conversation; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.conversation.dkalgo; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.handler; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.message; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.message.token; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.processor; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.saml; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.saml.ext; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.spnego; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.util; resolution:=optional; version="[1.6, 2)", org.apache.ws.security.validate; resolution:=optional; version="[1.6, 2)" I think these classes will be resolved at runtime when they being used by cxf, in our case these classes are not being used, i may be wrong. Thanks, -Nagamohan -- View this message in context: http://cxf.547215.n5.nabble.com/wsdl-is-not-being-handled-by-cxf-2-5-x-tp5465680p5485053.html Sent from the cxf-user mailing list archive at Nabble.com.
