The xmlns:wst defines the namespace used in the message, whereas the targetNamespace is used in the WSDL itself. Looking at the specs it appears that the WSDL in the CXF sample started off as a WS-Trust 1.3 WSDL (which uses the "/" for all namespaces) and was modified to make the requests compliant with WS-Trust 1.4 (which does not use "/" for the message parts, and uses a different targetNamespace altogether for the WSDL). It's been that way for years though and produces messages compliant with the spec so I'm not going to change it now.
Colm. On Mon, Sep 17, 2018 at 2:03 PM Tóth Csaba <ig...@domen.hu> wrote: > Hello! > > In the STS wsdl > ( > https://github.com/apache/cxf/blob/master/distribution/src/main/release/samples/sts/wsdl/ws-trust-1.4-service.wsdl) > > something is not clear for me: > in the definition there are two namespace definition: > - target namespace -> > targetNamespace="http://docs.oasis-open.org/ws-sx/ws-trust/200512/"; > - wst namespace -> > xmlns:wst="http://docs.oasis-open.org/ws-sx/ws-trust/200512"; > (one has "/" at the end, another not) > and for the one of element definition: <xs:element > name="RequestSecurityTokenCollection" > type="wst:RequestSecurityTokenCollectionType"/> > but the Type definition: <xs:complexType > name="RequestSecurityTokenCollectionType"> > (one is the namespace with "/" another is in the namespace without "/") > > Is this OK? > (and what is the namespace for the request/response: with or without "/"?) > > Thanx: > > Csaba > > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
