That file is referenced in the cxf.xml
(https://github.com/gmazza/blog-samples/blob/master/cxf_sts_tutorial/client/src/main/resources/cxf.xml)
and used by the SOAP client to determine the authentication method it
needs to use when interacting with the STS. (It might be redundant in
cases where the SOAP client makes a MEX--MetadataExchange--call to
retrieve that same WSDL--I'd have to look more into that.)
Yes, it should be the same as the STS WSDL -- it looks duplicative only
because the sample tutorial bundles the STS and WSC together but
normally separate teams would be handling each component, each with a
copy of the WSDL in their own project
Glen
On 05/25/2012 10:08 AM, Gina Choi wrote:
Hi Glen,
I was looking at
http://svn.apache.org/viewvc/cxf/fediz/trunk/services/sts/src/main/webapp/WEB-INF/cxf-ut.xml?view=markup.
Later I was able to fix it based on apache-cxf-2.6.0-src.
You have DoubleItSTSService.wsdl file under \client\src\main\resources
as well. What is role of the wsdl file in client side? The content
should be same as sts side?
Thanks.
Gina
On Thu, May 24, 2012 at 10:06 PM, Glen Mazza <[email protected]
<mailto:[email protected]>> wrote:
Hmm, the sample doesn't have encryptionName under utService:
http://svn.apache.org/viewvc/ cxf/trunk/distribution/src/
main/release/samples/sts/src/ demo/wssec/sts/wssec-sts.xml?
revision=1190520&view=markup# l69
<http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/sts/src/demo/wssec/sts/wssec-sts.xml?revision=1190520&view=markup#l69>
I'm not sure why you're placing such a property in.
Glen
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
