+1.
Colm.
On Fri, Jan 20, 2012 at 12:08 AM, Daniel Kulp dk...@apache.org wrote:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out. We've
also ported back over 25 of the fixes to 2.4.6 and 8
+1
Cheers, Sergey
On 20/01/12 00:08, Daniel Kulp wrote:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out. We've
also ported back over 25 of the fixes to 2.4.6 and 8 of those to 2.3.9.
List
+1 (non binding)
Tested in Karaf 2.2.5.
Regards
JB
On 01/20/2012 01:08 AM, Daniel Kulp wrote:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out. We've
also ported back over 25 of the fixes to
+1
David.
On 20 January 2012 00:08, Daniel Kulp dk...@apache.org wrote:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out. We've
also ported back over 25 of the fixes to 2.4.6 and 8 of those
+1
Christian
Am 20.01.2012 01:08, schrieb Daniel Kulp:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out. We've
also ported back over 25 of the fixes to 2.4.6 and 8 of those to 2.3.9.
List of
Hi,
Just a proposal for small improvements in Wss4jInInterceptor.
Normally CryptoProvider doesn't instantiated directly via CryptoFactory, but
firstly tried to be obtained from message context properties
(SecurityConstants.ENCRYPT_CRYPTO, SecurityConstants.SIGNATURE_CRYPTO). And
only if the
Hi !
I've a strange problem with the uploading file with pics.
When I uplaod a simple RTF file the content of the file is ok. But when I
insert the same file with a simple pics inside the content of the file is
empty.
Please find my interface :
@POST
@Consumes(multipart/form-data)
public
Hello,
I'm develop a bundle to export a service, and I'm using DOSGi (multi-bundle
distribution) and Apache-Felix.
I install my bundle and, when DOSGi detects, ApacheFelix lunch these
exceptions:
g! ERROR: Bundle cxf-dosgi-ri-discovery-local [46] EventDispatcher: Error
during
dispatch.
+1
Aki
2012/1/20 Daniel Kulp dk...@apache.org:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out. We've
also ported back over 25 of the fixes to 2.4.6 and 8 of those to 2.3.9.
List of
Alexey Markevich found a critical bug that prevents CXF from working in
OSGi.
https://issues.apache.org/jira/browse/CXF-4050
I forgot to change the Activator name in the poms when backporting a
refactoring.
Committed the fix.
I think we should redo the release. So reverting to
-1
Sorry
Hi Christian,
I didn't see it when testing with JAX-RS endpoint.
Let me try again to be sure.
Regards
JB
On 01/20/2012 03:02 PM, Christian Schneider wrote:
Alexey Markevich found a critical bug that prevents CXF from working in
OSGi.
https://issues.apache.org/jira/browse/CXF-4050
I forgot to
Hi Christian,
you are right.
I had some automatic tests that didn't report this problem (or was not
pulling 2.5.2 correctly, maybe) :-(
I saw the problem now after manually trying some scenarios.
regards, aki
2012/1/20 Christian Schneider ch...@die-schneider.net:
Alexey Markevich found a
I'm canceling this vote due to the OSGi issues that have been discovered.
With the fix in, I'm starting the rebuild process now.
Dan
On Thursday, January 19, 2012 7:08:44 PM Daniel Kulp wrote:
We've resolved over 45 issues since 2.5.1. Most importantly, several of
them were regressions
On Thursday, January 19, 2012 2:43:39 PM Christian Schneider wrote:
Hi all,
I propose we move the common-utilities project to the cxf api.
The API depends on this project and basically all other prohects in cxf
depend on the API. So I think it makes no real sense to split these into
two
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out. We've
also ported back over 25 of the fixes to 2.4.6 and 8 of those to 2.3.9.
This is the second attempt at this release which fixes the issues
+1
Jeff
On Jan 20, 2012, at 10:56 AM, Daniel Kulp wrote:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out.
We've
also ported back over 25 of the fixes to 2.4.6 and 8 of those to 2.3.9.
+1.
Colm.
On Fri, Jan 20, 2012 at 6:02 PM, Jeff Genender jgenen...@apache.org wrote:
+1
Jeff
On Jan 20, 2012, at 10:56 AM, Daniel Kulp wrote:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release
+1
Cheers
Alessio
On 01/20/2012 06:56 PM, Daniel Kulp wrote:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out.
We've
also ported back over 25 of the fixes to 2.4.6 and 8 of those to
+1
Aki
2012/1/20 Daniel Kulp dk...@apache.org:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out. We've
also ported back over 25 of the fixes to 2.4.6 and 8 of those to 2.3.9.
This is the
+1
Sergey
On 20/01/12 17:56, Daniel Kulp wrote:
We've resolved over 45 issues since 2.5.1. Most importantly, several of them
were regressions since 2.5.0 and thus we need to get a new release out. We've
also ported back over 25 of the fixes to 2.4.6 and 8 of those to 2.3.9.
This is the
20 matches
Mail list logo