I got this spun up but CXF doesn't seem to be acknowledging that I have
provided a custom interceptor. I use spring to provision endpoints, here is
an excerpt of my service definition:
I am operating in an environment where I communicate with web services to a
group of organization with certs signed by a common CA. This set of
organizations is mutable, and I don't want to manage my truststore everytime
a new organization joins. However, per my understanding of the
specifications
I am operating in an environment where I communicate with web services to a
group of organization with certs signed by a common CA. This set of
organizations is mutable, and I don't want to manage my truststore everytime
a new organization joins. However, per my understanding of the
specifications
The error I am seeing with the latest set up is:
Interceptor for
{urn:ihe:iti:xdr:2007}DocumentRepositoryXDR_Service#{urn:ihe:iti:xdr:2007}DocumentRepository_ProvideAndRegisterDocumentSet-b
has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: These policy alternatives can not be
sa
I have been able to resolve the mtom policy issue by making the mtom policy
optional as I want to allow users of my endpoint to have the option of
sending binaries inlined or attached. My updated wsdl is below. The rest of
my policies however are not optional, I need them all to be verified. My
mes
So I did something silly and attached my pre "making MTOM optional" changes.
I'll upload the new wsdl shortly, as I am trying one other thing... my WSDL
also has MTOM policy twice...
--
View this message in context:
http://cxf.547215.n5.nabble.com/ws-security-server-tp5709138p5709145.html
Sent fr
Hi. I have successfully created a client with web service security but I am
now having trouble on the receiving side. I would have thought that the
stack would automatically put together my policy based interceptors together
based on my wsdl, and actually it seems like that is the case but then I r
