Your pointers helped us. Thanks a lot. The basic issue was due to not loading of Wss4j. We have that in bundles repo but not included that in features.xml.
Regards Raman -----Original Message----- From: Daniel Kulp [mailto:[email protected]] Sent: Friday, February 10, 2012 11:13 PM To: [email protected] Cc: Malisetti, Ramanjaneyulu Subject: Re: ?wsdl is not being handled by cxf 2.5.x On Friday, February 10, 2012 8:41:14 AM Malisetti, Ramanjaneyulu wrote: > Is not supported log could give any clue? > > 2012-02-10 13:25:59,109 DEBUG [qtp9614239-94 - /node/wsman?wsdl] > phase.PhaseInterceptorChain --- - Invoking handleMessage on interceptor > org.apache.cxf.ws.policy.PolicyInInterceptor@1ddc941. 2012-02-10 > 13:25:59,109 DEBUG [qtp9614239-94 - /node/wsman?wsdl] > policy.PolicyEngineImpl --- - Alternative > {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}AsymmetricBindin > g is not supported. 2012-02-10 13:25:59,109 DEBUG [qtp9614239-94 - > /node/wsman?wsdl] policy.EffectivePolicyImpl --- - No alternative > supported. Strange. It SOUNDS like, somehow, the entire ws-security layer wasn't loaded, which is very strange. Since that is included in the big cxf-bundle jar, it definitely should have been loaded. Can you verify that you are using the cxf-bundle and not the minimal bundle or similar? Dan > > Regards > Raman > -----Original Message----- > From: Malisetti, Ramanjaneyulu > Sent: Friday, February 10, 2012 1:57 PM > To: [email protected] > Subject: RE: ?wsdl is not being handled by cxf 2.5.x > > We have the following policy fragment defined in WSDL. > > > <wsp:Policy wsu:Id="X509V3BindingPolicy"> > <wsp:ExactlyOne> > <wsp:All> > <sp:AsymmetricBinding> > <wsp:Policy> > <sp:InitiatorToken> > <wsp:Policy> > <sp:X509Token > sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy > /200702/IncludeToken/AlwaysToRecipient"> <wsp:Policy> > <sp:RequireThumbprintReference /> > > </wsp:Policy> > </sp:X509Token> > </wsp:Policy> > </sp:InitiatorToken> > <sp:RecipientToken> > <wsp:Policy> > <sp:X509Token > sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy > /200702/IncludeToken/Never"> <wsp:Policy> > <sp:RequireThumbprintReference /> > > </wsp:Policy> > </sp:X509Token> > </wsp:Policy> > </sp:RecipientToken> > <sp:Layout> > <wsp:Policy> > <sp:Strict /> > </wsp:Policy> > </sp:Layout> > <sp:IncludeTimestamp /> > > <sp:OnlySignEntireHeadersAndBody /> > <sp:AlgorithmSuite> > <wsp:Policy> > > <sp:TripleDesRsa15 /> > </wsp:Policy> > </sp:AlgorithmSuite> > </wsp:Policy> > </sp:AsymmetricBinding> > <sp:SignedSupportingTokens> > <wsp:Policy> > <sp:UsernameToken > > sp:IncludeToken="http://docs.oasis- open.org/ws-sx/ws-securitypolicy/2 > 00702/IncludeToken/Once" wsp:Optional="true"> > <wsp:Policy> > > <sp:WssUsernameToken10 /> > </wsp:Policy> > </sp:UsernameToken> > </wsp:Policy> > </sp:SignedSupportingTokens> > <sp:SignedParts> > <sp:Body /> > </sp:SignedParts> > <sp:EncryptedParts> > <sp:Body /> > </sp:EncryptedParts> > </wsp:All> > </wsp:ExactlyOne> > </wsp:Policy> > > > > Regards > Raman > -----Original Message----- > From: Daniel Kulp [mailto:[email protected]] > Sent: Thursday, February 09, 2012 8:27 PM > To: [email protected] > Cc: Blue Diamond > Subject: Re: ?wsdl is not being handled by cxf 2.5.x > > On Thursday, February 09, 2012 3:13:47 PM Blue Diamond wrote: > > Thanks for your response Glen. > > > > The WSDL is correctly set. And yes we are running inside Karaf. > > We also tried to put the WSDL file in the application classpath so that it > > is visible to both CXF & our app and gave the wsdlLocation="myfile.wsdl" > > ... still the same problem. the service starts, but ?wsdl is not > > responding > > correctly and CXF tries to handle it like a SOAP request intended for my > > service. > > Are there policy fragments in the WSDL that CXF may not understand? Thats > what it looks like the issue is. Since the wsdl is returned from an > interceptor on the chain, and the policies are processed very early in the > chain, they need to be resolvable. > > Dan > > > Regards, > > Anil > > > > On Wed, Feb 8, 2012 at 6:36 PM, Glen Mazza <[email protected]> wrote: > > > Are you using Karaf? Also, are you sure you're using the correct URL to > > > access the WSDL? The endpoint URL is normally different between, say, > > > Tomcat deployment and Karaf deployment. For my blog's DoubleIt tutorial > > > for example, by default it would be http://localhost:8080/** > > > doubleit/services/doubleit<http://localhost:8080/doubleit/services/doubl > > > ei > > > t>(Tomcat) vs. | > > > http://localhost:8080/**services/doubleit<http://localhost:8080/services > > > / > > > doubleit>(Karaf).| > > > > > > Glen > > > > > > On 02/08/2012 01:36 AM, Blue Diamond wrote: > > >> Hello, > > >> > > >> We are upgrading our CXF from 2.3.x to 2.5.x. We have our > > >> WebServiceProviders implemented. Our components run in OSGi. Everything > > >> is > > >> fine in 2.3.x where we used to embed CXF jars in our OSGi bundle. > > >> > > >> Now, we want to use CXF bundles from OSGi thus making our service jars > > >> thin. > > >> > > >> Our WSDL is inside the bundle. So, after migration, these resources are > > >> not > > >> visible to the outside CXF. So, we tried to handle this with 2 > > >> different > > >> apporaches > > >> 1. jaxwsCxfFactoryBean.setWSDLURL - service started successfully > > >> 2. In our WS provider impl, the annotation attribute wsdlLocation = > > >> "http://....../ourWSDL"; > > >> - service started successfully > > >> > > >> Both approaches made the service start but both have one main problem. > > >> > > >> When we open the ?wsdl endpoint on the browser, it throws a 500 error& > > >> we > > >> > > >> could see the following stacktrace on the server log. What I think is > > >> happening is that, the ?wsdl request is being handle by CXF as a SOAP > > >> call > > >> rather than a request for the WSDL document. Why could this be > > >> happening? > > >> > > >> [qtp17003719-152 - /node/wsman?wsdl] phase.PhaseInterceptorChain --- - > > >> Interceptor for -http://test/node}Node has thrown exception, unwinding > > >> now. > > >> org.apache.cxf.interceptor.**Fault: None of the policy alternatives can > > >> be > > >> satisfied. > > >> at > > >> org.apache.cxf.ws.policy.**AbstractPolicyInterceptor.**handleMessage(** > > >> AbstractPolicyInterceptor.**java:47)[131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.phase.**PhaseInterceptorChain.**doIntercept(** > > >> PhaseInterceptorChain.java:**263)[131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.transport.**ChainInitiationObserver.**onMessage(** > > >> ChainInitiationObserver.java:**123)[131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.transport.http_**jetty.JettyHTTPDestination.** > > >> serviceRequest(**JettyHTTPDestination.java:323)**[131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.transport.http_**jetty.JettyHTTPDestination.**doService( > > >> ** > > >> JettyHTTPDestination.java:289)**[131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.transport.http_**jetty.JettyHTTPHandler.handle(** > > >> JettyHTTPHandler.java:72)[131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.eclipse.jetty.server.**handler.ContextHandler.** > > >> doHandle(ContextHandler.java:**943)[99 > > >> rg.eclipse.jetty.server:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.server.**handler.ContextHandler.** > > >> doScope(ContextHandler.java:**879)[99 > > >> rg.eclipse.jetty.server:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.server.**handler.ScopedHandler.handle(** > > >> ScopedHandler.java:117)[99 > > >> rg.eclipse.jetty.server:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.server.**handler.**ContextHandlerCollection.**handle( > > >> ** > > >> ContextHandlerCollection.java:**250)[99 > > >> rg.eclipse.jetty.server:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.server.**handler.HandlerWrapper.handle(** > > >> HandlerWrapper.java:110)[99 > > >> rg.eclipse.jetty.server:7.5.4.**v20111024] > > >> at org.eclipse.jetty.server.**Server.handle(Server.java:345)**[99 > > >> rg.eclipse.jetty.server:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.server.**HttpConnection.handleRequest(** > > >> HttpConnection.java:441)[99 > > >> rg.eclipse.jetty.server:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.server.**HttpConnection$RequestHandler.** > > >> headerComplete(HttpConnection.**java:919)[99 > > >> rg.eclipse.jetty.server:7.5.4.**v20111024] > > >> at org.eclipse.jetty.http.**HttpParser.parseNext(** > > >> HttpParser.java:582)[95 > > >> rg.eclipse.jetty._http:7.5.4.**v20111024] > > >> at org.eclipse.jetty.http.**HttpParser.parseAvailable(** > > >> HttpParser.java:218)[95 > > >> rg.eclipse.jetty._http:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.server.**AsyncHttpConnection.handle(** > > >> AsyncHttpConnection.java:51)[**99 > > >> rg.eclipse.jetty.server:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.io.nio.**SelectChannelEndPoint.handle(** > > >> SelectChannelEndPoint.java:**586)[94 > > >> rg.eclipse.jetty.io:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.io.nio.**SelectChannelEndPoint$1.run(** > > >> SelectChannelEndPoint.java:44)**[94 > > >> rg.eclipse.jetty.io:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.util.thread.**QueuedThreadPool.runJob(** > > >> QueuedThreadPool.java:598)[93 > > >> rg.eclipse.jetty.util:7.5.4.**v20111024] > > >> at > > >> org.eclipse.jetty.util.thread.**QueuedThreadPool$3.run(** > > >> QueuedThreadPool.java:533)[93 > > >> rg.eclipse.jetty.util:7.5.4.**v20111024] > > >> at java.lang.Thread.run(Unknown Source)[:1.6.0_17] > > >> Caused by: org.apache.cxf.ws.policy.**PolicyException: None of the > > >> policy > > >> alternatives can be satisfied. > > >> at > > >> org.apache.cxf.ws.policy.**EffectivePolicyImpl.**chooseAlternative(** > > >> EffectivePolicyImpl.java:171)[**131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.ws.policy.**EffectivePolicyImpl.**chooseAlternative(** > > >> EffectivePolicyImpl.java:164)[**131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.ws.policy.**EffectivePolicyImpl.**initialise(** > > >> EffectivePolicyImpl.java:109)[**131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.ws.policy.**PolicyEngineImpl.** > > >> getEffectiveServerRequestPolic**y(PolicyEngineImpl.java:327)[**131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.ws.policy.**EndpointPolicyImpl.**initializeInterceptors( > > >> ** > > >> EndpointPolicyImpl.java:296)[**131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.ws.policy.**EndpointPolicyImpl.**getInterceptors(** > > >> EndpointPolicyImpl.java:126)[**131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.ws.policy.**PolicyInInterceptor.handle(** > > >> PolicyInInterceptor.java:140)[**131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> at > > >> org.apache.cxf.ws.policy.**AbstractPolicyInterceptor.**handleMessage(** > > >> AbstractPolicyInterceptor.**java:45)[131 > > >> rg.apache.cxf.bundle:2.5.2] > > >> ... 21 more > > >> 2012-02-07 15:25:41,312 WARN [qtp17003719-152 - /node/wsman?wsdl] > > >> addressing.ContextUtils --- - WS-Addressing - failed to retrieve > > >> Message > > >> Addressing Properties from context. > > >> 2012-02-07 15:25:41,312 WARN [qtp17003719-152 - /node/wsman?wsdl] > > >> addressing.ContextUtils --- - WS-Addressing - failed to retrieve > > >> Message > > >> Addressing Properties from context. > > >> 2012-02-07 15:25:41,312 WARN [qtp17003719-152 - /node/wsman?wsdl] > > >> addressing.ContextUtils --- - WS-Addressing - failed to retrieve > > >> Message > > >> Addressing Properties from context. > > >> > > >> > > >> Any help is greatly appreciated. Thanks& Regards, > > >> > > >> Anil > > > > > > -- > > > Glen Mazza > > > Talend Community Coders - coders.talend.com > > > blog: www.jroller.com/gmazza -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
