Well, seems that the approach of "contract-last" on the webservice creation
could be the issue. Changed to "contract-first" we now actually can get the
sts client to create the RST. We now just have to find out why the RST SOAP
message gets configured with SOAP1.1 when it should be 1.2. Namespaces
(Please forgive me if this is the wrong place for this)
Class QNamesMap has a private member QName[] values.
In the class' get method, if it finds a QName whose NamespaceURI
matches the NamespaceURI of the passed argument but whose LocalPart
doesn't match, it evaluates a conditional expression w
In my CXF STS using 2.7.12-SNAPSHOT and running on Tomcat 7.0.52, I get several
messages in the logs whenever I undeploy the STS app:
SEVERE: The web application [/STS] created a ThreadLocal with key of type
[java.lang.ThreadLocal] (value [java.lang.ThreadLocal@84421d]) and a value of
type [org
It seems it is firewall problem. Use the dongle(Any other network other than
your office network). Problem will be solved.
Hi Guys!
Thanks for your replies, I will try to supply the requested information.
This is the loop that occurs around and around (the object reference in the
logs will change though).
>From the stacktrace even further below it could suggest that the endpoint
read from the ADFS is not properly se
