Hi, > It can be published with no error, but from the debugging there is no any > Assertion found, so the Https transport didn't take effect.
The policy looks ok - how are you setting up the TLS endpoint though? Adding a TransportBinding policy does not set up TLS, it's up to the container to do that, or else you can add a "httpj:engine-factory" configuration if using Jetty. Colm. On Thu, Jan 19, 2012 at 4:00 AM, XiLai Dai <xl...@talend.com> wrote: > Hello, > > We have a jaxws:endpoint defined like this: > <jaxws:endpoint xmlns:tns="http://my.org/examples/"; > id="greeter_Https" > implementor="demo.service.Greeter_HttpsImpl" > serviceName="tns:Greeter_HttpsService" > address="/Greeter_HttpsService"> > <jaxws:features> > <p:policies> > <wsp:Policy> > <wsp:ExactlyOne> > <wsp:All> > <sp:TransportBinding > xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";> > <wsp:Policy> > <sp:TransportToken> > <wsp:Policy> > <sp:HttpsToken > RequireClientCertificate="false"/> > </wsp:Policy> > </sp:TransportToken> > </wsp:Policy> > </sp:TransportBinding> > </wsp:All> > </wsp:ExactlyOne> > </wsp:Policy> > </p:policies> > </jaxws:features> > </jaxws:endpoint> > > It can be published with no error, but from the debugging there is no any > Assertion found, so the Https transport didn't take effect. > Can someone take a look what's wrong with the definition of policy? Thanks in > advance. > > Regards. > Xilai -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
