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 in-bound message in an interceptor so
>> that no further processing is
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 exactly sure how the
test is SUPPOSED to work at all so it's hard to say what is going on.
THAT said, -1's on release votes are not a veto. Thus, as release manager,
it
I don't think a new vote is necessary, because as stated the vote covers
both portions. So everyone has voted +1 and +1 up to Jim.
To be valid, a veto must have a justifiable reason, and Jim certainly
does have one for CXF 2.3.2 but not CXF XJC 2.3.2, so the latter can
still proceed (if desir
Maybe we can consider to release XJC 2.3.2 as it doesn't relate to TCK
failures. And we don't need to cut new version of XJC 2.3.2 again.
Can we start a new vote for CXF XJC 2.3.2 ?
Willem
On 1/20/11 11:02 AM, Jim Ma wrote:
I have to vote -1 for this release.
The new changes in tagged CXF 2.3.
I have to vote -1 for this release.
The new changes in tagged CXF 2.3.2 introduced several JEE6 TCK
regression failures . I am looking for a quick fix for these failures.
Jim
On Wed, Jan 19, 2011 at 8:28 AM, Eric Johnson wrote:
> +1
>
> On Tue, Jan 18, 2011 at 6:31 PM, Christian Schneider
> wr
On Wednesday 19 January 2011 1:56:35 pm Benson Margulies wrote:
> Ian has cooked up test case for our woes with with wierd timeouts with
> MTOM. Let us know if we can help further.
>
> https://issues.apache.org/jira/browse/CXF-3259
The client isn't closing the streams. If you do:
DataHandler
On Wednesday 19 January 2011 5:24:58 am Dennis Sosnoski wrote:
> I've verified that the current WS-RM code only implements transmit
> handling (retry until acknowledged). A correct WS-RM implementation also
> requires receive handling, to postpone the delivery of messages received
> out of order wh
Ian has cooked up test case for our woes with with wierd timeouts with
MTOM. Let us know if we can help further.
https://issues.apache.org/jira/browse/CXF-3259
I've verified that the current WS-RM code only implements transmit
handling (retry until acknowledged). A correct WS-RM implementation also
requires receive handling, to postpone the delivery of messages received
out of order when InOrder delivery assurance is used, and to block the
delivery of dup
Christian has fixed it in 2.3.2 (being voted for now), most likely the
server is sending an HTTP error status, with no response body...
Cheers, Sergey
On Wed, Jan 19, 2011 at 3:21 AM, cxfuser71 wrote:
>
> Hello All,
> I am using JBoss 6.0.GA release which comes with CXF webservice stack
> (vers
10 matches
Mail list logo