+1,
Andrei.
> -Original Message-
> From: Daniel Kulp [mailto:dk...@apache.org]
> Sent: Dienstag, 7. Oktober 2014 22:00
> To: dev@cxf.apache.org
> Subject: [VOTE] CXF 2.6.16
>
> This is a vote to release CXF 2.6.16. This release is JUST to fix the
> problems
> running 2.6.15 with Java5
https://issues.apache.org/jira/browse/WSS-516
On 08/10/2014 10:19 AM, "Jason Pell" wrote:
> Would it be acceptable to change cxf to set the saml version on the Saml
> callback before calling the callback.
>
> I want to be able to create a bearer token inside a local callback and I
> want to hand
+1
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
On 2014-10-8, at 上午3:59, Daniel Kulp wrote:
> This is a vote to release CXF 2.6.16. This release is JUST to fix the
> problems running 2.6.15 with Java5. All the changes between 2.6.15 and
> 2.6.16 are dir
Just an follow up…
I was able to fix all the java5 issues and build 2.6.15 and the vote is
started.2.7.13 is built and staged, but I want to look at the staging real
quick before I call the vote.However, I’ve been struggling trying to get
3.0.2 built. I’ve had all kinds of various fa
Would it be acceptable to change cxf to set the saml version on the Saml
callback before calling the callback.
I want to be able to create a bearer token inside a local callback and I
want to handle saml 1 and 2 automatically based on the wsdl WS policy. At
the moment I can't do that. If I could c
+1
Andriy
DK> This is a vote to release CXF 2.6.16. This release is JUST to fix the
problems running 2.6.15 with Java5. All
DK> the changes between 2.6.15 and 2.6.16 are directly related to getting it to
build, run, and test with Java5. This
DK> does include downgrading a couple of depende
+1
Cheers, Sergey
On 07/10/14 20:59, Daniel Kulp wrote:
This is a vote to release CXF 2.6.16. This release is JUST to fix the
problems running 2.6.15 with Java5. All the changes between 2.6.15 and 2.6.16
are directly related to getting it to build, run, and test with Java5. This
does inc
+1
Jeff
On Oct 7, 2014, at 1:59 PM, Daniel Kulp wrote:
> This is a vote to release CXF 2.6.16. This release is JUST to fix the
> problems running 2.6.15 with Java5. All the changes between 2.6.15 and
> 2.6.16 are directly related to getting it to build, run, and test with Java5.
> This
+1
- Dennis
On 10/08/2014 08:59 AM, Daniel Kulp wrote:
This is a vote to release CXF 2.6.16. This release is JUST to fix the
problems running 2.6.15 with Java5. All the changes between 2.6.15 and 2.6.16
are directly related to getting it to build, run, and test with Java5. This
does i
This is a vote to release CXF 2.6.16. This release is JUST to fix the
problems running 2.6.15 with Java5. All the changes between 2.6.15 and 2.6.16
are directly related to getting it to build, run, and test with Java5. This
does include downgrading a couple of dependencies back to the 2.6.1
Github user asfgit closed the pull request at:
https://github.com/apache/cxf/pull/24
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
When IBM’s java 7 came out, we got bit by this pretty hard as it would garbage
collect the proxy before the invokes were complete. Many of our system tests
and such were failing. I did a bunch of experimenting with the IBM jdk to
find something that would work. I settled on:
git diff
f
Daniel,
We're still being bitten by CXF-6010 [1] for which the fix is a simple one
line null-check. Would be great to see that fixed so we can re-enable
schema validation for our tests.
The fix is rather trivial, but I've attached a patch to CXF-6010 for it
anyhow.
[1] https://issues.apache.org/
Hi,
some of you might already be aware that the finalize mechanism in the
JVM is basically flawed and there could be issues even when it's used
for commonly accepted reasons (like cleaning up stuff that the user
forgot about). A very interesting presentation has been recently made
available on
14 matches
Mail list logo
