[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
branch.

List of issues:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310511&fixfor=12313314

The staging area is at:
http://people.apache.org/~ningjiang/stage_cxf/2.0.9

The distributions are in the "dist" directory. The "maven" directory
contains the stuff that will by pushed to the central repository.

This release is tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.9


Here is my +1.   The vote will be open here for at least 72 hours.

Willem
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iEYEARECAAYFAkjvTt8ACgkQI1CSmK6N6eTuWACdFBA+C8R3DzKTWCIinln0sCaC
zWAAn04fkhek/PMlgRHwCeevV45CTwN6
=4dc9
-END PGP SIGNATURE-

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 JIRA issues
> are resolved for 2.0.9 which is a large number of fixes for the 2.0.x
> branch.
>
> List of issues:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310511&fixfor=12313314
>
> The staging area is at:
> http://people.apache.org/~ningjiang/stage_cxf/2.0.9
>
> The distributions are in the "dist" directory. The "maven" directory
> contains the stuff that will by pushed to the central repository.
>
> This release is tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.9
>
>
> Here is my +1.   The vote will be open here for at least 72 hours.
>
> Willem
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.8 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkjvTt8ACgkQI1CSmK6N6eTuWACdFBA+C8R3DzKTWCIinln0sCaC
> zWAAn04fkhek/PMlgRHwCeevV45CTwN6
> =4dc9
> -END PGP SIGNATURE-
>
>

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 number of fixes for the 2.0.x
branch.

List of issues:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310511&fixfor=12313314

The staging area is at:
http://people.apache.org/~ningjiang/stage_cxf/2.0.9

The distributions are in the "dist" directory. The "maven" directory
contains the stuff that will by pushed to the central repository.

This release is tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.9


Here is my +1.   The vote will be open here for at least 72 hours.

Willem
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iEYEARECAAYFAkjvTt8ACgkQI1CSmK6N6eTuWACdFBA+C8R3DzKTWCIinln0sCaC

zWAAn04fkhek/PMlgRHwCeevV45CTwN6
=4dc9
-END PGP SIGNATURE-
  



IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

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 to UncheckedException and corresponding
> "super" calls to all exceptions.
>
>   public UncheckedException(String code, ResourceBundle bundle,
> Object...params) {
>   this(new Message(code, bundle, params));
>   }
> public UncheckedException(String code, Throwable t, ResourceBundle
> bundle, Object...params) {
>   this(new Message(code, bundle, params), t);
>   }
>
> To use these you could do the following at the start of the class:
>   static final Logger LOG = LogUtils.getL7dLogger(JMSConfigFeature.class);
>   static final ResourceBundle BUNDLE = LOG.getResourceBundle();
>
> and then:
> throw new ConfigurationException("JMSCONFIGFEATURE_ONLY_JMS", BUNDLE);
>
> I have checked where the i18n Message is used and it seems only to be used
> for exceptions. So would it perhaps make sense to deprecate it and always
> create exceptions like above?
> Was there a special reason for the introduction of i18n Message?
> Any opinions?
>
> Greetings
>
> Christian
>
>
> Benson Margulies schrieb:
>>
>> I'm +1 to the constructor. I find the new-ing of messages to be a pain.
>>
>> On Tue, Oct 7, 2008 at 5:27 PM, Christian Schneider
>> <[EMAIL PROTECTED]
>>
>>>
>>> wrote:
>>>
>>
>>
>
>
> --
>
> Christian Schneider
> ---
> http://www.liquid-reality.de
>
>

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 large number of fixes for the 2.0.x
> branch.
>
> List of issues:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=h
>ide&sorter/order=DESC&sorter/field=priority&pid=12310511&fixfor=12313314
>
> The staging area is at:
> http://people.apache.org/~ningjiang/stage_cxf/2.0.9
>
> The distributions are in the "dist" directory. The "maven" directory
> contains the stuff that will by pushed to the central repository.
>
> This release is tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.9
>
>
> Here is my +1.   The vote will be open here for at least 72 hours.
>
> Willem



-- 
Daniel Kulp
[EMAIL PROTECTED]
http://dankulp.com/blog

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 JIRA issues
> are resolved for 2.0.9 which is a large number of fixes for the 2.0.x
> branch.
>
> List of issues:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310511&fixfor=12313314
>
> The staging area is at:
> http://people.apache.org/~ningjiang/stage_cxf/2.0.9
>
> The distributions are in the "dist" directory. The "maven" directory
> contains the stuff that will by pushed to the central repository.
>
> This release is tagged at:
> http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.9
>
>
> Here is my +1.   The vote will be open here for at least 72 hours.
>
> Willem
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.8 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkjvTt8ACgkQI1CSmK6N6eTuWACdFBA+C8R3DzKTWCIinln0sCaC
> zWAAn04fkhek/PMlgRHwCeevV45CTwN6
> =4dc9
> -END PGP SIGNATURE-
>
>

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

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
branch.

List of issues:

https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310511&fixfor=12313314

The staging area is at:
http://people.apache.org/~ningjiang/stage_cxf/2.0.9


The distributions are in the "dist" directory. The "maven" directory
contains the stuff that will by pushed to the central repository.

This release is tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.9


Here is my +1.   The vote will be open here for at least 72 hours.

Willem
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjvTt8ACgkQI1CSmK6N6eTuWACdFBA+C8R3DzKTWCIinln0sCaC
zWAAn04fkhek/PMlgRHwCeevV45CTwN6
=4dc9
-END PGP SIGNATURE-

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 Paiva
Java & Flex Developer - RHCE
Rio de Janeiro - Brazil
werneck [dot] paiva [at] gmail [dot] com



IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

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 stuff, it cannot.I'm 
wondering if it make sense for the line in JMSOldConfigHolder that reads:
 jmsConfig.setUseJms11(true);
should be changed to false to be compatible with the old version?

I suppose we could add a optional "useJms11" attribute (default to false) on 
one of the old extensors (address maybe?) to set this so if someone wants to 
use 1.1, they could, but default behavior is maintained.

Thoughts?

-- 
Daniel Kulp
[EMAIL PROTECTED]
http://dankulp.com/blog

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
GreeterImpl());
and GreeterImpl has "String greetMe(String me)" which just returns a string.
Server is running on a Solaris 10 machine with java version "1.5.0_14"
Server does nothing else. 

The libs in classpath are
-classpath
lib:/lib/cxf/asm-2.2.3.jar:lib/cxf/commons-logging-1.1.jar:lib/cxf/cxf-2.0.3-incubator.jar:lib/cxf/geronimo-activation_1.1_spec-1.
0-M1.jar:lib/cxf/geronimo-annotation_1.0_spec-1.1.jar:lib/cxf/geronimo-javamail_1.4_spec-1.0-M1.jar:lib/cxf/geronimo-jms_1.1_spec-
1.1.jar:lib/cxf/geronimo-servlet_2.5_spec-1.1-M1.jar:lib/cxf/geronimo-ws-metadata_2.0_spec-1.1.1.jar:lib/cxf/jaxb-api-2.0.jar:lib/
cxf/jaxb-impl-2.0.5.jar:lib/cxf/jaxb-xjc-2.0.jar:lib/cxf/jaxen-1.1.jar:lib/cxf/jaxws-api-2.0.jar:lib/cxf/jetty-6.1.12.rc2.jar:lib/
cxf/jetty-util-6.1.12.rc2.jar:lib/cxf/jra-1.0-alpha-4.jar:lib/cxf/js-1.6R5.jar:lib/cxf/neethi-2.0.2.jar:lib/cxf/saaj-api-1.3.jar:l
ib/cxf/saaj-impl-1.3.jar:lib/cxf/slf4j-api-1.3.1.jar:lib/cxf/slf4j-jdk14-1.3.1.jar:lib/cxf/spring-beans-2.0.6.jar:lib/cxf/spring-c
ontext-2.0.6.jar:lib/cxf/spring-core-2.0.6.jar:lib/cxf/stax-api-1.0.1.jar:lib/cxf/stax-utils-20060502.jar:lib/cxf/wsdl4j-1.6.1.jar
:lib/cxf/wss4j-1.5.1.jar:lib/cxf/wstx-asl-3.2.1.jar:lib/cxf/xalan-2.7.0.jar:lib/cxf/xbean-2.2.0.jar:lib/cxf/xml-apis-1.3.02.jar:li
b/cxf/xml-resolver-1.2.jar:lib/cxf/XmlSchema-1.3.2.jar:lib/activemq-core-5.0.0.jar:lib/geronimo-j2ee-management_1.0_spec-1.0.jar

Server is run with JVM parameters "-Xmx129m -XX:MaxPermSize=128m ". No other
tuning parameters added in server[However, a lot of other tuning were tried
(like,  -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled
-XX:+CMSPermGenSweepingEnabled) and found that the result is not favorable]

Client:
Client written in CXF, sends requests continuously to the server.(infinite
loop)

Behavior:
The memory of the server continously increases from ~90M to ~350M which
never comes down.
But through jconsole we know that the Heap, or non-heap memory hasn't
increased much.
Below table contains mem usage details over a period of 1Hr (800,000
Request/Response)

  prstatHeapNon-Heap
   CMS PermGen  
Total   RSS Used  Comitd Max  Used  Comitd   Max  
Used  Comitd   Max
176 103 3   36  120 16  30  163 
14  28  131
184 124 2   35  120 20  24  163 
16  20  131
184 129 2   13  120 22  25  163 
16  20  131
200 145 2   19  120 22  25  163 
16  20  131
204 149 2   45  120 22  25  163 
16  20  131
253 207 5   18  120 19  20  163 
14  16  131

Same test was carried out with CXF Version 2.1.2 and it behaves the same
way.



OS : Solaris 10
 [EMAIL PROTECTED] # psrinfo -v
Status of virtual processor 0 as of: 03/31/2000 22:38:54
  on-line since 03/25/2000 04:24:44.
  The sparcv9 processor operates at 1593 MHz,
and has a sparcv9 floating point processor.
Status of virtual processor 1 as of: 03/31/2000 22:38:54
  on-line since 03/25/2000 04:24:44.
  The sparcv9 processor operates at 1593 MHz,
and has a sparcv9 floating point processor.
Status of virtual processor 2 as of: 03/31/2000 22:38:54
  on-line since 03/25/2000 04:24:44.
  The sparcv9 processor operates at 1593 MHz,
and has a sparcv9 floating point processor.
Status of virtual processor 3 as of: 03/31/2000 22:38:54
  on-line since 03/25/2000 04:24:43.
  The sparcv9 processor operates at 1593 MHz,
and has a sparcv9 floating point processor.

[EMAIL PROTECTED] # prtconf | grep Memory
Memory size: 8192 Megabytes


Please help us identify the reason for this mem increase. 

regards
anoopPrasad



bharath-5 wrote:
> 
> Hi Hubert,
> 
> Is the leak replicable? Is is that the memory was just high or it was a
> leak? Did you see an OOM?
> Will be of great help if you can send the test case.
> Also let me know which CXF version you are using?
> 
> Thanks,
> Bharath
> IBM - India Software Labs
> 
> http://thoughts.bharathganesh.com
> 
> On Tue, Sep 23, 2008 at 5:36 AM, Sky-Tiger
> <[EMAIL PROTECTED]>wrote:
> 
>>
>> Dear Dan,
>>   I wrote a very simple application using CXF, just like Helloworld.
>>   Firstly, I run the application using JMS as tranport layer,
>> erverything is ok.
>>   But when i change the JMS with HTTP, I find the memory will
>> increase
>> slowly. And such increasing can not be ch

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 Aegis provider such that peopple could start doing Aegis and REST or indeed combining 
SOAP and REST with the help of Aegis, then it would be cool IMHO


Cheers, Sergey




I think I'm beginning to get the idea of what I'm trying to complain about.

An AegisDatabinding object has input configuration and it has state.
As it goes along, it constructs mappings for types.

I'm having trouble swallowing a situation in which each individual
JAX-RS item does this independently, as opposed to all the of the
items in a service sharing a single state. Am I just confused? 



IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

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 their hair on fire, but that might change.

--benson

On Fri, Oct 10, 2008 at 11:44 AM, Sergey Beryozkin
<[EMAIL PROTECTED]> wrote:
> 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 Aegis provider such that peopple
> could start doing Aegis and REST or indeed combining SOAP and REST with the
> help of Aegis, then it would be cool IMHO
>
> Cheers, Sergey
>
>
>
>> I think I'm beginning to get the idea of what I'm trying to complain
>> about.
>>
>> An AegisDatabinding object has input configuration and it has state.
>> As it goes along, it constructs mappings for types.
>>
>> I'm having trouble swallowing a situation in which each individual
>> JAX-RS item does this independently, as opposed to all the of the
>> items in a service sharing a single state. Am I just confused?
>
> 
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
>

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 to get into the 
details of the actual
JAX-RS runtime impl, hopefully you'd be able to craft a basic Aegis support 
inside the 'shell' of the (Aegis)
JAX-RS MessageBodyReader/Writer implementation...If we could say limit the support to pure Aegis (that is without it also supporting 
JAXB - which is something CXF Aegis can do as far as I understand) then it would be super...


Cheers, Sergey



--benson

On Fri, Oct 10, 2008 at 11:44 AM, Sergey Beryozkin
<[EMAIL PROTECTED]> wrote:

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 Aegis provider such that peopple
could start doing Aegis and REST or indeed combining SOAP and REST with the
help of Aegis, then it would be cool IMHO

Cheers, Sergey




I think I'm beginning to get the idea of what I'm trying to complain
about.

An AegisDatabinding object has input configuration and it has state.
As it goes along, it constructs mappings for types.

I'm having trouble swallowing a situation in which each individual
JAX-RS item does this independently, as opposed to all the of the
items in a service sharing a single state. Am I just confused?



IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland




IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

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.9 which is a large number of fixes for the 2.0.x
branch.

List of issues:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310511&fixfor=12313314

The staging area is at:
http://people.apache.org/~ningjiang/stage_cxf/2.0.9

The distributions are in the "dist" directory. The "maven" directory
contains the stuff that will by pushed to the central repository.

This release is tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.9


Here is my +1.   The vote will be open here for at least 72 hours.

Willem
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjvTt8ACgkQI1CSmK6N6eTuWACdFBA+C8R3DzKTWCIinln0sCaC
zWAAn04fkhek/PMlgRHwCeevV45CTwN6
=4dc9
-END PGP SIGNATURE-

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 wrote:

Correct.  Dan, you: +1 on logging (FINE or lower log level).  Me: +1  
on removing the validation out interceptor (outbound server side  
only), since it's doing nothing put churning cycles and possibly  
confusing the user.

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 of fixes for the 2.0.x
branch.

List of issues:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310511&fixfor=12313314

The staging area is at:
http://people.apache.org/~ningjiang/stage_cxf/2.0.9

The distributions are in the "dist" directory. The "maven" directory
contains the stuff that will by pushed to the central repository.

This release is tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.9


Here is my +1.   The vote will be open here for at least 72 hours.

Willem
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iEYEARECAAYFAkjvTt8ACgkQI1CSmK6N6eTuWACdFBA+C8R3DzKTWCIinln0sCaC

zWAAn04fkhek/PMlgRHwCeevV45CTwN6
=4dc9
-END PGP SIGNATURE-



IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

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 number of fixes for the 2.0.x
branch.

List of issues:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310511&fixfor=12313314

The staging area is at:
http://people.apache.org/~ningjiang/stage_cxf/2.0.9

The distributions are in the "dist" directory. The "maven" directory
contains the stuff that will by pushed to the central repository.

This release is tagged at:
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.0.9


Here is my +1.   The vote will be open here for at least 72 hours.

Willem
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iEYEARECAAYFAkjvTt8ACgkQI1CSmK6N6eTuWACdFBA+C8R3DzKTWCIinln0sCaC

zWAAn04fkhek/PMlgRHwCeevV45CTwN6
=4dc9
-END PGP SIGNATURE-