I think that's only if you provide an EPR (endpoint reference) in the
WSP's WSDL, right? If you haven't configured an EPR but instead are
relying on the sp:Issuer/wsaw:Metadata element like Metro STS's uses
(https://raw.github.com/gmazza/blog-samples/master/cxf_sts_tutorial/service/src/main/resources/DoubleIt.wsdl)
-- no MEX call will be made. Then again, I'm unsure if CXF's STSClient
actually even reads any sp:Issuer/wsaw:Metadata configuration in the
WSP--it may just rely on EPR alone, and not make a MEX call if that
element is not present. Do you have any info on this (and
which--wsaw:Metadata or EPR--take precedence with the CXF client?)
Thanks,
Glen
On 09/06/2012 01:02 PM, Alessio Soldano wrote:
AFAIR CXF clients will try using STS wsdl epr address to perform WS-MEX
calls by default. This can be disabled by using the
ws-security.sts.disable-wsmex-call-using-epr-address option [1].
[1] https://issues.apache.org/jira/browse/CXF-4308
On 09/06/2012 06:49 PM, Glen Mazza wrote:
My experience is that only Metro and not CXF clients make such "MEX"
(metadata exchange) calls:
http://www.jroller.com/gmazza/entry/wstrust_soap_call_analysis (Listing
#1). The CXF STS can handle MEX calls from Metro clients, but CXF
clients don't bother making them (that's by default, I'm not sure how to
force a CXF client to make the MEX call.)
Glen
On 09/06/2012 12:10 PM, Jay Walters wrote:
I am hoping this is nottoo obvious a question. I was unable to find
anything quick on the website.
We are using WS-trust from metro which does download and parse the
wsdl eachtime we connect to a service from the client, I would like to
confirm whether CXFhas a similar feature.
Thanks
Jay Walters
--
Glen Mazza
Talend Community Coders - coders.talend.com
http://www.jroller.com/gmazza/entry/blog_article_index
