Re: Typo

2018-04-08 Thread Dennis Kieselhorst
Hi Gav,

you're right, thanks for the info. I've just corrected it.

Cheers
Dennis

Am 09.04.2018 um 06:22 schrieb Gavin McDonald:
> Hi cxf-ers
>
> I spy a typo on your from page. 
>
> The warning says do not use 3.2.2 or 3.2.3 , but use 3.2.3 !
>
> You mean 3.2.4 of course.
>
> HTH
>
> Gav…
>



Typo

2018-04-08 Thread Gavin McDonald
Hi cxf-ers

I spy a typo on your from page. 

The warning says do not use 3.2.2 or 3.2.3 , but use 3.2.3 !

You mean 3.2.4 of course.

HTH

Gav…



[GitHub] cxf pull request #223: Fix obvious typo in DEBUG logs.

2017-01-17 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/cxf/pull/223


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] cxf pull request #223: Fix obvious typo in DEBUG logs.

2017-01-16 Thread ajeans
GitHub user ajeans opened a pull request:

https://github.com/apache/cxf/pull/223

Fix obvious typo in DEBUG logs.

Noticed this on 3.1.8 while debugging something on 3.1.X, and master still 
has the typo. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ajeans/cxf master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cxf/pull/223.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #223


commit f377a844218e31dea5ad253f07b0332bce3b4d5e
Author: Jeansen 
Date:   2017-01-16T13:45:54Z

Fix obvious typo in DEBUG logs.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] cxf pull request: Fix a typo in FIXED_PARAMETER_ORDER

2016-03-19 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/cxf/pull/122


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] cxf pull request: Fix a typo in FIXED_PARAMETER_ORDER

2016-03-15 Thread trohovsky
GitHub user trohovsky opened a pull request:

https://github.com/apache/cxf/pull/122

Fix a typo in FIXED_PARAMETER_ORDER



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/trohovsky/cxf fixed-parameter-order-typo

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cxf/pull/122.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #122


commit bc15935f1e5920b1016bcdcf827012cb001e9347
Author: Tomas Rohovsky 
Date:   2016-03-15T12:32:54Z

Fix a typo in FIXED_PARAMETER_ORDER




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: Typo error for null checking in EndpointImpl ?

2013-03-15 Thread Daniel Kulp

Yea, a bug.   The check really shouldn't even be there.   It should just be 
other.remove(o) no matter if its null or not.   Fixed.


Dan



On Mar 15, 2013, at 2:22 AM, Ivan  wrote:

> Hi, I found the codes below in the org.apache.cxf.jaxws.EndpointImpl (line
> 691)
> 
> public Interceptor remove(int index) {
>Interceptor o = orig.remove(index);
>if (o == null) {   <--- Is it a typo error ? Should be != null
>other.remove(o);
>}
>return o;
>}
> 
> -- 
> Ivan

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com



Re: Typo in wiki

2011-07-15 Thread Freeman Fang

Hi,

Thanks for letting us know this issue.
Just correct the wiki, should be sync up in a few hours.

Freeman
On 2011-7-15, at 下午3:27, akuhtz wrote:


Hi,

There is a typo in the code snippet on the
http://cxf.apache.org/docs/transformationfeature.html Transformation  
feature

site.

The classname StaxTransf*ro*mFeature must be StaxTransf*or*mFeature.

Cheers Andi



--
View this message in context: 
http://cxf.547215.n5.nabble.com/Typo-in-wiki-tp4589705p4589705.html
Sent from the cxf-dev mailing list archive at Nabble.com.


-
Freeman Fang

FuseSource
Email:ff...@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com











Typo in wiki

2011-07-15 Thread akuhtz
Hi,

There is a typo in the code snippet on the 
http://cxf.apache.org/docs/transformationfeature.html Transformation feature 
site.

The classname StaxTransf*ro*mFeature must be StaxTransf*or*mFeature.

Cheers Andi



--
View this message in context: 
http://cxf.547215.n5.nabble.com/Typo-in-wiki-tp4589705p4589705.html
Sent from the cxf-dev mailing list archive at Nabble.com.


RE: Typo in LoggingInInterceptor constructor?

2011-02-11 Thread Pieper, Aaron
Ha ha no problem, Glen :) thanks for incorporating my change.

- Aaron

-Original Message-
From: Glen Mazza [mailto:gma...@talend.com] 
Sent: Thursday, February 10, 2011 10:48 AM
To: dev@cxf.apache.org
Subject: Re: Typo in LoggingInInterceptor constructor?

Fixed on 2.3.2 and upcoming 2.4.  Also, I checked the official CXF 
treasury ($0.00), sorry no money for the Monster drink.

Thanks,
Glen

On 09.02.2011 14:40, Glen Mazza wrote:
> Hmm, seems like the CXF team owes Aaron a Monster energy drink (unless
> he's become partial to other beverages).
>
> Glen
>
> On 09.02.2011 14:00, Pieper, Aaron wrote:
>> Is there a typo in the LoggingInInterceptor(String,String)
constructor?
>> It seems to inaccurately call super(id, id) instead of super(id,
phase).
>> I'm looking at r1058274 which appears to be the latest:
>>
>>
>>
>>
http://svn.apache.org/viewvc/cxf/trunk/rt/core/src/main/java/org/apache/
>>
cxf/interceptor/LoggingInInterceptor.java?revision=1058274&view=markup
>>
>>
>>
>> It seems accidental, given the invocations on lines 55 and 64 which
>> wouldn't make much sense if it were deliberate.
>>
>> - Aaron
>>
>


-- 
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza




Re: Typo in LoggingInInterceptor constructor?

2011-02-11 Thread Glen Mazza

Thanks!

On 2/11/2011 4:26 AM, Willem Jiang wrote:

Hi Glen,

Your fix has some side effect, I just committed another patch[1] to fix
the test error of SecurityPolicyTest.

[1]http://svn.apache.org/viewvc?rev=1069716&view=rev

Willem

On 2/10/11 11:47 PM, Glen Mazza wrote:

Fixed on 2.3.2 and upcoming 2.4. Also, I checked the official CXF
treasury ($0.00), sorry no money for the Monster drink.

Thanks,
Glen

On 09.02.2011 14:40, Glen Mazza wrote:

Hmm, seems like the CXF team owes Aaron a Monster energy drink (unless
he's become partial to other beverages).

Glen

On 09.02.2011 14:00, Pieper, Aaron wrote:

Is there a typo in the LoggingInInterceptor(String,String) constructor?
It seems to inaccurately call super(id, id) instead of super(id, phase).
I'm looking at r1058274 which appears to be the latest:



http://svn.apache.org/viewvc/cxf/trunk/rt/core/src/main/java/org/apache/
cxf/interceptor/LoggingInInterceptor.java?revision=1058274&view=markup



It seems accidental, given the invocations on lines 55 and 64 which
wouldn't make much sense if it were deliberate.

- Aaron










Re: Typo in LoggingInInterceptor constructor?

2011-02-11 Thread Willem Jiang

Hi Glen,

Your fix has some side effect, I just committed another patch[1] to fix 
the test error of SecurityPolicyTest.


[1]http://svn.apache.org/viewvc?rev=1069716&view=rev

Willem

On 2/10/11 11:47 PM, Glen Mazza wrote:

Fixed on 2.3.2 and upcoming 2.4. Also, I checked the official CXF
treasury ($0.00), sorry no money for the Monster drink.

Thanks,
Glen

On 09.02.2011 14:40, Glen Mazza wrote:

Hmm, seems like the CXF team owes Aaron a Monster energy drink (unless
he's become partial to other beverages).

Glen

On 09.02.2011 14:00, Pieper, Aaron wrote:

Is there a typo in the LoggingInInterceptor(String,String) constructor?
It seems to inaccurately call super(id, id) instead of super(id, phase).
I'm looking at r1058274 which appears to be the latest:



http://svn.apache.org/viewvc/cxf/trunk/rt/core/src/main/java/org/apache/
cxf/interceptor/LoggingInInterceptor.java?revision=1058274&view=markup



It seems accidental, given the invocations on lines 55 and 64 which
wouldn't make much sense if it were deliberate.

- Aaron









--
Willem
--
FuseSource
Web: http://www.fusesource.com
Blog:http://willemjiang.blogspot.com (English)
 http://jnn.javaeye.com (Chinese)
Twitter: willemjiang


Re: Typo in LoggingInInterceptor constructor?

2011-02-10 Thread Glen Mazza
Fixed on 2.3.2 and upcoming 2.4.  Also, I checked the official CXF 
treasury ($0.00), sorry no money for the Monster drink.


Thanks,
Glen

On 09.02.2011 14:40, Glen Mazza wrote:

Hmm, seems like the CXF team owes Aaron a Monster energy drink (unless
he's become partial to other beverages).

Glen

On 09.02.2011 14:00, Pieper, Aaron wrote:

Is there a typo in the LoggingInInterceptor(String,String) constructor?
It seems to inaccurately call super(id, id) instead of super(id, phase).
I'm looking at r1058274 which appears to be the latest:



http://svn.apache.org/viewvc/cxf/trunk/rt/core/src/main/java/org/apache/
cxf/interceptor/LoggingInInterceptor.java?revision=1058274&view=markup



It seems accidental, given the invocations on lines 55 and 64 which
wouldn't make much sense if it were deliberate.

- Aaron






--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza




Re: Typo in LoggingInInterceptor constructor?

2011-02-09 Thread James Carr
Monster Energy drink? That's not a reward, that's a punishment. :)

On Wed, Feb 9, 2011 at 1:40 PM, Glen Mazza  wrote:
> Hmm, seems like the CXF team owes Aaron a Monster energy drink (unless he's
> become partial to other beverages).
>
> Glen
>
> On 09.02.2011 14:00, Pieper, Aaron wrote:
>>
>> Is there a typo in the LoggingInInterceptor(String,String) constructor?
>> It seems to inaccurately call super(id, id) instead of super(id, phase).
>> I'm looking at r1058274 which appears to be the latest:
>>
>>
>>
>> http://svn.apache.org/viewvc/cxf/trunk/rt/core/src/main/java/org/apache/
>> cxf/interceptor/LoggingInInterceptor.java?revision=1058274&view=markup
>>
>>
>>
>> It seems accidental, given the invocations on lines 55 and 64 which
>> wouldn't make much sense if it were deliberate.
>>
>> - Aaron
>>
>
>
> --
> Glen Mazza
> Software Engineer, Talend (http://www.talend.com)
> blog: http://www.jroller.com/gmazza
>
>
>


Re: Typo in LoggingInInterceptor constructor?

2011-02-09 Thread Glen Mazza
Hmm, seems like the CXF team owes Aaron a Monster energy drink (unless 
he's become partial to other beverages).


Glen

On 09.02.2011 14:00, Pieper, Aaron wrote:

Is there a typo in the LoggingInInterceptor(String,String) constructor?
It seems to inaccurately call super(id, id) instead of super(id, phase).
I'm looking at r1058274 which appears to be the latest:



http://svn.apache.org/viewvc/cxf/trunk/rt/core/src/main/java/org/apache/
cxf/interceptor/LoggingInInterceptor.java?revision=1058274&view=markup



It seems accidental, given the invocations on lines 55 and 64 which
wouldn't make much sense if it were deliberate.

- Aaron




--
Glen Mazza
Software Engineer, Talend (http://www.talend.com)
blog: http://www.jroller.com/gmazza




Typo in LoggingInInterceptor constructor?

2011-02-09 Thread Pieper, Aaron
Is there a typo in the LoggingInInterceptor(String,String) constructor?
It seems to inaccurately call super(id, id) instead of super(id, phase).
I'm looking at r1058274 which appears to be the latest:

 

http://svn.apache.org/viewvc/cxf/trunk/rt/core/src/main/java/org/apache/
cxf/interceptor/LoggingInInterceptor.java?revision=1058274&view=markup

 

It seems accidental, given the invocations on lines 55 and 64 which
wouldn't make much sense if it were deliberate.

- Aaron