[jira] [Commented] (CAMEL-13964) Create camel-debezium examples

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino commented on CAMEL-13964:
--

You now have permission to self-assign issues

> Create camel-debezium examples
> --
>
> Key: CAMEL-13964
> URL: https://issues.apache.org/jira/browse/CAMEL-13964
> Project: Camel
>  Issue Type: Task
>  Components: camel-debezium
>Reporter: Omar Al-Safi
>Assignee: Omar Al-Safi
>Priority: Minor
> Fix For: 3.0.0.RC2
>
>
> Per the title, add couple of useful examples for camel-debezium that can help 
> the users to use this components



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Assigned] (CAMEL-13964) Create camel-debezium examples

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino reassigned CAMEL-13964:


Assignee: Omar Al-Safi

> Create camel-debezium examples
> --
>
> Key: CAMEL-13964
> URL: https://issues.apache.org/jira/browse/CAMEL-13964
> Project: Camel
>  Issue Type: Task
>  Components: camel-debezium
>Reporter: Omar Al-Safi
>Assignee: Omar Al-Safi
>Priority: Minor
> Fix For: 3.0.0.RC2
>
>
> Per the title, add couple of useful examples for camel-debezium that can help 
> the users to use this components



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Work logged] (CAMEL-13916) website - Add migration guide page

2019-09-10 Thread ASF GitHub Bot (Jira)


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

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

Author: ASF GitHub Bot
Created on: 10/Sep/19 21:31
Start Date: 10/Sep/19 21:31
Worklog Time Spent: 10m 
  Work Description: oscerd commented on pull request #3159: CAMEL-13916: 
website - Add migration guide page
URL: https://github.com/apache/camel/pull/3159
 
 
   
 

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: 310136)
Time Spent: 20m  (was: 10m)

> website - Add migration guide page
> --
>
> Key: CAMEL-13916
> URL: https://issues.apache.org/jira/browse/CAMEL-13916
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Claus Ibsen
>Priority: Major
>  Labels: help-wanted
> Fix For: 3.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We need to have the migration guide on the website



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Work logged] (CAMEL-13916) website - Add migration guide page

2019-09-10 Thread ASF GitHub Bot (Jira)


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

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

Author: ASF GitHub Bot
Created on: 10/Sep/19 21:29
Start Date: 10/Sep/19 21:29
Worklog Time Spent: 10m 
  Work Description: alexkieling commented on pull request #3159: 
CAMEL-13916: website - Add migration guide page
URL: https://github.com/apache/camel/pull/3159
 
 
   Convert migration guide do AsciiDoc and move it to 
docs/user-manual/modules/ROOT/pages/camel-3-migration-guide.adoc
 

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: 310133)
Remaining Estimate: 0h
Time Spent: 10m

> website - Add migration guide page
> --
>
> Key: CAMEL-13916
> URL: https://issues.apache.org/jira/browse/CAMEL-13916
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Claus Ibsen
>Priority: Major
>  Labels: help-wanted
> Fix For: 3.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We need to have the migration guide on the website



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (CAMEL-13964) Create camel-debezium examples

2019-09-10 Thread Omar Al-Safi (Jira)


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

Omar Al-Safi commented on CAMEL-13964:
--

I will be working on this. However, [~acosentino] do you think if it makes 
sense to have the permission to self assign since there are also other tickets 
I'd like to work on? :) 

> Create camel-debezium examples
> --
>
> Key: CAMEL-13964
> URL: https://issues.apache.org/jira/browse/CAMEL-13964
> Project: Camel
>  Issue Type: Task
>  Components: camel-debezium
>Reporter: Omar Al-Safi
>Priority: Minor
> Fix For: 3.0.0.RC2
>
>
> Per the title, add couple of useful examples for camel-debezium that can help 
> the users to use this components



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (CAMEL-13964) Create camel-debezium examples

2019-09-10 Thread Omar Al-Safi (Jira)
Omar Al-Safi created CAMEL-13964:


 Summary: Create camel-debezium examples
 Key: CAMEL-13964
 URL: https://issues.apache.org/jira/browse/CAMEL-13964
 Project: Camel
  Issue Type: Task
  Components: camel-debezium
Reporter: Omar Al-Safi
 Fix For: 3.0.0.RC2


Per the title, add couple of useful examples for camel-debezium that can help 
the users to use this components



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (CAMEL-13963) Netty-HTTP in proxy mode should support POST method

2019-09-10 Thread Zoran Regvart (Jira)


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

Zoran Regvart resolved CAMEL-13963.
---
Resolution: Fixed

The DefaultNettyHttpBinding is now aware of the HTTP proxy mode and doesn't try 
to interfere with the request too much.

> Netty-HTTP in proxy mode should support POST method
> ---
>
> Key: CAMEL-13963
> URL: https://issues.apache.org/jira/browse/CAMEL-13963
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 3.0.0.RC1
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0.RC2
>
>
> Seems that the DefaultNettyHttpBinding might interfere and try to parse the 
> HTTP body preventing efficient buffer transfer between client request and the 
> origin service.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (CAMEL-13963) Netty-HTTP in proxy mode should support POST method

2019-09-10 Thread Zoran Regvart (Jira)
Zoran Regvart created CAMEL-13963:
-

 Summary: Netty-HTTP in proxy mode should support POST method
 Key: CAMEL-13963
 URL: https://issues.apache.org/jira/browse/CAMEL-13963
 Project: Camel
  Issue Type: Improvement
Affects Versions: 3.0.0.RC1
Reporter: Zoran Regvart
Assignee: Zoran Regvart
 Fix For: 3.0.0.RC2


Seems that the DefaultNettyHttpBinding might interfere and try to parse the 
HTTP body preventing efficient buffer transfer between client request and the 
origin service.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (CAMEL-13962) OgnlHelper.splitOgnl not able to handle Regex properly

2019-09-10 Thread Jira


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

Michael Pätzold updated CAMEL-13962:

Priority: Minor  (was: Major)

> OgnlHelper.splitOgnl not able to handle Regex properly
> --
>
> Key: CAMEL-13962
> URL: https://issues.apache.org/jira/browse/CAMEL-13962
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.24.1, 3.0.0.RC1
>Reporter: Michael Pätzold
>Priority: Minor
>
> The splitOgnl method cannot properly handle an expression if it contains 
> numerous paranthesis brackets and dots what is very likely in case you want 
> to use regular expressions.
> The following examples tries to extract a specific cookie value from the 
> cookie string that's containes within the headers:
> {code:java}
> @Test
> public void splitOgnlWithRegexInMethod() {
> String ognl = 
> "header.cookie.replaceFirst(\".*;?iwanttoknow=([^;]+);?.*\", \"$1\")";
> assertFalse(OgnlHelper.isInvalidValidOgnlExpression(ognl));
> assertTrue(OgnlHelper.isValidOgnlExpression(ognl));
> List strings = OgnlHelper.splitOgnl(ognl);
> assertEquals(3, strings.size());
> assertEquals("header", strings.get(0));
> assertEquals(".cookie", strings.get(1));
> assertEquals(".replaceFirst(\".*;?iwanttoknow=([^;]+);?.*\", 
> \"$1\")", strings.get(2));
> }
> {code}
> The test fails using the current code base since the regular expression 
> itself is split at the first dot after the first closing paranthesis bracket.
> If you'll agree that this is a bug I can come up with a possible solution 
> that takes the amount of opening/closing brackets into account via PR.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (CAMEL-13962) OgnlHelper.splitOgnl not able to handle Regex properly

2019-09-10 Thread Jira
Michael Pätzold created CAMEL-13962:
---

 Summary: OgnlHelper.splitOgnl not able to handle Regex properly
 Key: CAMEL-13962
 URL: https://issues.apache.org/jira/browse/CAMEL-13962
 Project: Camel
  Issue Type: Bug
  Components: camel-core
Affects Versions: 3.0.0.RC1, 2.24.1
Reporter: Michael Pätzold


The splitOgnl method cannot properly handle an expression if it contains 
numerous paranthesis brackets and dots what is very likely in case you want to 
use regular expressions.

The following examples tries to extract a specific cookie value from the cookie 
string that's containes within the headers:

{code:java}
@Test
public void splitOgnlWithRegexInMethod() {
String ognl = 
"header.cookie.replaceFirst(\".*;?iwanttoknow=([^;]+);?.*\", \"$1\")";
assertFalse(OgnlHelper.isInvalidValidOgnlExpression(ognl));
assertTrue(OgnlHelper.isValidOgnlExpression(ognl));

List strings = OgnlHelper.splitOgnl(ognl);
assertEquals(3, strings.size());
assertEquals("header", strings.get(0));
assertEquals(".cookie", strings.get(1));
assertEquals(".replaceFirst(\".*;?iwanttoknow=([^;]+);?.*\", \"$1\")", 
strings.get(2));
}
{code}

The test fails using the current code base since the regular expression itself 
is split at the first dot after the first closing paranthesis bracket.

If you'll agree that this is a bug I can come up with a possible solution that 
takes the amount of opening/closing brackets into account via PR.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (CAMEL-13961) Reconsider default for xslt:allowStAX

2019-09-10 Thread Thomas Diesler (Jira)


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

Thomas Diesler updated CAMEL-13961:
---
Component/s: camel-xslt

> Reconsider default for xslt:allowStAX
> -
>
> Key: CAMEL-13961
> URL: https://issues.apache.org/jira/browse/CAMEL-13961
> Project: Camel
>  Issue Type: Bug
>  Components: camel-xslt
>Reporter: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0
>
>
> This is currently set to true. However, Xalan (which the default XSLT 
> processor for most) cannot handle StAXSource
> {code}
> Caused by: javax.xml.transform.TransformerException: 
> javax.xml.transform.TransformerException: org.apache.xml.dtm.DTMException: 
> Not supported: javax.xml.transform.stax.StAXSource@6a35603
>   at 
> org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:642)
>   at 
> org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:303)
>   at 
> org.apache.camel.component.xslt.XsltBuilder.process(XsltBuilder.java:132)
>   at 
> org.apache.camel.support.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:95)
>   at 
> org.apache.camel.component.xslt.XsltEndpoint.onExchange(XsltEndpoint.java:121)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (CAMEL-13961) Reconsider default for xslt:allowStAX

2019-09-10 Thread Thomas Diesler (Jira)


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

Thomas Diesler updated CAMEL-13961:
---
Description: 
This is currently set to true. However, Xalan (which the default XSLT processor 
for most) cannot handle StAXSource

{code}
Caused by: javax.xml.transform.TransformerException: 
javax.xml.transform.TransformerException: org.apache.xml.dtm.DTMException: Not 
supported: javax.xml.transform.stax.StAXSource@6a35603
at 
org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:642)
at 
org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:303)
at 
org.apache.camel.component.xslt.XsltBuilder.process(XsltBuilder.java:132)
at 
org.apache.camel.support.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:95)
at 
org.apache.camel.component.xslt.XsltEndpoint.onExchange(XsltEndpoint.java:121)

{code}

  was:This is currently set to true. However, Xalan (which the default XSLT 
processor for most) cannot handle StAXSource


> Reconsider default for xslt:allowStAX
> -
>
> Key: CAMEL-13961
> URL: https://issues.apache.org/jira/browse/CAMEL-13961
> Project: Camel
>  Issue Type: Bug
>Reporter: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0
>
>
> This is currently set to true. However, Xalan (which the default XSLT 
> processor for most) cannot handle StAXSource
> {code}
> Caused by: javax.xml.transform.TransformerException: 
> javax.xml.transform.TransformerException: org.apache.xml.dtm.DTMException: 
> Not supported: javax.xml.transform.stax.StAXSource@6a35603
>   at 
> org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:642)
>   at 
> org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:303)
>   at 
> org.apache.camel.component.xslt.XsltBuilder.process(XsltBuilder.java:132)
>   at 
> org.apache.camel.support.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:95)
>   at 
> org.apache.camel.component.xslt.XsltEndpoint.onExchange(XsltEndpoint.java:121)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (CAMEL-13961) Reconsider default for xslt:allowStAX

2019-09-10 Thread Thomas Diesler (Jira)


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

Thomas Diesler updated CAMEL-13961:
---
Description: This is currently set to true. However, Xalan (which the 
default XSLT processor for most) cannot handle StAXSource  (was: This is 
currently set to true.

However, Xalan (which the default XSLT processor for most) cannot handle 
StAXSource)

> Reconsider default for xslt:allowStAX
> -
>
> Key: CAMEL-13961
> URL: https://issues.apache.org/jira/browse/CAMEL-13961
> Project: Camel
>  Issue Type: Bug
>Reporter: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0
>
>
> This is currently set to true. However, Xalan (which the default XSLT 
> processor for most) cannot handle StAXSource



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (CAMEL-13961) Reconsider default for xslt:allowStAX

2019-09-10 Thread Thomas Diesler (Jira)
Thomas Diesler created CAMEL-13961:
--

 Summary: Reconsider default for xslt:allowStAX
 Key: CAMEL-13961
 URL: https://issues.apache.org/jira/browse/CAMEL-13961
 Project: Camel
  Issue Type: Bug
Reporter: Thomas Diesler
 Fix For: 3.0.0


This is currently set to true.

However, Xalan (which the default XSLT processor for most) cannot handle 
StAXSource



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (CAMEL-12169) [XChange] Add initial support for order management

2019-09-10 Thread Thomas Diesler (Jira)


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

Thomas Diesler resolved CAMEL-12169.

Resolution: Later

Perhaps later

> [XChange] Add initial support for order management
> --
>
> Key: CAMEL-12169
> URL: https://issues.apache.org/jira/browse/CAMEL-12169
> Project: Camel
>  Issue Type: New Feature
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (CAMEL-12543) create a camel-debezium component

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino updated CAMEL-12543:
-
Component/s: camel-debezium

> create a camel-debezium component
> -
>
> Key: CAMEL-12543
> URL: https://issues.apache.org/jira/browse/CAMEL-12543
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-debezium
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0.RC2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See http://debezium.io/docs/embedded/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (CAMEL-13960) Non-retained buffer when using Netty-HTTP as proxy

2019-09-10 Thread Zoran Regvart (Jira)


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

Zoran Regvart resolved CAMEL-13960.
---
Resolution: Fixed

Added a retain when re-using the body of the initial request to be passed as 
the body of the next request.

> Non-retained buffer when using Netty-HTTP as proxy
> --
>
> Key: CAMEL-13960
> URL: https://issues.apache.org/jira/browse/CAMEL-13960
> Project: Camel
>  Issue Type: Bug
>  Components: camel-netty-http
>Affects Versions: 3.0.0.RC1
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.0.0.RC2
>
>
> As can be seen in the stack trace in the CAMEL-13707, we seem to have a 
> non-retained buffer that's being released.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (CAMEL-13960) Non-retained buffer when using Netty-HTTP as proxy

2019-09-10 Thread Zoran Regvart (Jira)
Zoran Regvart created CAMEL-13960:
-

 Summary: Non-retained buffer when using Netty-HTTP as proxy
 Key: CAMEL-13960
 URL: https://issues.apache.org/jira/browse/CAMEL-13960
 Project: Camel
  Issue Type: Bug
  Components: camel-netty-http
Affects Versions: 3.0.0.RC1
Reporter: Zoran Regvart
Assignee: Zoran Regvart
 Fix For: 3.0.0.RC2


As can be seen in the stack trace in the CAMEL-13707, we seem to have a 
non-retained buffer that's being released.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (CAMEL-12543) create a camel-debezium component

2019-09-10 Thread Andrea Cosentino (Jira)


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

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

> create a camel-debezium component
> -
>
> Key: CAMEL-12543
> URL: https://issues.apache.org/jira/browse/CAMEL-12543
> Project: Camel
>  Issue Type: New Feature
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0.RC2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See http://debezium.io/docs/embedded/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (CAMEL-12543) create a camel-debezium component

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino updated CAMEL-12543:
-
Labels:   (was: gsoc2019)

> create a camel-debezium component
> -
>
> Key: CAMEL-12543
> URL: https://issues.apache.org/jira/browse/CAMEL-12543
> Project: Camel
>  Issue Type: New Feature
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0.RC2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See http://debezium.io/docs/embedded/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Assigned] (CAMEL-12543) create a camel-debezium component

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino reassigned CAMEL-12543:


Assignee: Andrea Cosentino

> create a camel-debezium component
> -
>
> Key: CAMEL-12543
> URL: https://issues.apache.org/jira/browse/CAMEL-12543
> Project: Camel
>  Issue Type: New Feature
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Major
>  Labels: gsoc2019
> Fix For: 3.0.0.RC2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See http://debezium.io/docs/embedded/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (CAMEL-12543) create a camel-debezium component

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino updated CAMEL-12543:
-
Fix Version/s: (was: 3.x)
   3.0.0.RC2

> create a camel-debezium component
> -
>
> Key: CAMEL-12543
> URL: https://issues.apache.org/jira/browse/CAMEL-12543
> Project: Camel
>  Issue Type: New Feature
>Reporter: Luca Burgazzoli
>Priority: Major
>  Labels: gsoc2019
> Fix For: 3.0.0.RC2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See http://debezium.io/docs/embedded/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Work logged] (CAMEL-12543) create a camel-debezium component

2019-09-10 Thread ASF GitHub Bot (Jira)


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

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

Author: ASF GitHub Bot
Created on: 10/Sep/19 11:11
Start Date: 10/Sep/19 11:11
Worklog Time Spent: 10m 
  Work Description: oscerd commented on pull request #3128: CAMEL-12543: 
Add camel-debezium component to Camel 
URL: https://github.com/apache/camel/pull/3128
 
 
   
 

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: 309702)
Remaining Estimate: 0h
Time Spent: 10m

> create a camel-debezium component
> -
>
> Key: CAMEL-12543
> URL: https://issues.apache.org/jira/browse/CAMEL-12543
> Project: Camel
>  Issue Type: New Feature
>Reporter: Luca Burgazzoli
>Priority: Major
>  Labels: gsoc2019
> Fix For: 3.0.0.RC2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See http://debezium.io/docs/embedded/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino commented on CAMEL-13953:
--

If this is specific to Red Hat Fuse, you need to ask for support there.

> The url http://camel.apache.org/schema/blueprint/cxf is down
> 
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
>  Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core, 
> http://cxf.apache.org/transports/http/configuration, 
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint, 
> http://cxf.apache.org/configuration/security, 
> http://camel.apache.org/schema/blueprint, 
> http://cxf.apache.org/transports/http-undertow/configuration, 
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf 
> is a couple of days is not reachable and give me error code 404 "Page not 
> found".
> Is down for  a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (CAMEL-13887) camel-mongodb-gridfs - Mongo to MongoClient

2019-09-10 Thread Andrea Cosentino (Jira)


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

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

> camel-mongodb-gridfs - Mongo to MongoClient
> ---
>
> Key: CAMEL-13887
> URL: https://issues.apache.org/jira/browse/CAMEL-13887
> Project: Camel
>  Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0.RC2
>
>
> The former is deprecate and we should switch to MongoDBClient instead



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Assigned] (CAMEL-13887) camel-mongodb-gridfs - Mongo to MongoClient

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino reassigned CAMEL-13887:


Assignee: Andrea Cosentino

> camel-mongodb-gridfs - Mongo to MongoClient
> ---
>
> Key: CAMEL-13887
> URL: https://issues.apache.org/jira/browse/CAMEL-13887
> Project: Camel
>  Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0.RC2
>
>
> The former is deprecate and we should switch to MongoDBClient instead



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (CAMEL-13887) camel-mongodb-gridfs - Mongo to MongoClient

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino updated CAMEL-13887:
-
Fix Version/s: (was: 3.x)
   3.0.0.RC2

> camel-mongodb-gridfs - Mongo to MongoClient
> ---
>
> Key: CAMEL-13887
> URL: https://issues.apache.org/jira/browse/CAMEL-13887
> Project: Camel
>  Issue Type: Improvement
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 3.0.0.RC2
>
>
> The former is deprecate and we should switch to MongoDBClient instead



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Work logged] (CAMEL-13954) Generated property configurator is using wrong method on endpoint (camel-file-watch component)

2019-09-10 Thread ASF GitHub Bot (Jira)


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

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

Author: ASF GitHub Bot
Created on: 10/Sep/19 08:51
Start Date: 10/Sep/19 08:51
Worklog Time Spent: 10m 
  Work Description: omarsmak commented on pull request #3157: CAMEL-13954: 
Set file-watch events explicitly instead of relying on relying on the the auto 
generated property configurator
URL: https://github.com/apache/camel/pull/3157
 
 
   **Scope of changes**
   
   - Due to [CAMEL-13954](https://issues.apache.org/jira/browse/CAMEL-13954), 
the auto generated property configurator will use the wrong method which is 
expected due to the param type. However, instead of that, we just set events 
manually using the correct method.
   - Change junit testing directory from the default to the `target` folder. 
   - Make sure to delete spring testing files after the tests.
   - Add and modify some testing cases 
 

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: 309631)
Remaining Estimate: 0h
Time Spent: 10m

> Generated property configurator is using wrong method on endpoint 
> (camel-file-watch component)
> --
>
> Key: CAMEL-13954
> URL: https://issues.apache.org/jira/browse/CAMEL-13954
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 3.0.0.RC1
>Reporter: Edem Tiassou
>Priority: Major
> Fix For: 3.0.0, 3.0.0.RC2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Hi, I'am very new at Camel and I've being trying to use the component 
> camel-file-watch (version:3.0.0-RC1).
> When I set thing up with spring-boot, it does not seem to dectect file 
> systems events.
> With a little investigation, I found that the property conversion of events 
> from the uri scheme (file-watch://some-directory?events=DELETE,CREATE) to the 
> endpoint is calling
> (FileWatchEndpoint.java)
> public void setEvents(Set events) {
> this.events = events;
> }
> Instead of
> (FileWatchEndpoint.java)
> @SuppressWarnings("unused") //called via reflection
> public void setEvents(String commaSeparatedEvents) {
> String[] stringArray = commaSeparatedEvents.split(",");
> Set eventsSet = new HashSet<>();
> for (String event : stringArray) {
> eventsSet.add(FileEventEnum.valueOf(event.trim()));
> }
> events = eventsSet.isEmpty() ? new 
> HashSet<>(Arrays.asList(FileEventEnum.values())) : eventsSet;
> }
> (FileWatchEndpoint.java) events object declaration
> @UriParam(label = "consumer",
> enums = "CREATE,MODIFY,DELETE",
> description = "Comma separated list of events to watch.",
> defaultValue = "CREATE,MODIFY,DELETE")
> private Set events = new 
> HashSet<>(Arrays.asList(FileEventEnum.values()));
> Basically the conversion from String to Set fails and the 
> component is calling the first method listed above with Set instead 
> of Set
> I got it to work by adding a converter from String to Set but 
> I feel like this should have been taken care of by the component.
> Let me know what you think



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (CAMEL-13840) Upgrade to quickfix 2.x

2019-09-10 Thread Andrea Cosentino (Jira)


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

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

> Upgrade to quickfix 2.x
> ---
>
> Key: CAMEL-13840
> URL: https://issues.apache.org/jira/browse/CAMEL-13840
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-quickfix
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0.RC2
>
>
> It would be good to get quickfix upgraded from 1.x to 2.x



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (CAMEL-13916) website - Add migration guide page

2019-09-10 Thread Zoran Regvart (Jira)


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

Zoran Regvart commented on CAMEL-13916:
---

[~alexkieling] I think that makes perfect sense.

> website - Add migration guide page
> --
>
> Key: CAMEL-13916
> URL: https://issues.apache.org/jira/browse/CAMEL-13916
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Claus Ibsen
>Priority: Major
>  Labels: help-wanted
> Fix For: 3.0.0
>
>
> We need to have the migration guide on the website



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (CAMEL-13840) Upgrade to quickfix 2.x

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino updated CAMEL-13840:
-
Fix Version/s: (was: 3.x)
   3.0.0.RC2

> Upgrade to quickfix 2.x
> ---
>
> Key: CAMEL-13840
> URL: https://issues.apache.org/jira/browse/CAMEL-13840
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-quickfix
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0.RC2
>
>
> It would be good to get quickfix upgraded from 1.x to 2.x



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Assigned] (CAMEL-13840) Upgrade to quickfix 2.x

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino reassigned CAMEL-13840:


Assignee: Andrea Cosentino

> Upgrade to quickfix 2.x
> ---
>
> Key: CAMEL-13840
> URL: https://issues.apache.org/jira/browse/CAMEL-13840
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-quickfix
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.x
>
>
> It would be good to get quickfix upgraded from 1.x to 2.x



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (CAMEL-13840) Upgrade to quickfix 2.x

2019-09-10 Thread Andrea Cosentino (Jira)


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

Andrea Cosentino commented on CAMEL-13840:
--

It's already at 2.1.1

> Upgrade to quickfix 2.x
> ---
>
> Key: CAMEL-13840
> URL: https://issues.apache.org/jira/browse/CAMEL-13840
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-quickfix
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 3.x
>
>
> It would be good to get quickfix upgraded from 1.x to 2.x



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (CAMEL-13959) onException does not work

2019-09-10 Thread Akihito Nakano (Jira)
Akihito Nakano created CAMEL-13959:
--

 Summary: onException does not work
 Key: CAMEL-13959
 URL: https://issues.apache.org/jira/browse/CAMEL-13959
 Project: Camel
  Issue Type: Bug
Affects Versions: 3.0.0.M4, 2.24.1
 Environment: * Java8, 11
 * camel-2.24.1
 * camel-3.0.0.M4

 
Reporter: Akihito Nakano


I'm facing the specific case that onException does not work.


Here is a sample application that reproduce the issue.
https://github.com/ackintosh/on-exception-continue-test

The "onException" definition show below does not work. I'm expecting that to 
ignore and continue exceptions in the route but I got an exception.
https://github.com/ackintosh/on-exception-continue-test/blob/master/src/main/resources/order-error-handler.xml#L17-L21

Quick note:
If you comment out 
[this|[https://github.com/ackintosh/on-exception-continue-test/blob/master/src/main/resources/order.xml#L22-L27]]
 and enable 
[this|[https://github.com/ackintosh/on-exception-continue-test/blob/master/src/main/resources/order.xml#L29-L35]]
 instead, the "onException" definition will work.

 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)