[jira] [Commented] (CAMEL-11262) camel-google-pubsub - Improve to work with streaming mode

[Sarel Lugtenburg (JIRA)]

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

Sarel Lugtenburg commented on CAMEL-11262:
--

I have create PR https://github.com/apache/camel/pull/1837 for camel pubsub 
example (against current pubsub rest implementation)


> camel-google-pubsub - Improve to work with streaming mode
> -
>
> Key: CAMEL-11262
> URL: https://issues.apache.org/jira/browse/CAMEL-11262
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-google-pubsub
>Affects Versions: 2.19.0
>Reporter: Claus Ibsen
> Fix For: 2.20.0
>
>
> The pubsub component
> https://github.com/apache/camel/tree/master/components/camel-google-pubsub
> Can likely be improved to work better with streaming mode and use Camel 
> asynchronous processing. 
> There may be other things.
> Ray Tsang from Google has some ideas and want to help out.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11570) Add an example for camel-google-pubsub

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11570:


GitHub user sarelp opened a pull request:

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

CAMEL-11570: Added example for camel-google-pubsub



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

$ git pull https://github.com/ScentreGroup/camel 
feature/CAMEL-11570-camel-google-pubsub-example

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

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


commit 6f5b59363cec9b0006d36124669eedcd4f744ab1
Author: sarelp 
Date:   2017-07-21T01:32:01Z

CAMEL-11570: Added example for camel-google-pubsub




> Add an example for camel-google-pubsub
> --
>
> Key: CAMEL-11570
> URL: https://issues.apache.org/jira/browse/CAMEL-11570
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-google-pubsub
>Reporter: Sarel Lugtenburg
>Priority: Trivial
> Fix For: 2.20.0
>
>
> Add an example in examples for camel-google-pubsub component.
> The example is done against the camel-google-pubsub rest interface



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11570) Add an example for camel-google-pubsub

[Sarel Lugtenburg (JIRA)]

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

Sarel Lugtenburg updated CAMEL-11570:
-
Description: 
Add an example in examples for camel-google-pubsub component.

The example is done against the camel-google-pubsub rest interface

  was:
Add an example in examples for camel-google-pubsub component.




> Add an example for camel-google-pubsub
> --
>
> Key: CAMEL-11570
> URL: https://issues.apache.org/jira/browse/CAMEL-11570
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-google-pubsub
>Reporter: Sarel Lugtenburg
>Priority: Trivial
> Fix For: 2.20.0
>
>
> Add an example in examples for camel-google-pubsub component.
> The example is done against the camel-google-pubsub rest interface



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11571) Google Cloud BigQuery

[Evgeny Minkevich (JIRA)]

Evgeny Minkevich created CAMEL-11571:


 Summary: Google Cloud BigQuery
 Key: CAMEL-11571
 URL: https://issues.apache.org/jira/browse/CAMEL-11571
 Project: Camel
  Issue Type: New Feature
Reporter: Evgeny Minkevich


As a solution architect I would like to be able to write messages into Google 
BigQuery via Google BigQuery Streaming API:

https://cloud.google.com/bigquery/streaming-data-into-bigquery




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11570) Add an example for camel-google-pubsub

[Sarel Lugtenburg (JIRA)]

Sarel Lugtenburg created CAMEL-11570:


 Summary: Add an example for camel-google-pubsub
 Key: CAMEL-11570
 URL: https://issues.apache.org/jira/browse/CAMEL-11570
 Project: Camel
  Issue Type: Improvement
  Components: camel-google-pubsub
Reporter: Sarel Lugtenburg
Priority: Trivial
 Fix For: 2.20.0


Add an example in examples for camel-google-pubsub component.





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11531) camel-http-common; dependency servlet-api should be set to provided

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11531:


GitHub user onders86 reopened a pull request:

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

CAMEL-11531 - set servlet dependency as provided



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

$ git pull https://github.com/onders86/camel CAMEL-11531

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

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


commit 826da2c6445726ffe3d412ecc3719aa1fdd87c4d
Author: onders86 
Date:   2017-07-20T11:19:26Z

CAMEL-11531 - set servlet dependency as provided




> camel-http-common; dependency servlet-api should be set to provided
> ---
>
> Key: CAMEL-11531
> URL: https://issues.apache.org/jira/browse/CAMEL-11531
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-http-common, camel-servlet
>Affects Versions: 2.19.0
>Reporter: Harmen Renkema
>Assignee: Önder Sezgin
>Priority: Minor
> Fix For: 2.19.2, 2.20.0
>
>
> When using camel-servlet in WAR apps, the dependency on camel-http-common 
> brings in the servlet-api as a dependency with scope compile. The scope of 
> this dependency should be set to provided as it will be provided by the 
> container.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-11569) Implements CAMEL-11425 for camel-olingo4

[Dmitry Volodin (JIRA)]

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

Work on CAMEL-11569 started by Dmitry Volodin.
--
> Implements CAMEL-11425 for camel-olingo4
> 
>
> Key: CAMEL-11569
> URL: https://issues.apache.org/jira/browse/CAMEL-11569
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-olingo4
>Affects Versions: 2.20.0
>Reporter: Dmitry Volodin
>Assignee: Dmitry Volodin
> Fix For: 2.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (CAMEL-11531) camel-http-common; dependency servlet-api should be set to provided

[JIRA]

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

Önder Sezgin reopened CAMEL-11531:
--

due to spring-boot starter, reopening

> camel-http-common; dependency servlet-api should be set to provided
> ---
>
> Key: CAMEL-11531
> URL: https://issues.apache.org/jira/browse/CAMEL-11531
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-http-common, camel-servlet
>Affects Versions: 2.19.0
>Reporter: Harmen Renkema
>Assignee: Önder Sezgin
>Priority: Minor
> Fix For: 2.19.2, 2.20.0
>
>
> When using camel-servlet in WAR apps, the dependency on camel-http-common 
> brings in the servlet-api as a dependency with scope compile. The scope of 
> this dependency should be set to provided as it will be provided by the 
> container.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11168) Add deprecationNote to @Metadata

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11168.
-
Resolution: Fixed

Its now also included in the readme docs so we have options which are 
deprecated highlighted there.

> Add deprecationNote to @Metadata
> 
>
> Key: CAMEL-11168
> URL: https://issues.apache.org/jira/browse/CAMEL-11168
> Project: Camel
>  Issue Type: Improvement
>  Components: tooling
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> So we can add a note that can refer the user to something else, eg mina -> 
> mina2 etc. Then we can use the tooling to grab that note and add to the 
> readme files etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11443) Add a RouteController SPI to allow to customize routes life-cycle

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli resolved CAMEL-11443.
-
Resolution: Fixed

For camel 2.x this is more like a placeholder and will be reworked in 3.0, see:

- CAMEL-11565
- CAMEL-11566



> Add a RouteController SPI to allow to customize routes life-cycle
> -
>
> Key: CAMEL-11443
> URL: https://issues.apache.org/jira/browse/CAMEL-11443
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-blueprint, camel-core, camel-core-xml, 
> camel-spring, camel-spring-boot
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
> Fix For: 2.20.0
>
>
> As today the route life cycle is managed by the camel context and it is not 
> easy to hook into that process to implement custom startup/shutdown logic so 
> it would be nice to have a new SPI allowing 3rd parties to easily implement 
> custom logic.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11531) camel-http-common; dependency servlet-api should be set to provided

[JIRA]

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

Önder Sezgin resolved CAMEL-11531.
--
Resolution: Fixed

> camel-http-common; dependency servlet-api should be set to provided
> ---
>
> Key: CAMEL-11531
> URL: https://issues.apache.org/jira/browse/CAMEL-11531
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-http-common, camel-servlet
>Affects Versions: 2.19.0
>Reporter: Harmen Renkema
>Assignee: Önder Sezgin
>Priority: Minor
> Fix For: 2.19.2, 2.20.0
>
>
> When using camel-servlet in WAR apps, the dependency on camel-http-common 
> brings in the servlet-api as a dependency with scope compile. The scope of 
> this dependency should be set to provided as it will be provided by the 
> container.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11531) camel-http-common; dependency servlet-api should be set to provided

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11531:


Github user onders86 closed the pull request at:

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


> camel-http-common; dependency servlet-api should be set to provided
> ---
>
> Key: CAMEL-11531
> URL: https://issues.apache.org/jira/browse/CAMEL-11531
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-http-common, camel-servlet
>Affects Versions: 2.19.0
>Reporter: Harmen Renkema
>Assignee: Önder Sezgin
>Priority: Minor
> Fix For: 2.19.2, 2.20.0
>
>
> When using camel-servlet in WAR apps, the dependency on camel-http-common 
> brings in the servlet-api as a dependency with scope compile. The scope of 
> this dependency should be set to provided as it will be provided by the 
> container.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11168) Add deprecationNote to @Metadata

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-11168:
---

Assignee: Claus Ibsen

> Add deprecationNote to @Metadata
> 
>
> Key: CAMEL-11168
> URL: https://issues.apache.org/jira/browse/CAMEL-11168
> Project: Camel
>  Issue Type: Improvement
>  Components: tooling
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> So we can add a note that can refer the user to something else, eg mina -> 
> mina2 etc. Then we can use the tooling to grab that note and add to the 
> readme files etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11144) camel-milo - Use dynamic port in test

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11144.
-
Resolution: Fixed

> camel-milo - Use dynamic port in test
> -
>
> Key: CAMEL-11144
> URL: https://issues.apache.org/jira/browse/CAMEL-11144
> Project: Camel
>  Issue Type: Test
>Reporter: Claus Ibsen
>Assignee: Jens Reimann
> Fix For: 2.20.0
>
>
> This component uses hard coded port numbers which should be dynamic assigned 
> so it tests better on CI servers etc.
> Also the tests must be improved as they tend to hang etc.
> And the test code should be polished and updated as it has a bunch of 
> commented out stuff and seems personal hostnames etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11459) Upgrade CXF to 3.2

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11459:
-

Is there an ETA on CXF 3.2.0 release? We aim to do a Camel 2.20.0 release in 
September

> Upgrade CXF to 3.2
> --
>
> Key: CAMEL-11459
> URL: https://issues.apache.org/jira/browse/CAMEL-11459
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cxf
>Reporter: Guillaume Nodet
> Fix For: 2.20.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11525) Run tests in camel-core in parallel via test suites

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11525:

Fix Version/s: Future

> Run tests in camel-core in parallel via test suites
> ---
>
> Key: CAMEL-11525
> URL: https://issues.apache.org/jira/browse/CAMEL-11525
> Project: Camel
>  Issue Type: Test
>  Components: camel-core, tests
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> Look at using test suites so we can divide the tests into different groups, 
> and let them run in parallel. For example we can group by 
> org.apache.camel.xxx package level and run each in parallel depending on 
> number of cpu cores etc.
> I wonder if this tool can make it possible to setup the suites filtering via 
> the wildcard matching so we can do this easily
> https://github.com/michaeltamm/junit-toolbox
> See also
> https://stackoverflow.com/questions/7331214/junit4-run-all-tests-in-a-specific-package-using-a-testsuite
> And maven surefire plugin
> http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11132) Provide type metadata for each Components/DataFormats

[Tomohisa Igarashi (JIRA)]

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

Tomohisa Igarashi updated CAMEL-11132:
--
Fix Version/s: (was: 2.20.0)
   3.0.0

> Provide type metadata for each Components/DataFormats
> -
>
> Key: CAMEL-11132
> URL: https://issues.apache.org/jira/browse/CAMEL-11132
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Tomohisa Igarashi
>Assignee: Tomohisa Igarashi
> Fix For: 3.0.0
>
>
> CAMEL-10447 has introduced InputType/OutputType declaration and declarative 
> Transformer/Validator based on those types declared on a route.
> Next step is to provide type metadata for each Components/DataFormats:
> * Let components/DataFormats provide metadata about what data types are 
> supported so that app developer can see
> * Narrow down the possible data types (i.e. exclude unsupported types) and 
> transformers when writing a route in IDE, allow IDE to show those candidates 
> as a hint so that app developer can choose from. Also maven plugin could 
> leverage those metadata
> * Provide such facility from camel side so that the maven plugin and/or IDE 
> can leverage it
> Annotation would be an option, but it only provides static types. For example 
> xslt component only consumes/produces XML so "XML" could be provided via 
> annotation. But dozer component consumes/produces arbitrary data formats and 
> the actual type to be used is determined via configuration, so it cannot be 
> provided via annotation. It would need a common way to calculate possible 
> input types and output types on a component/endpoint and dataformat from its 
> configuration.
> Sometimes even body of the input message would affect the possible output 
> types. To visualize this we'll need some kind of simulation with a test 
> message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11569) Implements CAMEL-11425 for camel-olingo4

[Dmitry Volodin (JIRA)]

Dmitry Volodin created CAMEL-11569:
--

 Summary: Implements CAMEL-11425 for camel-olingo4
 Key: CAMEL-11569
 URL: https://issues.apache.org/jira/browse/CAMEL-11569
 Project: Camel
  Issue Type: Improvement
  Components: camel-olingo4
Affects Versions: 2.20.0
Reporter: Dmitry Volodin
Assignee: Dmitry Volodin
 Fix For: 2.20.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11531) camel-http-common; dependency servlet-api should be set to provided

[JIRA]

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

Önder Sezgin reassigned CAMEL-11531:


Assignee: Önder Sezgin

> camel-http-common; dependency servlet-api should be set to provided
> ---
>
> Key: CAMEL-11531
> URL: https://issues.apache.org/jira/browse/CAMEL-11531
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-http-common, camel-servlet
>Affects Versions: 2.19.0
>Reporter: Harmen Renkema
>Assignee: Önder Sezgin
>Priority: Minor
> Fix For: 2.19.2, 2.20.0
>
>
> When using camel-servlet in WAR apps, the dependency on camel-http-common 
> brings in the servlet-api as a dependency with scope compile. The scope of 
> this dependency should be set to provided as it will be provided by the 
> container.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11531) camel-http-common; dependency servlet-api should be set to provided

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11531:


GitHub user onders86 opened a pull request:

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

CAMEL-11531 - set servlet dependency as provided



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

$ git pull https://github.com/onders86/camel CAMEL-11531

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

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


commit 826da2c6445726ffe3d412ecc3719aa1fdd87c4d
Author: onders86 
Date:   2017-07-20T11:19:26Z

CAMEL-11531 - set servlet dependency as provided




> camel-http-common; dependency servlet-api should be set to provided
> ---
>
> Key: CAMEL-11531
> URL: https://issues.apache.org/jira/browse/CAMEL-11531
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-http-common, camel-servlet
>Affects Versions: 2.19.0
>Reporter: Harmen Renkema
>Priority: Minor
> Fix For: 2.19.2, 2.20.0
>
>
> When using camel-servlet in WAR apps, the dependency on camel-http-common 
> brings in the servlet-api as a dependency with scope compile. The scope of 
> this dependency should be set to provided as it will be provided by the 
> container.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11144) camel-milo - Use dynamic port in test

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11144:


Github user ctron closed the pull request at:

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


> camel-milo - Use dynamic port in test
> -
>
> Key: CAMEL-11144
> URL: https://issues.apache.org/jira/browse/CAMEL-11144
> Project: Camel
>  Issue Type: Test
>Reporter: Claus Ibsen
>Assignee: Jens Reimann
> Fix For: 2.20.0
>
>
> This component uses hard coded port numbers which should be dynamic assigned 
> so it tests better on CI servers etc.
> Also the tests must be improved as they tend to hang etc.
> And the test code should be polished and updated as it has a bunch of 
> commented out stuff and seems personal hostnames etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11568) Allow to set a CookiePolicy to CookieHandler

[Stephan Siano (JIRA)]

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

Stephan Siano resolved CAMEL-11568.
---
Resolution: Fixed

> Allow to set a CookiePolicy to CookieHandler
> 
>
> Key: CAMEL-11568
> URL: https://issues.apache.org/jira/browse/CAMEL-11568
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-http-common
>Affects Versions: 2.19.1
>Reporter: Stephan Siano
>Assignee: Stephan Siano
>Priority: Trivial
> Fix For: 2.20.0
>
>
> In some cases it might be useful to define a CookiePolicy for the 
> CookieHandler implementations included in camel-http-common. This will allow 
> some control over the cookies that can be stored by a server. See the JDK 
> javadoc for details.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11568) Allow to set a CookiePolicy to CookieHandler

[Stephan Siano (JIRA)]

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

Stephan Siano reassigned CAMEL-11568:
-

Assignee: Stephan Siano

> Allow to set a CookiePolicy to CookieHandler
> 
>
> Key: CAMEL-11568
> URL: https://issues.apache.org/jira/browse/CAMEL-11568
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-http-common
>Affects Versions: 2.19.1
>Reporter: Stephan Siano
>Assignee: Stephan Siano
>Priority: Trivial
> Fix For: 2.20.0
>
>
> In some cases it might be useful to define a CookiePolicy for the 
> CookieHandler implementations included in camel-http-common. This will allow 
> some control over the cookies that can be stored by a server. See the JDK 
> javadoc for details.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11568) Allow to set a CookiePolicy to CookieHandler

[Stephan Siano (JIRA)]

Stephan Siano created CAMEL-11568:
-

 Summary: Allow to set a CookiePolicy to CookieHandler
 Key: CAMEL-11568
 URL: https://issues.apache.org/jira/browse/CAMEL-11568
 Project: Camel
  Issue Type: Improvement
  Components: camel-http-common
Affects Versions: 2.19.1
Reporter: Stephan Siano
Priority: Trivial
 Fix For: 2.20.0


In some cases it might be useful to define a CookiePolicy for the CookieHandler 
implementations included in camel-http-common. This will allow some control 
over the cookies that can be stored by a server. See the JDK javadoc for 
details.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11059) camel-spring-dm - Should be removed

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11059.
-
Resolution: Fixed

> camel-spring-dm - Should be removed
> ---
>
> Key: CAMEL-11059
> URL: https://issues.apache.org/jira/browse/CAMEL-11059
> Project: Camel
>  Issue Type: Task
>  Components: karaf, osgi
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> Does not really work in OSGi
> http://camel.465427.n5.nabble.com/camel-spring-dm-feature-incompatible-to-most-other-features-of-camel-2-18-3-tp5796032.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-11567) ServiceNow : add suport for Jakarta release

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-11567:
---

 Summary: ServiceNow : add suport for Jakarta release
 Key: CAMEL-11567
 URL: https://issues.apache.org/jira/browse/CAMEL-11567
 Project: Camel
  Issue Type: Improvement
  Components: camel-servicenow
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor
 Fix For: 2.20.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-11059) camel-spring-dm - Should be removed

[Claus Ibsen (JIRA)]

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

Claus Ibsen reassigned CAMEL-11059:
---

Assignee: Claus Ibsen

> camel-spring-dm - Should be removed
> ---
>
> Key: CAMEL-11059
> URL: https://issues.apache.org/jira/browse/CAMEL-11059
> Project: Camel
>  Issue Type: Task
>  Components: karaf, osgi
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> Does not really work in OSGi
> http://camel.465427.n5.nabble.com/camel-spring-dm-feature-incompatible-to-most-other-features-of-camel-2-18-3-tp5796032.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11199) Service Call : provides an ServiceHealthFilter that leverages PingChek/HealthCheck APIs

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11199:

Fix Version/s: (was: 2.20.0)
   Future
   3.0.0

> Service Call : provides an ServiceHealthFilter that leverages 
> PingChek/HealthCheck APIs
> ---
>
> Key: CAMEL-11199
> URL: https://issues.apache.org/jira/browse/CAMEL-11199
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, Future
>
>
> If the service definition provides an health endpoint and no information 
> about the health, we should thinking about leverages ping check api to filter 
> out unhealthy services.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11128) camel-rest : rest factories should leverage http-commons

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11128:

Fix Version/s: (was: 2.20.0)
   Future
   3.0.0

> camel-rest : rest factories should leverage http-commons
> 
>
> Key: CAMEL-11128
> URL: https://issues.apache.org/jira/browse/CAMEL-11128
> Project: Camel
>  Issue Type: Wish
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, Future
>
>
> camel-rest creates producer and consumer using a factory which signatures 
> look like:
> {code:java}
> Producer createProducer(
> CamelContext camelContext, 
> String host,
> String verb, 
> String basePath, 
> String uriTemplate, 
> String queryParameters,
> String consumes, 
> String produces, 
> Map parameters) throws Exception;
> {code}
> The factory method are a mix of specific parameters like host, basePath, etc. 
> and something more open like parameters. It would be nice to explore the 
> possibility to bring some http-commons standardization here so we can put 
> more stuffs in the generic "parameters" options which would reduce the 
> difference to setup and validate rest components.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11127) ComponentVerifier : add support for producer/consumer options validation

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11127:

Fix Version/s: (was: 2.20.0)
   Future
   3.0.0

> ComponentVerifier : add support for producer/consumer options validation
> 
>
> Key: CAMEL-11127
> URL: https://issues.apache.org/jira/browse/CAMEL-11127
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, Future
>
>
> As today the ComponentVerifier (Ping Check) perform a global validation i.e. 
> it does not check if an option is consumer or producer only which is fine but 
> there are cases where it could make sense to perform a validation for a 
> specific side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-10815) Create a saxon-xslt component

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-10815:

Fix Version/s: Future

> Create a saxon-xslt component
> -
>
> Key: CAMEL-10815
> URL: https://issues.apache.org/jira/browse/CAMEL-10815
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-saxon
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, Future
>
>
> I've recently been working on camel-saxon and camel-xslt to enable
> saxon specific stuffs in camel-xslt and this required some little
> reflection hacks which could make it harder to detect potential api
> breaks when updating saxon and could be problematic for java 9 if
> saxon does not properly configure the modules system so we should create a 
> saxon-xslt component (to be done after 2.19) which inherit from xslt 
> component and adds saxon specifc stuffs without reflection hacks.
> So with component:
> - xslt --> you can still use saxon but can't confiugre saxon specific features
> - saxon-xslt --> same as xslt but you can configure/use saxon specific 
> features
> It also ensures that users are not in doubt if they use saxon or not. Usually 
> Saxon offers more advanced features that you dont have from the JDK.
> And maybe we can add something so users can install the commercial saxon and 
> unlock xslt 3.0 functionality or what else is exclusive in their commercial 
> product.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11200) reactive-streams : create a vertx based implementation of ReactorStreamsService

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-11200:

Fix Version/s: (was: 2.20.0)
   Future
   3.0.0

> reactive-streams : create a vertx based implementation of 
> ReactorStreamsService
> ---
>
> Key: CAMEL-11200
> URL: https://issues.apache.org/jira/browse/CAMEL-11200
> Project: Camel
>  Issue Type: New Feature
>Reporter: Luca Burgazzoli
> Fix For: 3.0.0, Future
>
>
> http://vertx.io/docs/vertx-reactive-streams/java/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-10815) Create a saxon-xslt component

[Luca Burgazzoli (JIRA)]

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

Luca Burgazzoli updated CAMEL-10815:

Fix Version/s: (was: 2.20.0)
   3.0.0

> Create a saxon-xslt component
> -
>
> Key: CAMEL-10815
> URL: https://issues.apache.org/jira/browse/CAMEL-10815
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-saxon
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, Future
>
>
> I've recently been working on camel-saxon and camel-xslt to enable
> saxon specific stuffs in camel-xslt and this required some little
> reflection hacks which could make it harder to detect potential api
> breaks when updating saxon and could be problematic for java 9 if
> saxon does not properly configure the modules system so we should create a 
> saxon-xslt component (to be done after 2.19) which inherit from xslt 
> component and adds saxon specifc stuffs without reflection hacks.
> So with component:
> - xslt --> you can still use saxon but can't confiugre saxon specific features
> - saxon-xslt --> same as xslt but you can configure/use saxon specific 
> features
> It also ensures that users are not in doubt if they use saxon or not. Usually 
> Saxon offers more advanced features that you dont have from the JDK.
> And maybe we can add something so users can install the commercial saxon and 
> unlock xslt 3.0 functionality or what else is exclusive in their commercial 
> product.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11179) MultiThread race condition in DefaultShutdownStrategy for suspend/resume

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11179.
-
Resolution: Won't Fix
  Assignee: Claus Ibsen

Use with timeout with a bit of care as when a timeout occur side effects can 
happens as the shutdown did not complete graceful.

> MultiThread race condition in DefaultShutdownStrategy for suspend/resume
> 
>
> Key: CAMEL-11179
> URL: https://issues.apache.org/jira/browse/CAMEL-11179
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.18.3
>Reporter: Benjamin Graf
>Assignee: Claus Ibsen
>Priority: Minor
>
> If call to suspend with timeout does timeout than two threads are invoking 
> forced processing one for suspending and one for hard stopping. This causes 
> the Consumer to be possibly left in a dead state.
> E.g. Jms consuming route:
> # Timeout occurs, ShutdownTask gets completed before main thread
> -> JmsConsumer gets stopped (listener gets destroyed), resume has no effect
> # Timeout occurs, ShutdownTask get completet after main thread
> -> JmsConsumer gets stopped first (listener gets destroyed) and get suspended 
> second, resume sets Consumer to started but the listener is still destroyed!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11217) ExchangePattern issue with direct-vm component

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11217.
-
Resolution: Later
  Assignee: Claus Ibsen

Try with newest version as the direct-vm component has been improved since.

> ExchangePattern issue with direct-vm component
> --
>
> Key: CAMEL-11217
> URL: https://issues.apache.org/jira/browse/CAMEL-11217
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.18.3
>Reporter: Bernard Ligny
>Assignee: Claus Ibsen
>
> A *same* route definition with a In Only exchange behaves differently 
> depending on whether the call to the sub-route (of the same CamelContext) is 
> done using direct or direct-vm component.
> My personal conclusion is that the ExchangePattern for the sub-route 
> invokation seems to vary:
> - In when "direct:" used in to uri
> - inherited from "parent" exchange (=InOnly) when "direct-vm:" used in to uri
> See full problem description (and example) in Camel User forum:
> http://camel.465427.n5.nabble.com/Body-lost-with-intra-context-calls-using-direct-vm-component-td5798327.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11252) camel-core : allow to retrieve components/endpoints/etc list with a predicate

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11252:

Fix Version/s: (was: 2.20.0)
   Future
   3.0.0

> camel-core : allow to retrieve components/endpoints/etc list with a predicate
> -
>
> Key: CAMEL-11252
> URL: https://issues.apache.org/jira/browse/CAMEL-11252
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0, Future
>
>
> As today components/endpoints and so on can be retrieved/removed from the 
> camel context by id but it would be nice to have a more flexible way to 
> retrieve them like:
> {code:java}
> List components = context.getComponents(id, component -> {
> return component instanceof IdAware;
> });
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11387) SFTP is delivered into incorrect location, without exception (file in subfolder + temp file is created + Camel running on Window & SFTP server running on LINUX)

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11387:
-

Can you be more specific what is the wrong location, maybe write down an file 
example and say step by step what is happening.

> SFTP is delivered into incorrect location, without exception (file in 
> subfolder + temp file is created + Camel running on Window & SFTP server 
> running on LINUX)
> 
>
> Key: CAMEL-11387
> URL: https://issues.apache.org/jira/browse/CAMEL-11387
> Project: Camel
>  Issue Type: Bug
>  Components: camel-sftp
>Affects Versions: 2.19.0
> Environment: camel is running on Window, and SFTP server is LINUX
>Reporter: Cherry Ngai
>Priority: Minor
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> The bug only happens when:
> i) file in subfolder
> ii) temp file is created 
> iii) Camel running on Window & SFTP server running on LINUX
> Route Configuration:
> {code}
>  from("file://sourceFolder?recursive=true=6").
>  to("sftp://username@linuxServer?tempFileName=${file:onlyname}.part;);
> {code}
> NOTES: added separator=UNIX or AUTO, I got the same issue.
> Window Local File: sourceFolder/myfolder1/myfolder2/test.txt
> FTPS Remote File Delivered: $linuxServer/myfolder1myfolder2test.txt
> NOTES: 
> * There is no exception throw in 2.19.0, even though the file delivered into 
> incorrect location.  
> * In 2.17.3, exception throw at 
> org.apache.camel.component.file.remote.SftpOperations.renameFile(SftpOperations.java:431)[camel-ftp-2.17.3.jar:2.17.3]
> * Without tempFileName, it works perfectly.  Issue is around the rename area.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error

[Claus Ibsen (JIRA)]

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

Claus Ibsen commented on CAMEL-11455:
-

Did you get a chance to send a PR, as we will work on a Camel 2.19.2 release 
early next month then we need to get this fixed fairly soon

> Automatic transform String to DBObject after previous conversion error
> --
>
> Key: CAMEL-11455
> URL: https://issues.apache.org/jira/browse/CAMEL-11455
> Project: Camel
>  Issue Type: Bug
>  Components: camel-mongodb, camel-mongodb3
>Affects Versions: 2.19.1
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
> Fix For: 2.19.2, 2.20.0
>
> Attachments: jsonFormatterDisappear.zip
>
>
> Hello,
> i found a bug. To reproduce it you can execute the code (see attachment file).
> The bug is simple:
> After an invalid conversion, the automatic String -> JSON transformation used 
> to put a document into MongoDB collection, fail!
> Application flow:
> # First document can be convert to JSON, Mongodb create a document (correct)
> # Second document has an error, Mongodb cannot create a document (correct)
> # Third document can be convert to JSON but Mongodb cannot create a document 
> into collection because automatic conversion is broken!!!  (BUG)
> Kings regards



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11376) camel-cxf - Conduit configuration not possible in SpringBoot without xml

[Claus Ibsen (JIRA)]

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

Claus Ibsen updated CAMEL-11376:

Summary: camel-cxf - Conduit configuration not possible in SpringBoot 
without xml  (was: Conduit configuration not possible in SpringBoot without xml)

> camel-cxf - Conduit configuration not possible in SpringBoot without xml
> 
>
> Key: CAMEL-11376
> URL: https://issues.apache.org/jira/browse/CAMEL-11376
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-cxf, camel-cxfrs
>Affects Versions: 2.16.3
> Environment: Camel with SpringBoot
>Reporter: Sony Joseph
>Priority: Minor
>
> I am looking for an option to get away without an XML file for application 
> context in my project. But the element like http-conduit can only be added 
> with the support of an XML



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11425) Camel Olingo needs a way to dynamically set and receive HTTP headers

[Claus Ibsen (JIRA)]

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

Claus Ibsen resolved CAMEL-11425.
-
Resolution: Fixed
  Assignee: Claus Ibsen

> Camel Olingo needs a way to dynamically set and receive HTTP headers
> 
>
> Key: CAMEL-11425
> URL: https://issues.apache.org/jira/browse/CAMEL-11425
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-olingo2
>Affects Versions: 2.17.7, 2.19.0
>Reporter: Sean Haynes
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Our interface with SAP Netweaver Gateway requires that we request a CSRF 
> token and then pass that value to future calls associated with our 
> transaction.  The current design of the camel-olingo2 component only allows 
> us to set headers at component level.  This change will allow the user to set 
> headers at the endpoint level prior to calling the endpoint and receive the 
> response headers after endpoint is called.  I have already created a version 
> of the component that supports this change.  I will submit this change for 
> approval shortly...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-11545) Avoid double dot in enriched with default value in XML XSD

[JIRA]

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

Önder Sezgin resolved CAMEL-11545.
--
Resolution: Fixed

> Avoid double dot in enriched with default value in XML XSD
> --
>
> Key: CAMEL-11545
> URL: https://issues.apache.org/jira/browse/CAMEL-11545
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Reporter: Claus Ibsen
>Assignee: Önder Sezgin
> Fix For: 2.20.0
>
>
> For example
> {code}
> 
> {code}
> Notice the double dot when the default value is inserted.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11545) Avoid double dot in enriched with default value in XML XSD

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CAMEL-11545:


Github user onders86 closed the pull request at:

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


> Avoid double dot in enriched with default value in XML XSD
> --
>
> Key: CAMEL-11545
> URL: https://issues.apache.org/jira/browse/CAMEL-11545
> Project: Camel
>  Issue Type: Task
>  Components: build system
>Reporter: Claus Ibsen
>Assignee: Önder Sezgin
> Fix For: 2.20.0
>
>
> For example
> {code}
> 
> {code}
> Notice the double dot when the default value is inserted.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)