[VOTE] Release CXF 2.0.9

2008-10-10 Thread Willem Jiang
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is a vote to release CXF 2.0.9 Once again, there have been a bunch of bug fixes and enhancements that have been done compared to the 2.0.9 release. Over 37 JIRA issues are resolved for 2.0.9 which is a large number of fixes for the 2.0.x branc

Re: [VOTE] Release CXF 2.0.9

2008-10-10 Thread Benson Margulies
+1 On Fri, Oct 10, 2008 at 8:48 AM, Willem Jiang <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > This is a vote to release CXF 2.0.9 > > Once again, there have been a bunch of bug fixes and enhancements that > have been done compared to the 2.0.9 release. Over 37

Re: [VOTE] Release CXF 2.0.9

2008-10-10 Thread Ulhas Bhole
+1 -- Ulhas Willem Jiang wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is a vote to release CXF 2.0.9 Once again, there have been a bunch of bug fixes and enhancements that have been done compared to the 2.0.9 release. Over 37 JIRA issues are resolved for 2.0.9 which is a large

Re: How to handle a configuration problem generally in CXF code

2008-10-10 Thread Benson Margulies
Are you sure that none of the tools are using the Message class directly? The message class still seems to be good modularity to me. I'm +1 on the new constructors, all the same. On Wed, Oct 8, 2008 at 7:17 PM, Christian Schneider <[EMAIL PROTECTED]> wrote: > I would propose to add the following

Re: [VOTE] Release CXF 2.0.9

2008-10-10 Thread Daniel Kulp
+1 - looks good Dan On Friday 10 October 2008 8:48:15 am Willem Jiang wrote: > This is a vote to release CXF 2.0.9 > > Once again, there have been a bunch of bug fixes and enhancements that > have been done compared to the 2.0.9 release. Over 37 JIRA issues > are resolved for 2.0.9 which is a

Re: [VOTE] Release CXF 2.0.9

2008-10-10 Thread Bharath Ganesh
+1 On Fri, Oct 10, 2008 at 6:18 PM, Willem Jiang <[EMAIL PROTECTED]>wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > This is a vote to release CXF 2.0.9 > > Once again, there have been a bunch of bug fixes and enhancements that > have been done compared to the 2.0.9 release. Over 37

Re: [VOTE] Release CXF 2.0.9

2008-10-10 Thread Jeff Genender
+1 On Oct 10, 2008, at 8:26 AM, Bharath Ganesh wrote: +1 On Fri, Oct 10, 2008 at 6:18 PM, Willem Jiang <[EMAIL PROTECTED]>wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is a vote to release CXF 2.0.9 Once again, there have been a bunch of bug fixes and enhancements that ha

Re: Wiki JAX-RS(JSR-311) documentation

2008-10-10 Thread Sergey Beryozkin
Hi , fixed now - thanks for pointing it out Cheers, Sergey There are an error on page: http://cwiki.apache.org/CXF20DOC/jax-rs-jsr-311.html the code: Should be: I tried to fix by myself, bu I don't have permission for that. Regards, Ricardo -- Ricardo Pai

JMS 1.0.2 support......

2008-10-10 Thread Daniel Kulp
Christian, The old JMS transport pretty much just used the JMS 1.0.2 API's so it worked with old versions of JMS providers and such. The new stuff seems to default to 1.1 which is causing issues.I see that if you use the new config, it's settable. However, if you use the old wsdl based

Re: Memory leak in CXF HTTP transport in Solaris ?

2008-10-10 Thread anoopPrasad
Dear Bharat, I have observed the same behavior. Allow me to present the details u seek. Server: Created a Sample HTTP Service with CXF 2.0.3(publishing Greeter interface provided in sample ) Service was published using : Endpoint ep = Endpoint.publish("http://localhost:9000/Greeter";, new Greet

Re: Aegis versus jaxrs

2008-10-10 Thread Sergey Beryozkin
Hi Benson I'm sorry If I'm too slow :-) but I'm still not getting what is it that you're proposing. That said, I believe that may be we should postponse the discussion on how to improve the overall JAX-RS implementation until after it reaches 1.0. In meantime, if we had even a basic JAX-RS Aeg

Re: Aegis versus jaxrs

2008-10-10 Thread Benson Margulies
Sergey, I'm not feeling like I'm doing a very good job of explaining myself here. It's probably true that the best way for me to proceed is to code something and with some comments that say: 'Sergey, I'm frustrated HERE.' I've not been having the time to do more for CXF than to address users with

Re: Aegis versus jaxrs

2008-10-10 Thread Sergey Beryozkin
Hi Sergey, I'm not feeling like I'm doing a very good job of explaining myself here. It's probably true that the best way for me to proceed is to code something and with some comments that say: 'Sergey, I'm frustrated HERE.' ... Yea, please do it :-) ! I do hope though that you wouldn't need

Re: [VOTE] Release CXF 2.0.9

2008-10-10 Thread Jim Jagielski
+1 On Oct 10, 2008, at 8:48 AM, Willem Jiang wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is a vote to release CXF 2.0.9 Once again, there have been a bunch of bug fixes and enhancements that have been done compared to the 2.0.9 release. Over 37 JIRA issues are resolved for 2.0

Re: More on server response policies

2008-10-10 Thread Fred Dushin
Just to be clear, my +1 is a long-term strategy, and is not held with the conviction of a religious belief. A patch for CXF-1849 has been applied, and as long as I can get that back-merged to the 2.1.x-fixes branch, that gets me over the hump. -Fred On Oct 9, 2008, at 5:41 PM, Fred Dushin

Re: [VOTE] Release CXF 2.0.9

2008-10-10 Thread Eoghan Glynn
+1 Willem Jiang wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is a vote to release CXF 2.0.9 Once again, there have been a bunch of bug fixes and enhancements that have been done compared to the 2.0.9 release. Over 37 JIRA issues are resolved for 2.0.9 which is a large number

Re: [VOTE] Release CXF 2.0.9

2008-10-10 Thread Freeman Fang
+1 Freeman Willem Jiang wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is a vote to release CXF 2.0.9 Once again, there have been a bunch of bug fixes and enhancements that have been done compared to the 2.0.9 release. Over 37 JIRA issues are resolved for 2.0.9 which is a large