Hi Dan,
thanks for the time for Jim to investigate this a bit further.
I agree on the whole line below btw.
Cheers
Alessio
On 01/20/2011 06:08 AM, Daniel Kulp wrote:
I want to give Jim a bit more time to investigate what is causing the
failures. I chatted with him a bit on IRC and I'm not exac
+1
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: 18 January 2011 04:26
To: dev@cxf.apache.org
Subject: [VOTE] Apache CXF 2.3.2
We've had a busy 8 weeks or so despite the holidays. We've managed to fix
over 75 JIRA issues since 2.3.1 which is quite remarkable .
+1
On Tue, Jan 18, 2011 at 05:26, Daniel Kulp wrote:
>
> We've had a busy 8 weeks or so despite the holidays. We've managed to fix
> over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes
> a bunch of OSGi related issues that are needed for
> Camel and ServiceMix.
>
> No
Hi,
I've tried out the setup.eclipse profile for setting up my workspace for Helios
and several questions
* Is it by intention that the Checkstyle profile created is not activated by
default ?
* Looks like the checkstyle setup could be simplified by styling once, then
copying to the alte
Hi,
I've tried out the setup.eclipse profile for setting up my workspace for Helios
and several questions
* Is it by intention that the Checkstyle profile created is not activated by
default ?
* Looks like the checkstyle setup could be simplified by styling once, then
copying to the alte
Oops... Sorry.. The second post was an accident :-(
--
Jürgen Kindler
Dan,
Thanks. How embarassing.
Does the JAX-WS spec give us any leeway in offering a feature to close
up these streams by magic when the service function returns? Aside, of
course, from the possibility that someone wants to hang onto one.
--benson
On Wed, Jan 19, 2011 at 2:35 PM, Daniel Kulp w
Thanks Dan. My fix to CXF-3209 introduced these regression failures
. I've reverted these changes in 2.3.x branch . I'll look this issue
again and provide some better test for it .
On Thu, Jan 20, 2011 at 1:08 PM, Daniel Kulp wrote:
>
> I want to give Jim a bit more time to investigate what is
OK, at least it's clear what the situation is :-)
With my Apache hat on, here is my +1 to the 2.3.2 release, even with
this issue the release is fine.
We'll fix this in 2.3.3 ;-)
Cheers
Alessio
On 01/20/2011 02:11 PM, Jim Ma wrote:
Thanks Dan. My fix to CXF-3209 introduced these regression f
On Thursday 20 January 2011 3:15:23 am Jürgen Kindler wrote:
> Hi,
>
> I've tried out the setup.eclipse profile for setting up my workspace for
> Helios and several questions
A lot of the issues on this list are possibly historical. The setup.eclipse
stuff was setup probably 4-5 years ago, lik
On Thursday 20 January 2011 7:30:09 am Benson Margulies wrote:
> Dan,
>
> Thanks. How embarassing.
>
> Does the JAX-WS spec give us any leeway in offering a feature to close
> up these streams by magic when the service function returns? Aside, of
> course, from the possibility that someone wants
I wasn't clear.
We *could* define the model to be
try {
call_function_in_sib();
} finally {
stream.close();
}
but that would not work for anyone inclined to hang onto the stream
like grim death. The gc does clean this up, but if you have lots of
VM, it has no reason to be in a hurry to fin
On Thursday 20 January 2011 2:49:53 am Dennis Sosnoski wrote:
> On 01/20/2011 08:19 AM, Daniel Kulp wrote:
> > On Wednesday 19 January 2011 5:24:58 am Dennis Sosnoski wrote:
> >> ...
> >>
> >> In order to implement the receive handling, I need to be able to
> >> short-circuit the processing of an
On 01/21/2011 10:57 AM, Daniel Kulp wrote:
> On Thursday 20 January 2011 2:49:53 am Dennis Sosnoski wrote:
>
> ..
>
>> The WS-RM code does implement duplicate message checks if AtMostOnce is
>> specified (in org.apache.cxf.ws.rm.DestinationSequence), in which case
>> it throws
Ah, I think I see how response handling is supposed to work in WS-RM.
CreateSequence can optionally offer to create a separate sequence for
the opposite direction. I'd say the offer should always be configured in
policy when using a request-response MEP, and should always be accepted
by the destina
We have 14 +1 votes with (10 binding).
There is a -1 vote from Jim Ma. It relates to a J2EE TCK failure. However,
the standalone TCK's do pass so that doesn't affect CXF when used standalone.
It would only affect app servers embedding CXF.
Thus, I'm going to mark this vote as passed and
16 matches
Mail list logo
