[jira] [Created] (CAMEL-13473) camel3 - build system - dataformats from camel-core no longer generated in readme files

2019-04-30 Thread Claus Ibsen (JIRA)
Claus Ibsen created CAMEL-13473:
---

 Summary: camel3 - build system - dataformats from camel-core no 
longer generated in readme files
 Key: CAMEL-13473
 URL: https://issues.apache.org/jira/browse/CAMEL-13473
 Project: Camel
  Issue Type: Task
Reporter: Claus Ibsen
 Fix For: 3.0.0, 3.0.0-M3


Likely because they were moved from camel-core to camel-base etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation

2019-04-30 Thread Claus Ibsen (JIRA)


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

Claus Ibsen updated CAMEL-13468:

Fix Version/s: 2.23.3
   2.24.0

> Exception tag is missing when Camel Java DSL is converted into XML using 
> dumpRouteAsXml() operation
> ---
>
> Key: CAMEL-13468
> URL: https://issues.apache.org/jira/browse/CAMEL-13468
> Project: Camel
>  Issue Type: Bug
>  Components: came-core
>Affects Versions: 2.22.4, 3.0.0-M1
>Reporter: Shailendra Kumar singh
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 2.24.0, 3.0.0-M3, 2.23.3
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Exception tag is missing when Camel Java DSL is converted into XML using 
> dumpRouteAsXml() operation
> #Java DSL route
> {code:java}
> public void configure() {
>   
> onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
>   .handled(true);
>   
> from("timer://foo?fixedRate=true=1=101").routeId("test")
>   .log("Hello World");
> }
> {code}
> #XML converted by dumpRouteAsXml() 
> operation(*java.lang.Exception* tag is missing)
> {code:java}
> 
> http://camel.apache.org/schema/spring; customId="true" 
> id="test">
>  uri="timer://foo?fixedRate=trueperiod=1repeatCount=101"/>
> 
> 
> 
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation

2019-04-30 Thread ASF GitHub Bot (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-13468?focusedWorklogId=235667=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235667
 ]

ASF GitHub Bot logged work on CAMEL-13468:
--

Author: ASF GitHub Bot
Created on: 01/May/19 05:25
Start Date: 01/May/19 05:25
Worklog Time Spent: 10m 
  Work Description: davsclaus commented on pull request #2895: 
[CAMEL-13468]Exception tag is missing when Camel Java DSL is converte…
URL: https://github.com/apache/camel/pull/2895
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 235667)
Time Spent: 40m  (was: 0.5h)

> Exception tag is missing when Camel Java DSL is converted into XML using 
> dumpRouteAsXml() operation
> ---
>
> Key: CAMEL-13468
> URL: https://issues.apache.org/jira/browse/CAMEL-13468
> Project: Camel
>  Issue Type: Bug
>  Components: came-core
>Affects Versions: 2.22.4, 3.0.0-M1
>Reporter: Shailendra Kumar singh
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Exception tag is missing when Camel Java DSL is converted into XML using 
> dumpRouteAsXml() operation
> #Java DSL route
> {code:java}
> public void configure() {
>   
> onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
>   .handled(true);
>   
> from("timer://foo?fixedRate=true=1=101").routeId("test")
>   .log("Hello World");
> }
> {code}
> #XML converted by dumpRouteAsXml() 
> operation(*java.lang.Exception* tag is missing)
> {code:java}
> 
> http://camel.apache.org/schema/spring; customId="true" 
> id="test">
>  uri="timer://foo?fixedRate=trueperiod=1repeatCount=101"/>
> 
> 
> 
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (CAMEL-12834) Failing Camel CDI tests for 1.2 & 2.0 profiles

2019-04-30 Thread Denis Istomin (JIRA)


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

Denis Istomin reassigned CAMEL-12834:
-

Assignee: Denis Istomin

> Failing Camel CDI tests for 1.2 & 2.0 profiles
> --
>
> Key: CAMEL-12834
> URL: https://issues.apache.org/jira/browse/CAMEL-12834
> Project: Camel
>  Issue Type: Test
>  Components: camel-cdi
>Reporter: James Netherton
>Assignee: Denis Istomin
>Priority: Major
>
> There are 2 failing tests when Camel CDI tests are run for any of the CDI 1.2 
> or 2.0 profiles:
> UnsatisfiedContextForEndpointInjectTest
> UriWithWrongContextTest
> Seems one of the expected error messages never occurs.
> I'm going to exclude them in the surefire plugin configuration until a fix is 
> available.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-13469) Move camel core classes that are not dependent on the model to camel-base

2019-04-30 Thread Guillaume Nodet (JIRA)


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

Guillaume Nodet resolved CAMEL-13469.
-
Resolution: Fixed

> Move camel core classes that are not dependent on the model to camel-base
> -
>
> Key: CAMEL-13469
> URL: https://issues.apache.org/jira/browse/CAMEL-13469
> Project: Camel
>  Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-13472) camel-box, add JWT authentication method

2019-04-30 Thread Jiri Ondrusek (JIRA)


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

Jiri Ondrusek commented on CAMEL-13472:
---

This improvement is probably already implemented in current box component. Once 
I validate it, this issue could be closed as "not a problem".

> camel-box, add JWT authentication method
> 
>
> Key: CAMEL-13472
> URL: https://issues.apache.org/jira/browse/CAMEL-13472
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-box
>Affects Versions: 3.0.0
>Reporter: Jiri Ondrusek
>Priority: Major
>
> Camel-box component is currently using OAuth mechanism for authentication [1].
> But it should be possible to authenticate also with JWT mechanism [2].
> It seems that it should be possible to enhance camel-box component to use 
> either OAuth [1] and JWT [2] mechanisms.
> Usage of JWT [2] authentication mechanism would allow box component to use 
> some more API calls (e.g. to create app users) and to allow some integration 
> tests, which are currently ignored.
> If both mechanisms are supported, users could decide which one to use.
> [1] https://developer.box.com/docs/authenticate-with-oauth-2
> [2] https://developer.box.com/docs/authenticate-with-jwt



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation

2019-04-30 Thread ASF GitHub Bot (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-13468?focusedWorklogId=235340=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235340
 ]

ASF GitHub Bot logged work on CAMEL-13468:
--

Author: ASF GitHub Bot
Created on: 30/Apr/19 14:58
Start Date: 30/Apr/19 14:58
Worklog Time Spent: 10m 
  Work Description: davsclaus commented on pull request #2895: 
[CAMEL-13468]Exception tag is missing when Camel Java DSL is converte…
URL: https://github.com/apache/camel/pull/2895
 
 
   …d into XML using dumpRouteAsXml() operation
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 235340)
Time Spent: 0.5h  (was: 20m)

> Exception tag is missing when Camel Java DSL is converted into XML using 
> dumpRouteAsXml() operation
> ---
>
> Key: CAMEL-13468
> URL: https://issues.apache.org/jira/browse/CAMEL-13468
> Project: Camel
>  Issue Type: Bug
>  Components: came-core
>Affects Versions: 2.22.4, 3.0.0-M1
>Reporter: Shailendra Kumar singh
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Exception tag is missing when Camel Java DSL is converted into XML using 
> dumpRouteAsXml() operation
> #Java DSL route
> {code:java}
> public void configure() {
>   
> onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
>   .handled(true);
>   
> from("timer://foo?fixedRate=true=1=101").routeId("test")
>   .log("Hello World");
> }
> {code}
> #XML converted by dumpRouteAsXml() 
> operation(*java.lang.Exception* tag is missing)
> {code:java}
> 
> http://camel.apache.org/schema/spring; customId="true" 
> id="test">
>  uri="timer://foo?fixedRate=trueperiod=1repeatCount=101"/>
> 
> 
> 
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (CAMEL-13234) Can we get rid of weld2

2019-04-30 Thread Denis Istomin (JIRA)


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

Denis Istomin reassigned CAMEL-13234:
-

Assignee: Denis Istomin

> Can we get rid of weld2
> ---
>
> Key: CAMEL-13234
> URL: https://issues.apache.org/jira/browse/CAMEL-13234
> Project: Camel
>  Issue Type: Task
>  Components: camel-cdi
>Reporter: Claus Ibsen
>Assignee: Denis Istomin
>Priority: Major
> Fix For: 3.0.0
>
>
> camel-cdi is using weld3. And we may have some examples and other bits that 
> uses weld2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name

2019-04-30 Thread ASF GitHub Bot (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-13465?focusedWorklogId=235284=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235284
 ]

ASF GitHub Bot logged work on CAMEL-13465:
--

Author: ASF GitHub Bot
Created on: 30/Apr/19 13:36
Start Date: 30/Apr/19 13:36
Worklog Time Spent: 10m 
  Work Description: oscerd commented on pull request #2892: [CAMEL-13465] 
Camel-box, BoxGroupMembership.Info getGroupMembershipIn…
URL: https://github.com/apache/camel/pull/2892
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 235284)
Time Spent: 20m  (was: 10m)

> Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String 
> groupMemebershipId) typo in argument name
> --
>
> Key: CAMEL-13465
> URL: https://issues.apache.org/jira/browse/CAMEL-13465
> Project: Camel
>  Issue Type: Bug
>  Components: camel-box
>Reporter: Jiri Ondrusek
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> There is a typo in argument of API method BoxGroupMembership.Info 
> getGroupMembershipInfo(String groupMemebershipId). >>>memEbership<<<
> (see 
> https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273)
> It forces users to use this "wrong" parameter in their code.
> Typo should be fixed, but it also has to be consistent in tests



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones

2019-04-30 Thread ASF GitHub Bot (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-13467?focusedWorklogId=235283=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235283
 ]

ASF GitHub Bot logged work on CAMEL-13467:
--

Author: ASF GitHub Bot
Created on: 30/Apr/19 13:36
Start Date: 30/Apr/19 13:36
Worklog Time Spent: 10m 
  Work Description: oscerd commented on pull request #2894: [CAMEL-13467] 
Camel-box, replace deprecated calls with correct ones
URL: https://github.com/apache/camel/pull/2894
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 235283)
Time Spent: 20m  (was: 10m)

> Camel-box, replace deprecated calls with  correct ones
> --
>
> Key: CAMEL-13467
> URL: https://issues.apache.org/jira/browse/CAMEL-13467
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-box
>Reporter: Jiri Ondrusek
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of 
> them could be replaced by the correct calls.
> {quote}
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
> Warning:(354, 24) java: moveFolderToUser(java.lang.String) in 
> com.box.sdk.BoxUser has been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
> Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has 
> been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
> Warning:(218, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(220, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(223, 21) java: uploadVersion(java.io.InputStream) in 
> com.box.sdk.BoxFile has been deprecated
> {quote}
> Inspect all 5 occurrences of deprecated calls and fix them if possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones

2019-04-30 Thread Andrea Cosentino (JIRA)


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

Andrea Cosentino reassigned CAMEL-13467:


Assignee: Andrea Cosentino

> Camel-box, replace deprecated calls with  correct ones
> --
>
> Key: CAMEL-13467
> URL: https://issues.apache.org/jira/browse/CAMEL-13467
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-box
>Reporter: Jiri Ondrusek
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of 
> them could be replaced by the correct calls.
> {quote}
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
> Warning:(354, 24) java: moveFolderToUser(java.lang.String) in 
> com.box.sdk.BoxUser has been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
> Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has 
> been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
> Warning:(218, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(220, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(223, 21) java: uploadVersion(java.io.InputStream) in 
> com.box.sdk.BoxFile has been deprecated
> {quote}
> Inspect all 5 occurrences of deprecated calls and fix them if possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones

2019-04-30 Thread Andrea Cosentino (JIRA)


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

Andrea Cosentino updated CAMEL-13467:
-
Affects Version/s: (was: 3.0.0)

> Camel-box, replace deprecated calls with  correct ones
> --
>
> Key: CAMEL-13467
> URL: https://issues.apache.org/jira/browse/CAMEL-13467
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-box
>Reporter: Jiri Ondrusek
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of 
> them could be replaced by the correct calls.
> {quote}
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
> Warning:(354, 24) java: moveFolderToUser(java.lang.String) in 
> com.box.sdk.BoxUser has been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
> Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has 
> been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
> Warning:(218, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(220, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(223, 21) java: uploadVersion(java.io.InputStream) in 
> com.box.sdk.BoxFile has been deprecated
> {quote}
> Inspect all 5 occurrences of deprecated calls and fix them if possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name

2019-04-30 Thread Andrea Cosentino (JIRA)


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

Andrea Cosentino resolved CAMEL-13465.
--
Resolution: Fixed

> Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String 
> groupMemebershipId) typo in argument name
> --
>
> Key: CAMEL-13465
> URL: https://issues.apache.org/jira/browse/CAMEL-13465
> Project: Camel
>  Issue Type: Bug
>  Components: camel-box
>Reporter: Jiri Ondrusek
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a typo in argument of API method BoxGroupMembership.Info 
> getGroupMembershipInfo(String groupMemebershipId). >>>memEbership<<<
> (see 
> https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273)
> It forces users to use this "wrong" parameter in their code.
> Typo should be fixed, but it also has to be consistent in tests



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones

2019-04-30 Thread Andrea Cosentino (JIRA)


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

Andrea Cosentino resolved CAMEL-13467.
--
Resolution: Fixed

> Camel-box, replace deprecated calls with  correct ones
> --
>
> Key: CAMEL-13467
> URL: https://issues.apache.org/jira/browse/CAMEL-13467
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-box
>Reporter: Jiri Ondrusek
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of 
> them could be replaced by the correct calls.
> {quote}
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
> Warning:(354, 24) java: moveFolderToUser(java.lang.String) in 
> com.box.sdk.BoxUser has been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
> Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has 
> been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
> Warning:(218, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(220, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(223, 21) java: uploadVersion(java.io.InputStream) in 
> com.box.sdk.BoxFile has been deprecated
> {quote}
> Inspect all 5 occurrences of deprecated calls and fix them if possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones

2019-04-30 Thread Andrea Cosentino (JIRA)


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

Andrea Cosentino updated CAMEL-13467:
-
Fix Version/s: 3.0.0-M3
   3.0.0

> Camel-box, replace deprecated calls with  correct ones
> --
>
> Key: CAMEL-13467
> URL: https://issues.apache.org/jira/browse/CAMEL-13467
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-box
>Reporter: Jiri Ondrusek
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of 
> them could be replaced by the correct calls.
> {quote}
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
> Warning:(354, 24) java: moveFolderToUser(java.lang.String) in 
> com.box.sdk.BoxUser has been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
> Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has 
> been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
> Warning:(218, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(220, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(223, 21) java: uploadVersion(java.io.InputStream) in 
> com.box.sdk.BoxFile has been deprecated
> {quote}
> Inspect all 5 occurrences of deprecated calls and fix them if possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name

2019-04-30 Thread Andrea Cosentino (JIRA)


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

Andrea Cosentino updated CAMEL-13465:
-
Fix Version/s: 3.0.0-M3
   3.0.0

> Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String 
> groupMemebershipId) typo in argument name
> --
>
> Key: CAMEL-13465
> URL: https://issues.apache.org/jira/browse/CAMEL-13465
> Project: Camel
>  Issue Type: Bug
>  Components: camel-box
>Affects Versions: 3.0.0
>Reporter: Jiri Ondrusek
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a typo in argument of API method BoxGroupMembership.Info 
> getGroupMembershipInfo(String groupMemebershipId). >>>memEbership<<<
> (see 
> https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273)
> It forces users to use this "wrong" parameter in their code.
> Typo should be fixed, but it also has to be consistent in tests



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name

2019-04-30 Thread Andrea Cosentino (JIRA)


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

Andrea Cosentino reassigned CAMEL-13465:


Assignee: Andrea Cosentino

> Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String 
> groupMemebershipId) typo in argument name
> --
>
> Key: CAMEL-13465
> URL: https://issues.apache.org/jira/browse/CAMEL-13465
> Project: Camel
>  Issue Type: Bug
>  Components: camel-box
>Reporter: Jiri Ondrusek
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a typo in argument of API method BoxGroupMembership.Info 
> getGroupMembershipInfo(String groupMemebershipId). >>>memEbership<<<
> (see 
> https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273)
> It forces users to use this "wrong" parameter in their code.
> Typo should be fixed, but it also has to be consistent in tests



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name

2019-04-30 Thread Andrea Cosentino (JIRA)


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

Andrea Cosentino updated CAMEL-13465:
-
Affects Version/s: (was: 3.0.0)

> Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String 
> groupMemebershipId) typo in argument name
> --
>
> Key: CAMEL-13465
> URL: https://issues.apache.org/jira/browse/CAMEL-13465
> Project: Camel
>  Issue Type: Bug
>  Components: camel-box
>Reporter: Jiri Ondrusek
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a typo in argument of API method BoxGroupMembership.Info 
> getGroupMembershipInfo(String groupMemebershipId). >>>memEbership<<<
> (see 
> https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273)
> It forces users to use this "wrong" parameter in their code.
> Typo should be fixed, but it also has to be consistent in tests



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-13472) camel-box, add JWT authentication method

2019-04-30 Thread Jiri Ondrusek (JIRA)


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

Jiri Ondrusek commented on CAMEL-13472:
---

I'm working on this issue

> camel-box, add JWT authentication method
> 
>
> Key: CAMEL-13472
> URL: https://issues.apache.org/jira/browse/CAMEL-13472
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-box
>Affects Versions: 3.0.0
>Reporter: Jiri Ondrusek
>Priority: Major
>
> Camel-box component is currently using OAuth mechanism for authentication [1].
> But it should be possible to authenticate also with JWT mechanism [2].
> It seems that it should be possible to enhance camel-box component to use 
> either OAuth [1] and JWT [2] mechanisms.
> Usage of JWT [2] authentication mechanism would allow box component to use 
> some more API calls (e.g. to create app users) and to allow some integration 
> tests, which are currently ignored.
> If both mechanisms are supported, users could decide which one to use.
> [1] https://developer.box.com/docs/authenticate-with-oauth-2
> [2] https://developer.box.com/docs/authenticate-with-jwt



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-13472) camel-box, add JWT authentication method

2019-04-30 Thread Jiri Ondrusek (JIRA)
Jiri Ondrusek created CAMEL-13472:
-

 Summary: camel-box, add JWT authentication method
 Key: CAMEL-13472
 URL: https://issues.apache.org/jira/browse/CAMEL-13472
 Project: Camel
  Issue Type: Improvement
  Components: camel-box
Affects Versions: 3.0.0
Reporter: Jiri Ondrusek


Camel-box component is currently using OAuth mechanism for authentication [1].
But it should be possible to authenticate also with JWT mechanism [2].

It seems that it should be possible to enhance camel-box component to use 
either OAuth [1] and JWT [2] mechanisms.

Usage of JWT [2] authentication mechanism would allow box component to use some 
more API calls (e.g. to create app users) and to allow some integration tests, 
which are currently ignored.

If both mechanisms are supported, users could decide which one to use.

[1] https://developer.box.com/docs/authenticate-with-oauth-2
[2] https://developer.box.com/docs/authenticate-with-jwt




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-13144) Move bean component out of camel-core

2019-04-30 Thread Claus Ibsen (JIRA)


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

Claus Ibsen resolved CAMEL-13144.
-
   Resolution: Fixed
Fix Version/s: 3.0.0-M3

> Move bean component out of camel-core
> -
>
> Key: CAMEL-13144
> URL: https://issues.apache.org/jira/browse/CAMEL-13144
> Project: Camel
>  Issue Type: Task
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> This component is a bit more challenging as bean component is also used for 
> method call language and has support for using language annotations. For 
> example also for @XPath etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-13471) Support TCP + TLS in Camel CoAP

2019-04-30 Thread Colm O hEigeartaigh (JIRA)
Colm O hEigeartaigh created CAMEL-13471:
---

 Summary: Support TCP + TLS in Camel CoAP
 Key: CAMEL-13471
 URL: https://issues.apache.org/jira/browse/CAMEL-13471
 Project: Camel
  Issue Type: Improvement
  Components: camel-coap
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 3.0.0


This task is to support TCP + TLS in Camel CoAP as per 
https://tools.ietf.org/html/rfc8323



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones

2019-04-30 Thread ASF GitHub Bot (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-13467?focusedWorklogId=235262=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235262
 ]

ASF GitHub Bot logged work on CAMEL-13467:
--

Author: ASF GitHub Bot
Created on: 30/Apr/19 12:34
Start Date: 30/Apr/19 12:34
Worklog Time Spent: 10m 
  Work Description: JiriOndrusek commented on pull request #2894: 
[CAMEL-13467] Camel-box, replace deprecated calls with correct ones
URL: https://github.com/apache/camel/pull/2894
 
 
   Issue: https://issues.apache.org/jira/browse/CAMEL-13467
   
   Change of deprecated APIs for the correct ones.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 235262)
Time Spent: 10m
Remaining Estimate: 0h

> Camel-box, replace deprecated calls with  correct ones
> --
>
> Key: CAMEL-13467
> URL: https://issues.apache.org/jira/browse/CAMEL-13467
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-box
>Affects Versions: 3.0.0
>Reporter: Jiri Ondrusek
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of 
> them could be replaced by the correct calls.
> {quote}
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
> Warning:(354, 24) java: moveFolderToUser(java.lang.String) in 
> com.box.sdk.BoxUser has been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
> Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has 
> been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
> Warning:(218, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(220, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(223, 21) java: uploadVersion(java.io.InputStream) in 
> com.box.sdk.BoxFile has been deprecated
> {quote}
> Inspect all 5 occurrences of deprecated calls and fix them if possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones

2019-04-30 Thread Jiri Ondrusek (JIRA)


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

Jiri Ondrusek commented on CAMEL-13467:
---

PR: https://github.com/apache/camel/pull/2894

> Camel-box, replace deprecated calls with  correct ones
> --
>
> Key: CAMEL-13467
> URL: https://issues.apache.org/jira/browse/CAMEL-13467
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-box
>Affects Versions: 3.0.0
>Reporter: Jiri Ondrusek
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of 
> them could be replaced by the correct calls.
> {quote}
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
> Warning:(354, 24) java: moveFolderToUser(java.lang.String) in 
> com.box.sdk.BoxUser has been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
> Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has 
> been deprecated
> * 
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
> Warning:(218, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(220, 25) java: 
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
>  in com.box.sdk.BoxFile has been deprecated
> Warning:(223, 21) java: uploadVersion(java.io.InputStream) in 
> com.box.sdk.BoxFile has been deprecated
> {quote}
> Inspect all 5 occurrences of deprecated calls and fix them if possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-13470) Publish security advisories

2019-04-30 Thread Zoran Regvart (JIRA)
Zoran Regvart created CAMEL-13470:
-

 Summary: Publish security advisories
 Key: CAMEL-13470
 URL: https://issues.apache.org/jira/browse/CAMEL-13470
 Project: Camel
  Issue Type: Sub-task
  Components: website
Reporter: Zoran Regvart
Assignee: Zoran Regvart


We have a number of [security 
advisories|https://github.com/apache/camel/tree/master/docs/user-manual/en/security-advisories]
 that we need to publish and are not currently publishing on the new website.
We should create a Hugo archetype and copy over the current advisories to the 
{{camel-website}} git repository.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-12764) camel-http4: basic auth no longer working when used in combination with a dynamic to

2019-04-30 Thread Pascal Schumacher (JIRA)


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

Pascal Schumacher updated CAMEL-12764:
--
Fix Version/s: (was: 2.23.2)
   2.24.0

> camel-http4: basic auth no longer working when used in combination with a 
> dynamic to
> 
>
> Key: CAMEL-12764
> URL: https://issues.apache.org/jira/browse/CAMEL-12764
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http4
>Affects Versions: 2.22.0, 2.22.1
>Reporter: Pascal Schumacher
>Priority: Major
>  Labels: regresion
> Fix For: 2.24.0
>
>
> After upgrading a Spring Boot Project from Camel 2.21.1 to Camel 2.22.0 basic 
> authentication of the http4 component stopped working when it is used in 
> combination with a dynamic to.
> My (slightly simplified) route:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE, 
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> 
> .toD("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/${exchangeProperty.my_id}");
> {code}
> When I change the route and remove the dynamic to everything works fine again:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE, 
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> .setHeader(Exchange.HTTP_PATH, exchangeProperty("my_id"))
> .to("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/");
> {code}
> Maybe this regression was caused by CAMEL-12462?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12764) camel-http4: basic auth no longer working when used in combination with a dynamic to

2019-04-30 Thread Pascal Schumacher (JIRA)


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

Pascal Schumacher commented on CAMEL-12764:
---

Sorry I messed up, it still does not work with Camel 2.23.2.

> camel-http4: basic auth no longer working when used in combination with a 
> dynamic to
> 
>
> Key: CAMEL-12764
> URL: https://issues.apache.org/jira/browse/CAMEL-12764
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http4
>Affects Versions: 2.22.0, 2.22.1, 2.23.2
>Reporter: Pascal Schumacher
>Priority: Major
>  Labels: regresion
> Fix For: 2.24.0
>
>
> After upgrading a Spring Boot Project from Camel 2.21.1 to Camel 2.22.0 basic 
> authentication of the http4 component stopped working when it is used in 
> combination with a dynamic to.
> My (slightly simplified) route:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE, 
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> 
> .toD("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/${exchangeProperty.my_id}");
> {code}
> When I change the route and remove the dynamic to everything works fine again:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE, 
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> .setHeader(Exchange.HTTP_PATH, exchangeProperty("my_id"))
> .to("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/");
> {code}
> Maybe this regression was caused by CAMEL-12462?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-12764) camel-http4: basic auth no longer working when used in combination with a dynamic to

2019-04-30 Thread Pascal Schumacher (JIRA)


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

Pascal Schumacher updated CAMEL-12764:
--
Affects Version/s: 2.23.2

> camel-http4: basic auth no longer working when used in combination with a 
> dynamic to
> 
>
> Key: CAMEL-12764
> URL: https://issues.apache.org/jira/browse/CAMEL-12764
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http4
>Affects Versions: 2.22.0, 2.22.1, 2.23.2
>Reporter: Pascal Schumacher
>Priority: Major
>  Labels: regresion
> Fix For: 2.24.0
>
>
> After upgrading a Spring Boot Project from Camel 2.21.1 to Camel 2.22.0 basic 
> authentication of the http4 component stopped working when it is used in 
> combination with a dynamic to.
> My (slightly simplified) route:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE, 
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> 
> .toD("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/${exchangeProperty.my_id}");
> {code}
> When I change the route and remove the dynamic to everything works fine again:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE, 
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> .setHeader(Exchange.HTTP_PATH, exchangeProperty("my_id"))
> .to("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/");
> {code}
> Maybe this regression was caused by CAMEL-12462?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Reopened] (CAMEL-12764) camel-http4: basic auth no longer working when used in combination with a dynamic to

2019-04-30 Thread Pascal Schumacher (JIRA)


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

Pascal Schumacher reopened CAMEL-12764:
---

> camel-http4: basic auth no longer working when used in combination with a 
> dynamic to
> 
>
> Key: CAMEL-12764
> URL: https://issues.apache.org/jira/browse/CAMEL-12764
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http4
>Affects Versions: 2.22.0, 2.22.1
>Reporter: Pascal Schumacher
>Priority: Major
>  Labels: regresion
> Fix For: 2.23.2
>
>
> After upgrading a Spring Boot Project from Camel 2.21.1 to Camel 2.22.0 basic 
> authentication of the http4 component stopped working when it is used in 
> combination with a dynamic to.
> My (slightly simplified) route:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE, 
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> 
> .toD("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/${exchangeProperty.my_id}");
> {code}
> When I change the route and remove the dynamic to everything works fine again:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE, 
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> .setHeader(Exchange.HTTP_PATH, exchangeProperty("my_id"))
> .to("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/");
> {code}
> Maybe this regression was caused by CAMEL-12462?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-13464) Problem with Olingo4 and authenticated metadata

2019-04-30 Thread Dmitry Volodin (JIRA)


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

Dmitry Volodin commented on CAMEL-13464:


[~r.sch...@topdesk.com], are you working on PR for fix or I can add your patch 
to upstream?

> Problem with Olingo4 and authenticated metadata
> ---
>
> Key: CAMEL-13464
> URL: https://issues.apache.org/jira/browse/CAMEL-13464
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.23.2
>Reporter: Remco Schoen
>Priority: Minor
> Attachments: headers_fix.diff
>
>
> I'm currently working with the Olingo4 component for linking with Microsoft 
> Dynamics 365 CRM. This OData feed requires authentication to get the 
> metadata. As I have to refresh the Access Token for authenticating I can not 
> add it to the configuration, but I'm using the 
> CamelOlingo4.endpointHttpHeaders header for this. But when the component is 
> retrieving the metadata it is ignoring the header and it is not able to 
> authenticate.
> If I add the headers to the get metadata request it works.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-9589) Apache Artemis example with Camel

2019-04-30 Thread Claus Ibsen (JIRA)


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

Claus Ibsen resolved CAMEL-9589.

   Resolution: Fixed
 Assignee: Claus Ibsen
Fix Version/s: 3.0.0-M3
   3.0.0

> Apache Artemis example with Camel
> -
>
> Key: CAMEL-9589
> URL: https://issues.apache.org/jira/browse/CAMEL-9589
> Project: Camel
>  Issue Type: New Feature
>  Components: examples
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We should have an example that uses Camel with ActiveMQ Artemis as the 
> broker. For example we have the widget-gadget that uses regular ActiveMQ. We 
> could create an example with something similar or something else.
> The idea is to show Camel as a client connecting to a remote Artemis broker.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-13402) Update to Californium 2.0.x and support DTLS

2019-04-30 Thread Andrea Cosentino (JIRA)


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

Andrea Cosentino resolved CAMEL-13402.
--
Resolution: Fixed

> Update to Californium 2.0.x and support DTLS
> 
>
> Key: CAMEL-13402
> URL: https://issues.apache.org/jira/browse/CAMEL-13402
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-coap
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> This task is to update to Californium 2.0.x and support DTLS in the 
> camel-coap component. Currently we only support plain UDP and not UDP / TLS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-13402) Update to Californium 2.0.x and support DTLS

2019-04-30 Thread Andrea Cosentino (JIRA)


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

Andrea Cosentino updated CAMEL-13402:
-
Fix Version/s: 3.0.0-M3

> Update to Californium 2.0.x and support DTLS
> 
>
> Key: CAMEL-13402
> URL: https://issues.apache.org/jira/browse/CAMEL-13402
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-coap
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>
> This task is to update to Californium 2.0.x and support DTLS in the 
> camel-coap component. Currently we only support plain UDP and not UDP / TLS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation

2019-04-30 Thread Claus Ibsen (JIRA)


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

Claus Ibsen commented on CAMEL-13468:
-

Okay working on backporting this to 2.x

> Exception tag is missing when Camel Java DSL is converted into XML using 
> dumpRouteAsXml() operation
> ---
>
> Key: CAMEL-13468
> URL: https://issues.apache.org/jira/browse/CAMEL-13468
> Project: Camel
>  Issue Type: Bug
>  Components: came-core
>Affects Versions: 2.22.4, 3.0.0-M1
>Reporter: Shailendra Kumar singh
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0-M3
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Exception tag is missing when Camel Java DSL is converted into XML using 
> dumpRouteAsXml() operation
> #Java DSL route
> {code:java}
> public void configure() {
>   
> onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
>   .handled(true);
>   
> from("timer://foo?fixedRate=true=1=101").routeId("test")
>   .log("Hello World");
> }
> {code}
> #XML converted by dumpRouteAsXml() 
> operation(*java.lang.Exception* tag is missing)
> {code:java}
> 
> http://camel.apache.org/schema/spring; customId="true" 
> id="test">
>  uri="timer://foo?fixedRate=trueperiod=1repeatCount=101"/>
> 
> 
> 
> 
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-13469) Move camel core classes that are not dependent on the model to camel-base

2019-04-30 Thread Guillaume Nodet (JIRA)
Guillaume Nodet created CAMEL-13469:
---

 Summary: Move camel core classes that are not dependent on the 
model to camel-base
 Key: CAMEL-13469
 URL: https://issues.apache.org/jira/browse/CAMEL-13469
 Project: Camel
  Issue Type: Improvement
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: 3.0.0, 3.0.0-M3






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work stopped] (CAMEL-13290) Reactive camel-core engine

2019-04-30 Thread Guillaume Nodet (JIRA)


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

Work on CAMEL-13290 stopped by Guillaume Nodet.
---
> Reactive camel-core engine
> --
>
> Key: CAMEL-13290
> URL: https://issues.apache.org/jira/browse/CAMEL-13290
> Project: Camel
>  Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.0.0-M2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-13450) Introduce reifiers for DataFormat

2019-04-30 Thread Guillaume Nodet (JIRA)


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

Guillaume Nodet resolved CAMEL-13450.
-
Resolution: Fixed

> Introduce reifiers for DataFormat
> -
>
> Key: CAMEL-13450
> URL: https://issues.apache.org/jira/browse/CAMEL-13450
> Project: Camel
>  Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)