For the record, we always perform committer votes on the public list.
Them's the rules. We might have a private discussion if there are
issues.
On Tue, Nov 11, 2008 at 8:50 PM, Willem Jiang <[EMAIL PROTECTED]> wrote:
> Here is my +1.
>
> Willem
>
> Eoghan Glynn wrote:
>> Folks,
>>
>> I'd like to p
+1
On Wed, Nov 12, 2008 at 9:50 AM, Willem Jiang <[EMAIL PROTECTED]>wrote:
> Here is my +1.
>
> Willem
>
> Eoghan Glynn wrote:
> > Folks,
> >
> > I'd like to propose David Bosschaert for CXF committership, on the basis
> of
> >
> > - the many quality patches he's submitted for our CXF-based distr
Here is my +1.
Willem
Eoghan Glynn wrote:
> Folks,
>
> I'd like to propose David Bosschaert for CXF committership, on the basis of
>
> - the many quality patches he's submitted for our CXF-based distributed OSGi
> reference implementation
>
> - his community participation especially in drivi
+1
Freeman
Eoghan Glynn wrote:
Folks,
I'd like to propose David Bosschaert for CXF committership, on the basis of
- the many quality patches he's submitted for our CXF-based distributed OSGi
reference implementation
- his community participation especially in driving the re-integration of
+1
Eoghan Glynn schrieb:
Folks,
I'd like to propose David Bosschaert for CXF committership, on the basis of
- the many quality patches he's submitted for our CXF-based distributed OSGi
reference implementation
- his community participation especially in driving the re-integration of the
F
Dan wrote:
>>Hmm... that's not good. What problem are you having?
I'm not sure what I was smoking at the time, but it is building fine
now.
--Erik
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2008 11:45 AM
To: dev@cxf.apache.org
Cc: Osterm
+1
On Nov 11, 2008, at 11:09 AM, Daniel Kulp wrote:
+1 for me.
Dan
On Tuesday 11 November 2008 10:57:28 am Eoghan Glynn wrote:
Folks,
I'd like to propose David Bosschaert for CXF committership, on the
basis of
- the many quality patches he's submitted for our CXF-based
distributed
On Tuesday 11 November 2008 2:04:25 pm Guillaume Nodet wrote:
> Btw, votes on people are usually held on the private mailing list to
> avoid potential problems.
Not for CXF. Every vote we've ever done for committer has been public.
(PMC votes have been on the private PMC list) However, there
+1 for me.
Dan
On Tuesday 11 November 2008 10:57:28 am Eoghan Glynn wrote:
> Folks,
>
> I'd like to propose David Bosschaert for CXF committership, on the basis of
>
> - the many quality patches he's submitted for our CXF-based distributed
> OSGi reference implementation
>
> - his community par
+1
Btw, votes on people are usually held on the private mailing list to
avoid potential problems.
On Tue, Nov 11, 2008 at 4:57 PM, Eoghan Glynn <[EMAIL PROTECTED]> wrote:
>
> Folks,
>
> I'd like to propose David Bosschaert for CXF committership, on the basis of
>
> - the many quality patches he's
I would really encourage you to take a look at the smx code for
handling continuations.
We've had quite a hard time to handle race conditions, timeouts etc...
because the continuation has a timeout and when the message is
received back around the timeout, things can become a bit tricky.
https://sv
This is something I'm kind of "on the fence" about. There are definitely use
cases where having the other services/ports in the wsdl so this behavior
definitely would need to be optional.
The usecases that I have in mind:
1) Clustering/Failover - the clustering/failover stuff kind of relies
Hi, seeing this NPE with the latest trunk :
T E S T S
---
Running org.apache.cxf.systest.multitransport.MultiTransportClientServerTest
Exception in thread "DefaultMessageListenerContainer-1" java.lang.NullPointerExc
eption
at java.lang.St
Yea, I think it's caused by the move from Spring 2.5.4 to 2.5.6.The Spring
JMS stuff doesn't seem to tolerate an ungraceful shutdown which is what I
think is happening. I want to dig in a bit furthur and possibly log a bug
with Spring, just haven't had the time.
Dan
On Tuesday 11 Novem
+1,
I have worked with David in past and he will surely be an asset to CXF
given the knowledge he would bring in on general WS-* stuff and mainly OSGI.
-- Ulhas
Eoghan Glynn wrote:
Folks,
I'd like to propose David Bosschaert for CXF committership, on the basis of
- the many quality patches
Hi
I have 10 threads involved, 5 control ones + 5 application ones, I see a
loss of message approximately once in 5 cases. The fact that cont.resume()
is done virtually immediately after cont.suspend() can explain it.
Without seeing your code, I cannot really offer valid suggestions, but I'll
+1
-> richard
Eoghan Glynn wrote:
Folks,
I'd like to propose David Bosschaert for CXF committership, on the basis of
- the many quality patches he's submitted for our CXF-based distributed OSGi
reference implementation
- his community participation especially in driving the re-integratio
On Thursday 06 November 2008 11:23:41 am Ostermueller, Erik wrote:
> I had trouble building the 2.1.3 source distribution,
Hmm... that's not good. What problem are you having?
> so I'm trying to
> build the lastest svn code.
No idea what would cause this. Maybe the path ends up too long for
On Friday 07 November 2008 8:56:46 am Sergey Beryozkin wrote:
> That said :-), even with this extremely small time window I'm getting log
> warnings. I guess it's due to a nature of my tests. I have contol threads
> waiting in the application code which do continuation.resume() as soon as
> they're
Sounds good. +1
Glen
Sergey Beryozkin-3 wrote:
>
> +1
>
> David is working very hard indeed to ensure CXF, being the core component
> of DOSGI RI , is recognized in the OSGI community, so
> having David on board will be very good for CXF.
>
> Cheers, Sergey
>
> - Original Message ---
I think I see the issue. If jms102 support is enabled, we need to create a
SingleConnectionFactory102 instead of SingleConnectionFactory. Probably
should check the spring-jms jar for other classes ending in 102 to see if we
need to change anything else.
Dan
On Tuesday 11 November 2008 2:
Hi Christian,
Our configuration is wsdl based. Here is the service description:
Regards,
Seumas
-Original Message-
From: Christian Schneider [mailto:[EMAIL PROTECTED]
Sent: T
+1
On Tue, Nov 11, 2008 at 10:57 AM, Eoghan Glynn <[EMAIL PROTECTED]> wrote:
>
> Folks,
>
> I'd like to propose David Bosschaert for CXF committership, on the basis of
>
> - the many quality patches he's submitted for our CXF-based distributed OSGi
> reference implementation
>
> - his community p
+1
David is working very hard indeed to ensure CXF, being the core component of DOSGI RI , is recognized in the OSGI community, so
having David on board will be very good for CXF.
Cheers, Sergey
- Original Message -
From: "Eoghan Glynn" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, Novem
Folks,
I'd like to propose David Bosschaert for CXF committership, on the basis of
- the many quality patches he's submitted for our CXF-based distributed OSGi
reference implementation
- his community participation especially in driving the re-integration of the
Felix fork in the CXF sandox
I have just upgraded to CXF 2.1.3 and am running against an old
implementation of SonicMQ version 5, which I believe based upon the old
1.0.2 apis. However, I am still getting a stack which indicates that CXF
does still not seem compatible with older versions of JMS. Clearly the
stack show that a J
26 matches
Mail list logo
