Some of the imports in my Maven plugin was not specifying a path. Thus, when I ran my TestNG test with the client STS code it was loading 2.5.2 instead of 2.7.2 and as the exception message clearly indicates the method it was looking for was not implemented in the 2.5.2 version of the class. It's remarkable how useful the exception message is once you've experienced the pain of "deciphering" it for the first time. I'm quite sure I'll never forget this lesson.
-- View this message in context: http://cxf.547215.n5.nabble.com/STSClient-requestSecurityToken-exception-tp5723546p5723585.html Sent from the cxf-user mailing list archive at Nabble.com.
