I debugged my client to check following error messages that I am receiving
when I run client. I found cause for NPE. In
org.apache.cxf.ws.security.wss4j.policyhandlers.TransportBindingHandler.java,
we have doIssuedTokenSignature( Token token, SignedEncryptedParts
signdParts, TokenWrapper wrapper)
With 2.6.1 hopefully going out shortly, I'd like to get peoples thoughts
about creating a 2.6.x-fixes branch and changing trunk to target 2.7. Here
is a list of some things I'd like to start thinking about for 2.7:
1) Drop support for Java 5 - this may be a bit contentious. :-) It would
si
On Thursday, May 31, 2012 09:34:43 PM Oliver Wulff wrote:
> One question from my side. The distribution package can be downloaded
> here:
> https://repository.apache.org/content/groups/snapshots/org/apache/cxf/fed
> iz/apache-fediz/1.0.0-SNAPSHOT/
>
> The CXF download page has got the following do
Hi Oli,
It's almost there from my POV. I'd like to see better exception handling
and (especially) better unit testing of the core plugin before the release
goes out.
Colm.
On Thu, May 31, 2012 at 10:34 PM, Oliver Wulff wrote:
> Hi guys
>
> I'd like to get the first release out of Fediz within
Hi Gina
I guess it's the same policy flaw with KeyValueToken - at least the error
message is the same.
Thanks
Oli
--
Oliver Wulff
Blog: http://owulff.blogspot.com
Solution Architect
http://coders.talend.com
Talend Application Integration Division http://www.talend.com
_
+1
Willem
On 5/31/12 2:15 AM, Daniel Kulp wrote:
We've resolved over 90 issues since 2.6.0 was released. We've back ported
over 70 of them to 2.5.4 and 40 to 2.4.8 and 25 to 2.3.11.
List of issues:
2.3.11:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=123
