[jira] [Commented] (CAMEL-10433) The camel-jetty, camel-jetty9 feature should explicitly define the expected feature version range for jetty

2016-11-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627506#comment-15627506
 ] 

ASF GitHub Bot commented on CAMEL-10433:


GitHub user xldai opened a pull request:

https://github.com/apache/camel/pull/1244

fix CAMEL-10433 in Camel 2.16.x



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

$ git pull https://github.com/xldai/camel patch-4

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

https://github.com/apache/camel/pull/1244.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 #1244


commit 3e096a5dde6a2a6c352b8ae7c9787addf739c3ac
Author: Xilai Dai 
Date:   2016-11-02T03:17:17Z

fix CAMEL-10433 in Camel 2.16.x




> The camel-jetty, camel-jetty9 feature should explicitly define the expected 
> feature version range for jetty
> ---
>
> Key: CAMEL-10433
> URL: https://issues.apache.org/jira/browse/CAMEL-10433
> Project: Camel
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 2.16.3, 2.17.3
> Environment: Java 8
>Reporter: Xilai Dai
>Priority: Minor
>
> There is no version range restriction of jetty feature in the camel-jetty and 
> camel-jetty9 feature definition.
> {code}
> jetty
> {code}
> For camel-jetty9 feature, it maybe should add version range like this:
> {code}
> jetty
> {code}
> For camel-jetty feature, it maybe should add version range like this:
> {code}
> jetty
> {code}
> Because from karaf 4.x there are both jetty 8 and jetty 9 feature existing. 
> Making this changes will avoid install the wrong version jetty bundles when 
> install camel-jetty (or camel-jetty8 of Camel 2.17.x)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10423) Introduce XmppDirectProducer

2016-11-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627450#comment-15627450
 ] 

ASF GitHub Bot commented on CAMEL-10423:


GitHub user allancth opened a pull request:

https://github.com/apache/camel/pull/1243

CAMEL-10423 - Introduce XmppDirectProducer

The order of which producer is used depends on what parameters are 
specified to the endpoint, with the following precendence: room (GroupChat), 
pubsub (PubSub), doc (Direct). When these parameters are not specified, by 
default, a PrivateChat producer will be used.

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

$ git pull https://github.com/allancth/camel CAMEL-10423

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

https://github.com/apache/camel/pull/1243.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 #1243


commit b65c9feffe569c392b0b25866e7e35fb4a715f11
Author: Allan C 
Date:   2016-11-02T02:31:21Z

CAMEL-10423 - Introduce XmppDirectProducer




> Introduce XmppDirectProducer
> 
>
> Key: CAMEL-10423
> URL: https://issues.apache.org/jira/browse/CAMEL-10423
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-xmpp
>Affects Versions: 2.18.0
> Environment: Linux, Karaf 4.0.6
>Reporter: Allan Cheong Tyng Huei
>Assignee: Andrea Cosentino
>Priority: Minor
>  Labels: beginner, newbie
> Fix For: 2.19.0
>
>
> Current XMPP component is unable to send messages to Firebase/Google cloud 
> connection server (CCS). Similar to the PubSubProducer, a "direct producer" 
> that sends a Packet instead of a PubSub would be needed to communicate with 
> the CCS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10433) The camel-jetty, camel-jetty9 feature should explicitly define the expected feature version range for jetty

2016-11-01 Thread Xilai Dai (JIRA) 
Xilai Dai created CAMEL-10433:
-

 Summary: The camel-jetty, camel-jetty9 feature should explicitly 
define the expected feature version range for jetty
 Key: CAMEL-10433
 URL: https://issues.apache.org/jira/browse/CAMEL-10433
 Project: Camel
  Issue Type: Bug
  Components: karaf
Affects Versions: 2.17.3, 2.16.3
 Environment: Java 8
Reporter: Xilai Dai
Priority: Minor


There is no version range restriction of jetty feature in the camel-jetty and 
camel-jetty9 feature definition.
{code}
jetty
{code}

For camel-jetty9 feature, it maybe should add version range like this:
{code}
jetty
{code}

For camel-jetty feature, it maybe should add version range like this:
{code}
jetty
{code}

Because from karaf 4.x there are both jetty 8 and jetty 9 feature existing. 
Making this changes will avoid install the wrong version jetty bundles when 
install camel-jetty (or camel-jetty8 of Camel 2.17.x)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10344) RouteIdFactory - That can assign route ids using derived values from uris

2016-11-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626352#comment-15626352
 ] 

ASF GitHub Bot commented on CAMEL-10344:


GitHub user tkopczynski opened a pull request:

https://github.com/apache/camel/pull/1242

CAMEL-10344: RouteIdFactory - assigning route ids based on uris

This PR adds RouteIdFactory which can be used as a NodeIdFactory 
implementation in CamelContext as a different strategy for assigning route ids.

Currently, it works with direct and similar routes.

Unfortunately, I'm not sure on how to integrate this with assigning ids in 
rest routes. It feels like this should be somewhere in 
`RestDefinition.addRouteDefinition` but route id is assigned so early that 
RouteDefinition doesn't have enough information for creating the id from the 
path.

@davsclaus do you have any ideas/suggestions on this?

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

$ git pull https://github.com/tkopczynski/camel camel-10344

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

https://github.com/apache/camel/pull/1242.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 #1242


commit f0bc524b7546b398a4a4f804c63a7e0807d1b58a
Author: Tomasz Kopczynski 
Date:   2016-11-01T18:49:06Z

CAMEL-10344: RouteIdFactory - assigning route ids based on uris




> RouteIdFactory - That can assign route ids using derived values from uris
> -
>
> Key: CAMEL-10344
> URL: https://issues.apache.org/jira/browse/CAMEL-10344
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
>
> When using routes that uses direct/seda etc as route inputs, then you may 
> want to use their name as the route id, eg
> direct:foo   -> foo
> seda:bar-> bar
> jms:orders -> orders
> Instead of having route1, route2 as auto assigned names. 
> There could be a NodeIdFactory that assign such names for route's. For 
> example it can use the context-path of the route url as the name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10350) New camel-bonita component

2016-11-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626287#comment-15626287
 ] 

ASF GitHub Bot commented on CAMEL-10350:


Github user lio-p closed the pull request at:

https://github.com/apache/camel/pull/1236


> New camel-bonita component
> --
>
> Key: CAMEL-10350
> URL: https://issues.apache.org/jira/browse/CAMEL-10350
> Project: Camel
>  Issue Type: New Feature
>Reporter: Lionel Palacin
>Priority: Minor
> Fix For: 2.19.0
>
>
> Hello,
> I implemented a component to interface Bonita BPM engine. For now I have a 
> producer to start a new process. 
> I need to polish the code and write some tests. Once done, could I share it 
> here?
> Thanks 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10431) camel-elsql - Does not read named parameter from header properties

2016-11-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625974#comment-15625974
 ] 

ASF GitHub Bot commented on CAMEL-10431:


Github user osmman closed the pull request at:

https://github.com/apache/camel/pull/1241


> camel-elsql - Does not read named parameter from header properties
> --
>
> Key: CAMEL-10431
> URL: https://issues.apache.org/jira/browse/CAMEL-10431
> Project: Camel
>  Issue Type: Bug
>  Components: camel-elsql
>Affects Versions: 2.18.0
>Reporter: Tomas Turek
>Assignee: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
>
> Camel-elsql could not lookup for parameters from message headers. Problem is 
> here 
> https://github.com/apache/camel/blob/camel-2.18.0/components/camel-elsql/src/main/java/org/apache/camel/component/elsql/ElsqlSqlMapSource.java#L70
> Sample route:
> {code}
> from("direct:projects")
>   .setHeader("lic", constant("ASF"))
>   .setHeader("min", constant(123))
>   .to("elsql:projects:com/foo/projects.elsql")
> {code}
> ElSql:
> {code}
> @NAME(projects)
>   SELECT *
>   FROM projects
>   WHERE license = :lic AND id > :min
>   ORDER BY id
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10432) concurrentlinkedhashmap used by LRU cache consumes 100MB memory on 1024 core Solaris T5

2016-11-01 Thread Ben Manes (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625877#comment-15625877
 ] 

Ben Manes commented on CAMEL-10432:
---

Fixed in [CAMEL-8994|https://issues.apache.org/jira/browse/CAMEL-8994] and 
later switched to Caffeine. So I think this is fixed.

> concurrentlinkedhashmap used by LRU cache consumes 100MB memory on 1024 core 
> Solaris T5
> ---
>
> Key: CAMEL-10432
> URL: https://issues.apache.org/jira/browse/CAMEL-10432
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.17.1
> Environment: Solaris T5 1024 core machine
> java 1.7.045
>Reporter: Matt Baker
>
> Cloned from: AMQ-6492
> On a Solaris T5 with 1024 cores, the amount of memory used by LRUCache which 
> in turn is using ConcurrentLinkedHashMap from 
> https://github.com/ben-manes/concurrentlinkedhashmap
> consumes about 20MB of memory.  In my install this correlates to over 300MB 
> of memory.
> concurrentlinkedhashmap allocates memory based on CPU count, with no upper 
> limit, so each instance of LRUCache in memory consumes more memory than is 
> really needed.
> See AMQ-6492 for screenshots (didn't want to copy/paste them here)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10432) concurrentlinkedhashmap used by LRU cache consumes 100MB memory on 1024 core Solaris T5

2016-11-01 Thread Matt Baker (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625872#comment-15625872
 ] 

Matt Baker commented on CAMEL-10432:


I think this is similar to OFBIZ-6747

> concurrentlinkedhashmap used by LRU cache consumes 100MB memory on 1024 core 
> Solaris T5
> ---
>
> Key: CAMEL-10432
> URL: https://issues.apache.org/jira/browse/CAMEL-10432
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.17.1
> Environment: Solaris T5 1024 core machine
> java 1.7.045
>Reporter: Matt Baker
>
> Cloned from: AMQ-6492
> On a Solaris T5 with 1024 cores, the amount of memory used by LRUCache which 
> in turn is using ConcurrentLinkedHashMap from 
> https://github.com/ben-manes/concurrentlinkedhashmap
> consumes about 20MB of memory.  In my install this correlates to over 300MB 
> of memory.
> concurrentlinkedhashmap allocates memory based on CPU count, with no upper 
> limit, so each instance of LRUCache in memory consumes more memory than is 
> really needed.
> See AMQ-6492 for screenshots (didn't want to copy/paste them here)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10432) concurrentlinkedhashmap used by LRU cache consumes 100MB memory on 1024 core Solaris T5

2016-11-01 Thread Matt Baker (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625837#comment-15625837
 ] 

Matt Baker commented on CAMEL-10432:


this may have already been fixed but would require an update to the 
ConcurrentLinkedHashMap 1.4.2.

https://github.com/ben-manes/concurrentlinkedhashmap/issues/43

> concurrentlinkedhashmap used by LRU cache consumes 100MB memory on 1024 core 
> Solaris T5
> ---
>
> Key: CAMEL-10432
> URL: https://issues.apache.org/jira/browse/CAMEL-10432
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.17.1
> Environment: Solaris T5 1024 core machine
> java 1.7.045
>Reporter: Matt Baker
>
> Cloned from: AMQ-6492
> On a Solaris T5 with 1024 cores, the amount of memory used by LRUCache which 
> in turn is using ConcurrentLinkedHashMap from 
> https://github.com/ben-manes/concurrentlinkedhashmap
> consumes about 20MB of memory.  In my install this correlates to over 300MB 
> of memory.
> concurrentlinkedhashmap allocates memory based on CPU count, with no upper 
> limit, so each instance of LRUCache in memory consumes more memory than is 
> really needed.
> See AMQ-6492 for screenshots (didn't want to copy/paste them here)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-10431) camel-elsql - Does not read named parameter from header properties

2016-11-01 Thread Claus Ibsen (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-10431.
-
   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: 2.19.0
   2.18.1

Thanks for the PR

> camel-elsql - Does not read named parameter from header properties
> --
>
> Key: CAMEL-10431
> URL: https://issues.apache.org/jira/browse/CAMEL-10431
> Project: Camel
>  Issue Type: Bug
>  Components: camel-elsql
>Affects Versions: 2.18.0
>Reporter: Tomas Turek
>Assignee: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
>
> Camel-elsql could not lookup for parameters from message headers. Problem is 
> here 
> https://github.com/apache/camel/blob/camel-2.18.0/components/camel-elsql/src/main/java/org/apache/camel/component/elsql/ElsqlSqlMapSource.java#L70
> Sample route:
> {code}
> from("direct:projects")
>   .setHeader("lic", constant("ASF"))
>   .setHeader("min", constant(123))
>   .to("elsql:projects:com/foo/projects.elsql")
> {code}
> ElSql:
> {code}
> @NAME(projects)
>   SELECT *
>   FROM projects
>   WHERE license = :lic AND id > :min
>   ORDER BY id
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10432) concurrentlinkedhashmap used by LRU cache consumes 100MB memory on 1024 core Solaris T5

2016-11-01 Thread Matt Baker (JIRA) 
Matt Baker created CAMEL-10432:
--

 Summary: concurrentlinkedhashmap used by LRU cache consumes 100MB 
memory on 1024 core Solaris T5
 Key: CAMEL-10432
 URL: https://issues.apache.org/jira/browse/CAMEL-10432
 Project: Camel
  Issue Type: Bug
  Components: camel-core
Affects Versions: 2.17.1
 Environment: Solaris T5 1024 core machine
java 1.7.045
Reporter: Matt Baker


Cloned from: AMQ-6492

On a Solaris T5 with 1024 cores, the amount of memory used by LRUCache which in 
turn is using ConcurrentLinkedHashMap from 
https://github.com/ben-manes/concurrentlinkedhashmap

consumes about 20MB of memory.  In my install this correlates to over 300MB of 
memory.

concurrentlinkedhashmap allocates memory based on CPU count, with no upper 
limit, so each instance of LRUCache in memory consumes more memory than is 
really needed.

See AMQ-6492 for screenshots (didn't want to copy/paste them here)






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10431) camel-elsql - Does not read named parameter from header properties

2016-11-01 Thread Tomas Turek (JIRA) 
Tomas Turek created CAMEL-10431:
---

 Summary: camel-elsql - Does not read named parameter from header 
properties
 Key: CAMEL-10431
 URL: https://issues.apache.org/jira/browse/CAMEL-10431
 Project: Camel
  Issue Type: Bug
  Components: camel-elsql
Affects Versions: 2.18.0
Reporter: Tomas Turek


Camel-elsql could not lookup for parameters from message headers. Problem is 
here 
https://github.com/apache/camel/blob/camel-2.18.0/components/camel-elsql/src/main/java/org/apache/camel/component/elsql/ElsqlSqlMapSource.java#L70

Sample route:
{code}
from("direct:projects")
  .setHeader("lic", constant("ASF"))
  .setHeader("min", constant(123))
  .to("elsql:projects:com/foo/projects.elsql")
{code}

ElSql:
{code}
@NAME(projects)
  SELECT *
  FROM projects
  WHERE license = :lic AND id > :min
  ORDER BY id
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-10430) camel-hystrix - Should also execute fallback if exception not from Camel

2016-11-01 Thread Claus Ibsen (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-10430.
-
Resolution: Fixed

> camel-hystrix - Should also execute fallback if exception not from Camel
> 
>
> Key: CAMEL-10430
> URL: https://issues.apache.org/jira/browse/CAMEL-10430
> Project: Camel
>  Issue Type: Bug
>  Components: camel-hystrix
>Affects Versions: 2.18.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Hystrix-Fallback-not-executed-on-Thread-Pool-Semaphore-rejection-tp5789521.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10430) camel-hystrix - Should also execute fallback if exception not from Camel

2016-11-01 Thread Claus Ibsen (JIRA) 
Claus Ibsen created CAMEL-10430:
---

 Summary: camel-hystrix - Should also execute fallback if exception 
not from Camel
 Key: CAMEL-10430
 URL: https://issues.apache.org/jira/browse/CAMEL-10430
 Project: Camel
  Issue Type: Bug
  Components: camel-hystrix
Affects Versions: 2.18.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.18.1, 2.19.0


See nabble
http://camel.465427.n5.nabble.com/Hystrix-Fallback-not-executed-on-Thread-Pool-Semaphore-rejection-tp5789521.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10429) CXFRS client requires Exchange.HTTP_URI instead of HTTP_PATH for Camel tranport

2016-11-01 Thread Tadayoshi Sato (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tadayoshi Sato updated CAMEL-10429:
---
Attachment: camel-cxf-transport.zip

Reproducer {{camel-cxf-transport.zip}} attached. See {{README.md}} inside for 
how to run it.

> CXFRS client requires Exchange.HTTP_URI instead of HTTP_PATH for Camel 
> tranport
> ---
>
> Key: CAMEL-10429
> URL: https://issues.apache.org/jira/browse/CAMEL-10429
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxfrs
>Affects Versions: 2.18.0
>Reporter: Tadayoshi Sato
> Attachments: camel-cxf-transport.zip
>
>
> The [camel-cxfrs doc|http://camel.apache.org/cxfrs.html] writes that 
> {{HTTP_PATH}} is required for {{camel-cxfrs}} producer when it's used with 
> {{httpClientAPI}} option.
> {quote}
> The CXF JAXRS front end also provides a http centric client API. You can also 
> invoke this API from camel-cxfrs producer. *You need to specify the HTTP_PATH 
> and the HTTP_METHOD* and let the producer use the http centric client API by 
> using the URI option httpClientAPI or by setting the message header 
> CxfConstants.CAMEL_CXF_RS_USING_HTTP_API.
> {quote}
> However, when Camel transport is used between CXFRS producer and consumer, 
> the invocation succeeds only if it sets {{HTTP_URI}}, not {{HTTP_PATH}}, to 
> the header.
> {code:java}
> from("direct:input.camel")
> .setHeader(Exchange.HTTP_METHOD, constant("GET"))
> .setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
> .setHeader(Exchange.HTTP_URI, 
> simple("/greeting/hello/${body}"))
> //.setHeader(Exchange.HTTP_PATH, 
> simple("/greeting/hello/${body}")) // <- fails
> .inOut("cxfrs:bean:rsClient");
> {code}
> Otherwise it fails with {{404}} error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10429) CXFRS client requires Exchange.HTTP_URI instead of HTTP_PATH for Camel tranport

2016-11-01 Thread Tadayoshi Sato (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tadayoshi Sato updated CAMEL-10429:
---
Description: 
The [camel-cxfrs doc|http://camel.apache.org/cxfrs.html] writes that 
{{HTTP_PATH}} is required for {{camel-cxfrs}} producer when it's used with 
{{httpClientAPI}} option.
{quote}
The CXF JAXRS front end also provides a http centric client API. You can also 
invoke this API from camel-cxfrs producer. *You need to specify the HTTP_PATH 
and the HTTP_METHOD* and let the producer use the http centric client API by 
using the URI option httpClientAPI or by setting the message header 
CxfConstants.CAMEL_CXF_RS_USING_HTTP_API.
{quote}
However, when Camel transport is used between CXFRS producer and consumer, the 
invocation succeeds only if it sets {{HTTP_URI}}, not {{HTTP_PATH}}, to the 
header.
{code:java}
from("direct:input.camel")
.setHeader(Exchange.HTTP_METHOD, constant("GET"))
.setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
.setHeader(Exchange.HTTP_URI, 
simple("/greeting/hello/${body}"))
//.setHeader(Exchange.HTTP_PATH, 
simple("/greeting/hello/${body}")) // <- fails
.inOut("cxfrs:bean:rsClient");
{code}
Otherwise it fails with {{404}} error.

  was:
The [camel-cxfrs doc|http://camel.apache.org/cxfrs.html] writes that 
{{HTTP_PATH}} is required for {{camel-cxfrs}} producer when it's used with 
{{httpClientAPI}} option.
{quote}
The CXF JAXRS front end also provides a http centric client API. You can also 
invoke this API from camel-cxfrs producer. *You need to specify the HTTP_PATH 
and the HTTP_METHOD* and let the producer use the http centric client API by 
using the URI option httpClientAPI or by setting the message header 
CxfConstants.CAMEL_CXF_RS_USING_HTTP_API.
{quote}
However, when Camel transport is used between CXFRS producer and consumer, the 
invocation succeeds only if it sets {{HTTP_URI}}, not {{HTTP_PATH}}, to the 
header. Otherwise it fails with {{404}} error.
{code:java}
from("direct:input.camel")
.setHeader(Exchange.HTTP_METHOD, constant("GET"))
.setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
.setHeader(Exchange.HTTP_URI, 
simple("/greeting/hello/${body}"))
//.setHeader(Exchange.HTTP_PATH, 
simple("/greeting/hello/${body}")) // <- fails
.inOut("cxfrs:bean:rsClient");
{code}


> CXFRS client requires Exchange.HTTP_URI instead of HTTP_PATH for Camel 
> tranport
> ---
>
> Key: CAMEL-10429
> URL: https://issues.apache.org/jira/browse/CAMEL-10429
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxfrs
>Affects Versions: 2.18.0
>Reporter: Tadayoshi Sato
>
> The [camel-cxfrs doc|http://camel.apache.org/cxfrs.html] writes that 
> {{HTTP_PATH}} is required for {{camel-cxfrs}} producer when it's used with 
> {{httpClientAPI}} option.
> {quote}
> The CXF JAXRS front end also provides a http centric client API. You can also 
> invoke this API from camel-cxfrs producer. *You need to specify the HTTP_PATH 
> and the HTTP_METHOD* and let the producer use the http centric client API by 
> using the URI option httpClientAPI or by setting the message header 
> CxfConstants.CAMEL_CXF_RS_USING_HTTP_API.
> {quote}
> However, when Camel transport is used between CXFRS producer and consumer, 
> the invocation succeeds only if it sets {{HTTP_URI}}, not {{HTTP_PATH}}, to 
> the header.
> {code:java}
> from("direct:input.camel")
> .setHeader(Exchange.HTTP_METHOD, constant("GET"))
> .setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
> .setHeader(Exchange.HTTP_URI, 
> simple("/greeting/hello/${body}"))
> //.setHeader(Exchange.HTTP_PATH, 
> simple("/greeting/hello/${body}")) // <- fails
> .inOut("cxfrs:bean:rsClient");
> {code}
> Otherwise it fails with {{404}} error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10429) CXFRS client requires Exchange.HTTP_URI instead of HTTP_PATH for Camel tranport

2016-11-01 Thread Tadayoshi Sato (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tadayoshi Sato updated CAMEL-10429:
---
Description: 
The [camel-cxfrs doc|http://camel.apache.org/cxfrs.html] writes that 
{{HTTP_PATH}} is required for {{camel-cxfrs}} producer when it's used with 
{{httpClientAPI}} option.
{quote}
The CXF JAXRS front end also provides a http centric client API. You can also 
invoke this API from camel-cxfrs producer. *You need to specify the HTTP_PATH 
and the HTTP_METHOD* and let the producer use the http centric client API by 
using the URI option httpClientAPI or by setting the message header 
CxfConstants.CAMEL_CXF_RS_USING_HTTP_API.
{quote}
However, when Camel transport is used between CXFRS producer and consumer, the 
invocation succeeds only if it sets {{HTTP_URI}}, not {{HTTP_PATH}}, to the 
header. Otherwise it fails with {{404}} error.
{code:java}
from("direct:input.camel")
.setHeader(Exchange.HTTP_METHOD, constant("GET"))
.setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
.setHeader(Exchange.HTTP_URI, 
simple("/greeting/hello/${body}"))
//.setHeader(Exchange.HTTP_PATH, 
simple("/greeting/hello/${body}")) // <- fails
.inOut("cxfrs:bean:rsClient");
{code}

  was:
The [camel-cxfrs doc|http://camel.apache.org/cxfrs.html] writes that 
{{HTTP_PATH}} is required for {{camel-cxfrs}} producer when it's used with 
{{httpClientAPI}} option.
{quote}
The CXF JAXRS front end also provides a http centric client API. You can also 
invoke this API from camel-cxfrs producer. You need to specify the HTTP_PATH 
and the HTTP_METHOD and let the producer use the http centric client API by 
using the URI option httpClientAPI or by setting the message header 
CxfConstants.CAMEL_CXF_RS_USING_HTTP_API.
{quote}
However, when Camel transport is used between CXFRS producer and consumer, the 
invocation succeeds only if it sets {{HTTP_URI}}, not {{HTTP_PATH}}, to the 
header. Otherwise it fails with {{404}} error.
{code:java}
from("direct:input.camel")
.setHeader(Exchange.HTTP_METHOD, constant("GET"))
.setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
.setHeader(Exchange.HTTP_URI, 
simple("/greeting/hello/${body}"))
//.setHeader(Exchange.HTTP_PATH, 
simple("/greeting/hello/${body}")) // <- fails
.inOut("cxfrs:bean:rsClient");
{code}


> CXFRS client requires Exchange.HTTP_URI instead of HTTP_PATH for Camel 
> tranport
> ---
>
> Key: CAMEL-10429
> URL: https://issues.apache.org/jira/browse/CAMEL-10429
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxfrs
>Affects Versions: 2.18.0
>Reporter: Tadayoshi Sato
>
> The [camel-cxfrs doc|http://camel.apache.org/cxfrs.html] writes that 
> {{HTTP_PATH}} is required for {{camel-cxfrs}} producer when it's used with 
> {{httpClientAPI}} option.
> {quote}
> The CXF JAXRS front end also provides a http centric client API. You can also 
> invoke this API from camel-cxfrs producer. *You need to specify the HTTP_PATH 
> and the HTTP_METHOD* and let the producer use the http centric client API by 
> using the URI option httpClientAPI or by setting the message header 
> CxfConstants.CAMEL_CXF_RS_USING_HTTP_API.
> {quote}
> However, when Camel transport is used between CXFRS producer and consumer, 
> the invocation succeeds only if it sets {{HTTP_URI}}, not {{HTTP_PATH}}, to 
> the header. Otherwise it fails with {{404}} error.
> {code:java}
> from("direct:input.camel")
> .setHeader(Exchange.HTTP_METHOD, constant("GET"))
> .setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
> .setHeader(Exchange.HTTP_URI, 
> simple("/greeting/hello/${body}"))
> //.setHeader(Exchange.HTTP_PATH, 
> simple("/greeting/hello/${body}")) // <- fails
> .inOut("cxfrs:bean:rsClient");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10429) CXFRS client requires Exchange.HTTP_URI instead of HTTP_PATH for Camel tranport

2016-11-01 Thread Tadayoshi Sato (JIRA) 
Tadayoshi Sato created CAMEL-10429:
--

 Summary: CXFRS client requires Exchange.HTTP_URI instead of 
HTTP_PATH for Camel tranport
 Key: CAMEL-10429
 URL: https://issues.apache.org/jira/browse/CAMEL-10429
 Project: Camel
  Issue Type: Bug
  Components: camel-cxfrs
Affects Versions: 2.18.0
Reporter: Tadayoshi Sato


The [camel-cxfrs doc|http://camel.apache.org/cxfrs.html] writes that 
{{HTTP_PATH}} is required for {{camel-cxfrs}} producer when it's used with 
{{httpClientAPI}} option.
{quote}
The CXF JAXRS front end also provides a http centric client API. You can also 
invoke this API from camel-cxfrs producer. You need to specify the HTTP_PATH 
and the HTTP_METHOD and let the producer use the http centric client API by 
using the URI option httpClientAPI or by setting the message header 
CxfConstants.CAMEL_CXF_RS_USING_HTTP_API.
{quote}
However, when Camel transport is used between CXFRS producer and consumer, the 
invocation succeeds only if it sets {{HTTP_URI}}, not {{HTTP_PATH}}, to the 
header. Otherwise it fails with {{404}} error.
{code:java}
from("direct:input.camel")
.setHeader(Exchange.HTTP_METHOD, constant("GET"))
.setHeader(Exchange.CONTENT_TYPE, constant("text/plain"))
.setHeader(Exchange.HTTP_URI, 
simple("/greeting/hello/${body}"))
//.setHeader(Exchange.HTTP_PATH, 
simple("/greeting/hello/${body}")) // <- fails
.inOut("cxfrs:bean:rsClient");
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10428) Cannot compile master code

2016-11-01 Thread Andrea Cosentino (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15624688#comment-15624688
 ] 

Andrea Cosentino commented on CAMEL-10428:
--

In the past I had problem with the Italian language.

Anyway I have no problem to compile actually. What JDK are you using?

> Cannot compile master code
> --
>
> Key: CAMEL-10428
> URL: https://issues.apache.org/jira/browse/CAMEL-10428
> Project: Camel
>  Issue Type: Task
>Reporter: Fabrizio Spataro
>
> mvn clean install -Pfastinstall
> i have this error, i am skipping JMX component to compile master code:
> [INFO] Camel :: Jing .. SUCCESS [  8.585 
> s]
> [INFO] Camel :: JIRA .. SUCCESS [ 27.211 
> s]
> [INFO] Camel :: JMX ... FAILURE [  4.836 
> s]
> [INFO] Camel :: Jolt .. SKIPPED
> [INFO] Camel :: Johnzon ... SKIPPED
> 
> 
> [INFO] Camel :: Example :: Zipkin :: Service 1  SKIPPED
> [INFO] Camel :: Example :: Zipkin :: Service 2  SKIPPED
> [INFO] Camel :: Assembly .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29:14 min
> [INFO] Finished at: 2016-11-01T08:10:53+01:00
> [INFO] Final Memory: 1212M/2906M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate (default) on project 
> camel-jmx: Execution default of goal 
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate failed: Illegal 
> pattern character 'g' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10428) Cannot compile master code

2016-11-01 Thread Fabrizio Spataro (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15624685#comment-15624685
 ] 

Fabrizio Spataro commented on CAMEL-10428:
--

i have maven default settings + "-Xms3000m -Xmx3000m" and italian language!

I will try to change language so there is a new mandatory compile option? 
With camel-2.18 it is all ok


> Cannot compile master code
> --
>
> Key: CAMEL-10428
> URL: https://issues.apache.org/jira/browse/CAMEL-10428
> Project: Camel
>  Issue Type: Task
>Reporter: Fabrizio Spataro
>
> mvn clean install -Pfastinstall
> i have this error, i am skipping JMX component to compile master code:
> [INFO] Camel :: Jing .. SUCCESS [  8.585 
> s]
> [INFO] Camel :: JIRA .. SUCCESS [ 27.211 
> s]
> [INFO] Camel :: JMX ... FAILURE [  4.836 
> s]
> [INFO] Camel :: Jolt .. SKIPPED
> [INFO] Camel :: Johnzon ... SKIPPED
> 
> 
> [INFO] Camel :: Example :: Zipkin :: Service 1  SKIPPED
> [INFO] Camel :: Example :: Zipkin :: Service 2  SKIPPED
> [INFO] Camel :: Assembly .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29:14 min
> [INFO] Finished at: 2016-11-01T08:10:53+01:00
> [INFO] Final Memory: 1212M/2906M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate (default) on project 
> camel-jmx: Execution default of goal 
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate failed: Illegal 
> pattern character 'g' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10428) Cannot compile master code

2016-11-01 Thread Andrea Cosentino (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15624665#comment-15624665
 ] 

Andrea Cosentino commented on CAMEL-10428:
--

For the first error. Are you using Italian language?

Try to set LANG to en_US.UTF-8.

Also what are your setting for min heap and max heap?

> Cannot compile master code
> --
>
> Key: CAMEL-10428
> URL: https://issues.apache.org/jira/browse/CAMEL-10428
> Project: Camel
>  Issue Type: Task
>Reporter: Fabrizio Spataro
>
> mvn clean install -Pfastinstall
> i have this error, i am skipping JMX component to compile master code:
> [INFO] Camel :: Jing .. SUCCESS [  8.585 
> s]
> [INFO] Camel :: JIRA .. SUCCESS [ 27.211 
> s]
> [INFO] Camel :: JMX ... FAILURE [  4.836 
> s]
> [INFO] Camel :: Jolt .. SKIPPED
> [INFO] Camel :: Johnzon ... SKIPPED
> 
> 
> [INFO] Camel :: Example :: Zipkin :: Service 1  SKIPPED
> [INFO] Camel :: Example :: Zipkin :: Service 2  SKIPPED
> [INFO] Camel :: Assembly .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29:14 min
> [INFO] Finished at: 2016-11-01T08:10:53+01:00
> [INFO] Final Memory: 1212M/2906M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate (default) on project 
> camel-jmx: Execution default of goal 
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate failed: Illegal 
> pattern character 'g' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10428) Cannot compile master code

2016-11-01 Thread Fabrizio Spataro (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15624642#comment-15624642
 ] 

Fabrizio Spataro commented on CAMEL-10428:
--

There is another compile error:


[INFO] Camel :: Olingo2 :: Parent . SUCCESS [  0.117 s]
[INFO] Camel :: Olingo2 :: API  SUCCESS [  4.143 s]
[INFO] Camel :: Olingo2 :: Component .. FAILURE [  3.385 s]
[INFO] Camel :: OpenShift (deprecated)  SKIPPED
[INFO] Camel :: OptaPlanner ... SKIPPED
..
[INFO] Camel :: Assembly .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 03:11 min
[INFO] Finished at: 2016-11-01T08:25:50+01:00
[INFO] Final Memory: 1089M/2929M
[INFO] 
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:exec 
(generate-sources) on project camel-olingo2: Command execution failed. Process 
exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.


> Cannot compile master code
> --
>
> Key: CAMEL-10428
> URL: https://issues.apache.org/jira/browse/CAMEL-10428
> Project: Camel
>  Issue Type: Task
>Reporter: Fabrizio Spataro
>
> mvn clean install -Pfastinstall
> i have this error, i am skipping JMX component to compile master code:
> [INFO] Camel :: Jing .. SUCCESS [  8.585 
> s]
> [INFO] Camel :: JIRA .. SUCCESS [ 27.211 
> s]
> [INFO] Camel :: JMX ... FAILURE [  4.836 
> s]
> [INFO] Camel :: Jolt .. SKIPPED
> [INFO] Camel :: Johnzon ... SKIPPED
> 
> 
> [INFO] Camel :: Example :: Zipkin :: Service 1  SKIPPED
> [INFO] Camel :: Example :: Zipkin :: Service 2  SKIPPED
> [INFO] Camel :: Assembly .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29:14 min
> [INFO] Finished at: 2016-11-01T08:10:53+01:00
> [INFO] Final Memory: 1212M/2906M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate (default) on project 
> camel-jmx: Execution default of goal 
> org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate failed: Illegal 
> pattern character 'g' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10428) Cannot compile master code

2016-11-01 Thread Fabrizio Spataro (JIRA) 
Fabrizio Spataro created CAMEL-10428:


 Summary: Cannot compile master code
 Key: CAMEL-10428
 URL: https://issues.apache.org/jira/browse/CAMEL-10428
 Project: Camel
  Issue Type: Task
Reporter: Fabrizio Spataro


mvn clean install -Pfastinstall

i have this error, i am skipping JMX component to compile master code:

[INFO] Camel :: Jing .. SUCCESS [  8.585 s]
[INFO] Camel :: JIRA .. SUCCESS [ 27.211 s]
[INFO] Camel :: JMX ... FAILURE [  4.836 s]
[INFO] Camel :: Jolt .. SKIPPED
[INFO] Camel :: Johnzon ... SKIPPED


[INFO] Camel :: Example :: Zipkin :: Service 1  SKIPPED
[INFO] Camel :: Example :: Zipkin :: Service 2  SKIPPED
[INFO] Camel :: Assembly .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 29:14 min
[INFO] Finished at: 2016-11-01T08:10:53+01:00
[INFO] Final Memory: 1212M/2906M
[INFO] 
[ERROR] Failed to execute goal 
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate (default) on project 
camel-jmx: Execution default of goal 
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate failed: Illegal 
pattern character 'g' -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10427) CXFRS client gets "Response timeout" exception when used with Camel transport

2016-11-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CAMEL-10427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15624499#comment-15624499
 ] 

ASF GitHub Bot commented on CAMEL-10427:


GitHub user tadayosi opened a pull request:

https://github.com/apache/camel/pull/1240

CAMEL-10427 - CXFRS client gets "Response timeout" exception when used with 
Camel transport

https://issues.apache.org/jira/browse/CAMEL-10427
https://issues.jboss.org/browse/ENTESB-6028

Made `CxfHeaderHelper` aware of mapping between Camel 
`Exchange.HTTP_RESPONSE_CODE` <-> CXF `Message.RESPONSE_CODE`.

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

$ git pull https://github.com/tadayosi/camel CAMEL-10427

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

https://github.com/apache/camel/pull/1240.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 #1240


commit f7443a03264b1363cf996c98538640923012f2bd
Author: Tadayoshi Sato 
Date:   2016-11-01T05:19:01Z

CAMEL-10427 - CXFRS client gets "Response timeout" exception when used with 
Camel transport




> CXFRS client gets "Response timeout" exception when used with Camel transport
> -
>
> Key: CAMEL-10427
> URL: https://issues.apache.org/jira/browse/CAMEL-10427
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxfrs
>Affects Versions: 2.18.0
>Reporter: Tadayoshi Sato
> Attachments: camel-cxf-transport.zip
>
>
> When a CXFRS client is used with Camel transport:
> {code:java}
>   
> {code}
> it throws the following exception waiting for a response from the target REST 
> server:
> {code}
> javax.ws.rs.ProcessingException: Response timeout
> at 
> org.apache.cxf.jaxrs.client.AbstractClient.waitForResponseCode(AbstractClient.java:617)
> at 
> org.apache.cxf.jaxrs.client.AbstractClient.checkClientException(AbstractClient.java:598)
> at 
> org.apache.cxf.jaxrs.client.AbstractClient.preProcessResult(AbstractClient.java:580)
> at org.apache.cxf.jaxrs.client.WebClient.doResponse(WebClient.java:1098)
> at 
> org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1035)
> at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:892)
> at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:863)
> at org.apache.cxf.jaxrs.client.WebClient.invoke(WebClient.java:329)
> at 
> org.apache.camel.component.cxf.jaxrs.CxfRsProducer.invokeHttpClient(CxfRsProducer.java:210)
> at 
> org.apache.camel.component.cxf.jaxrs.CxfRsProducer.process(CxfRsProducer.java:89)
> [...]
> {code}
> unless you explicitly remap the following header:
> {code:xml}
> 
> ${headers.CamelHttpResponseCode}
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)