Re: To spring 3 or not to spring 3

2010-07-17 Thread Cyrille Le Clerc
+1 for upgrading to Spring 3 and Jetty 7. Cyrille On Fri, Jul 16, 2010 at 11:14 PM, Daniel Kulp wrote: > > Since we are getting close to having 2.3 ready to release, I'm kind of looking > at the various deps to see if there are updates we should grab or not. > Things like woodstox and abdera and

Re: DOSGI: Update to CXF 2.2.9

2010-07-17 Thread Eoghan Glynn
> I think we're ready for a release! Great! > Eoghan would you have some cycles? Yeah. A couple of things before I go ahead and cut the release: - can you update the release notes[1] with a summary of what's new in this release? - does this TimeoutException[2] in TestExportService.testAccessE

Re: To spring 3 or not to spring 3

2010-07-17 Thread Craig Tataryn
I think +1 for Spring 3, if a company is going to make the leap to CXF 2.3, they are probably willing to make the jump to Spring 3.0. Would there actually be any @since 3.0 features you'd use from Spring? Or would it be possible they could still operate with 2.5.6 by doing maven excludes on th

Re: To spring 3 or not to spring 3

2010-07-17 Thread Daniel Kulp
On Saturday 17 July 2010 11:11:03 am Craig Tataryn wrote: > I think +1 for Spring 3, if a company is going to make the leap to CXF 2.3, > they are probably willing to make the jump to Spring 3.0. > > Would there actually be any @since 3.0 features you'd use from Spring? Or > would it be possible

Re: jetty 7: CXF-2898

2010-07-17 Thread Daniel Kulp
On Thursday 15 July 2010 9:53:28 pm Benson Margulies wrote: > The continuation code is very different. I attached a first pass > patch. It does not pass unit tests because I am completely flummoxed > by mock, and I may not understand what's going on with the > continuations. Digging into this a bi

Re: To spring 3 or not to spring 3

2010-07-17 Thread Craig Tataryn
On 2010-07-17, at 11:00 AM, Daniel Kulp wrote: > On Saturday 17 July 2010 11:11:03 am Craig Tataryn wrote: >> I think +1 for Spring 3, if a company is going to make the leap to CXF 2.3, >> they are probably willing to make the jump to Spring 3.0. >> >> Would there actually be any @since 3.0 feat