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
+1 for both branching out and dropping Java 5 Support.
Regards,
Ulhas Bhole
On 5 Jun 2012, at 10:11, Colm O hEigeartaigh wrote:
> +1.
>
> I intend on introducing streaming WS-Security support in 2.7, which will
> depend on Santuario 2.0 and WSS4J 2.0, both of which are slated to require
> JD
+1.
I intend on introducing streaming WS-Security support in 2.7, which will
depend on Santuario 2.0 and WSS4J 2.0, both of which are slated to require
JDK 1.6.
Colm.
On Fri, Jun 1, 2012 at 4:10 PM, Daniel Kulp wrote:
>
> With 2.6.1 hopefully going out shortly, I'd like to get peoples thoughts
Yep something like that would be fine.
Colm.
On Mon, Jun 4, 2012 at 10:17 PM, Oliver Wulff wrote:
> Colm, do you have something similar in mind as for the STS:
>
> example:
> throw new FedizRuntimeException("Error in validating token", ex,
> FedizRuntimeException.TOKEN_EXPIRED);
>
> Thanks
> Ol
