[jira] [Updated] (CAMEL-7884) camel-netty4-http does not work for HTTP POST requests
[
https://issues.apache.org/jira/browse/CAMEL-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-7884:
---
Affects Version/s: (was: 2.14.1)
> camel-netty4-http does not work for HTTP POST requests
> --
>
> Key: CAMEL-7884
> URL: https://issues.apache.org/jira/browse/CAMEL-7884
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4-http
>Affects Versions: 2.14.0
>Reporter: Yaron A
>
> I tried to add the camel-netty4-http component to a proper working project
> that uses camel-netty-http.
> HTTP GET requests are working properly but POST requests are not working.
> It might be an issue in Netty but I could not find a solution to get it to
> work.
> Here is the exception I see:
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault removed 0 from heap
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault added 0 on disk
> 2014-10-01 09:12:18,012 TRACE [pool-1-thread-1 ]
> [o.a.c.i.c.DefaultTypeConverter] Converting
> io.netty.util.IllegalReferenceCountException -> java.lang.Throwable with
> value: {}
> io.netty.util.IllegalReferenceCountException: refCnt: 0
> at
> io.netty.buffer.AbstractByteBuf.ensureAccessible(AbstractByteBuf.java:1187)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1170)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:676)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:1461)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:40)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> org.apache.camel.component.netty4.http.NettyChannelBufferStreamCache.read(NettyChannelBufferStreamCache.java:69)
> ~[camel-netty4-http-2.14.0.jar:2.14.0]
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) ~[na:1.8.0]
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> ~[na:1.8.0]
> at java.io.BufferedReader.fill(BufferedReader.java:161) ~[na:1.8.0]
> at java.io.BufferedReader.read1(BufferedReader.java:212) ~[na:1.8.0]
> at java.io.BufferedReader.read(BufferedReader.java:286) ~[na:1.8.0]
> at java.io.Reader.read(Reader.java:140) ~[na:1.8.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:304)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:290)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:351)
> ~[camel-core-2.14.0.jar:2.14.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0]
> at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0]
> at
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1002)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:276)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:165)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.MessageSupport.getMandatoryBody(MessageSupport.java:99)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.builder.ExpressionBuilder$41.evaluate(ExpressionBuilder.java:1011)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:36)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.component.bean.MethodInfo$2.evaluateParameterBinding(MethodInfo.java:595)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.component.bean.MethodInfo$2.evaluate(MethodInfo.java:485)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.component.bean.MethodInfo.createMethodInvocation(MethodInfo.java:240)
> ~[camel-core-2.14.0.jar:2.14.0]
>
[jira] [Commented] (CAMEL-7884) camel-netty4-http does not work for HTTP POST requests
[
https://issues.apache.org/jira/browse/CAMEL-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154452#comment-14154452
]
Claus Ibsen commented on CAMEL-7884:
Can you tell more about your HTTP POST. Maybe you can provide the details how
that request "looks like" eg its HTTP headers and body etc. We do have unit
tests that works with HTTP POST so it works in general.
> camel-netty4-http does not work for HTTP POST requests
> --
>
> Key: CAMEL-7884
> URL: https://issues.apache.org/jira/browse/CAMEL-7884
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4-http
>Affects Versions: 2.14.0
>Reporter: Yaron A
>
> I tried to add the camel-netty4-http component to a proper working project
> that uses camel-netty-http.
> HTTP GET requests are working properly but POST requests are not working.
> It might be an issue in Netty but I could not find a solution to get it to
> work.
> Here is the exception I see:
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault removed 0 from heap
> 2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
> [n.s.ehcache.store.disk.Segment] fault added 0 on disk
> 2014-10-01 09:12:18,012 TRACE [pool-1-thread-1 ]
> [o.a.c.i.c.DefaultTypeConverter] Converting
> io.netty.util.IllegalReferenceCountException -> java.lang.Throwable with
> value: {}
> io.netty.util.IllegalReferenceCountException: refCnt: 0
> at
> io.netty.buffer.AbstractByteBuf.ensureAccessible(AbstractByteBuf.java:1187)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1170)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:676)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:1461)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:40)
> ~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
> at
> org.apache.camel.component.netty4.http.NettyChannelBufferStreamCache.read(NettyChannelBufferStreamCache.java:69)
> ~[camel-netty4-http-2.14.0.jar:2.14.0]
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) ~[na:1.8.0]
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) ~[na:1.8.0]
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> ~[na:1.8.0]
> at java.io.BufferedReader.fill(BufferedReader.java:161) ~[na:1.8.0]
> at java.io.BufferedReader.read1(BufferedReader.java:212) ~[na:1.8.0]
> at java.io.BufferedReader.read(BufferedReader.java:286) ~[na:1.8.0]
> at java.io.Reader.read(Reader.java:140) ~[na:1.8.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:304)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:290)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.converter.IOConverter.toString(IOConverter.java:351)
> ~[camel-core-2.14.0.jar:2.14.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0]
> at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0]
> at
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1002)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:276)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:165)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.impl.MessageSupport.getMandatoryBody(MessageSupport.java:99)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.builder.ExpressionBuilder$41.evaluate(ExpressionBuilder.java:1011)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:36)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.component.bean.MethodInfo$2.evaluateParameterBinding(MethodInfo.java:595)
> ~[camel-core-2.14.0.jar:2.14.0]
> at
> org.apache.camel.comp
[jira] [Created] (CAMEL-7884) camel-netty4-http does not work for HTTP POST requests
Yaron A created CAMEL-7884:
--
Summary: camel-netty4-http does not work for HTTP POST requests
Key: CAMEL-7884
URL: https://issues.apache.org/jira/browse/CAMEL-7884
Project: Camel
Issue Type: Bug
Components: camel-netty4-http
Affects Versions: 2.14.0, 2.14.1
Reporter: Yaron A
I tried to add the camel-netty4-http component to a proper working project that
uses camel-netty-http.
HTTP GET requests are working properly but POST requests are not working.
It might be an issue in Netty but I could not find a solution to get it to work.
Here is the exception I see:
2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
[n.s.ehcache.store.disk.Segment] fault removed 0 from heap
2014-10-01 09:12:18,012 DEBUG [042ase_1412143933559.data]
[n.s.ehcache.store.disk.Segment] fault added 0 on disk
2014-10-01 09:12:18,012 TRACE [pool-1-thread-1 ]
[o.a.c.i.c.DefaultTypeConverter] Converting
io.netty.util.IllegalReferenceCountException -> java.lang.Throwable with value:
{}
io.netty.util.IllegalReferenceCountException: refCnt: 0
at
io.netty.buffer.AbstractByteBuf.ensureAccessible(AbstractByteBuf.java:1187)
~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
at
io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1170)
~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:676)
~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
at
io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:1461)
~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
at io.netty.buffer.CompositeByteBuf.readBytes(CompositeByteBuf.java:40)
~[netty-buffer-4.0.23.Final.jar:4.0.23.Final]
at
org.apache.camel.component.netty4.http.NettyChannelBufferStreamCache.read(NettyChannelBufferStreamCache.java:69)
~[camel-netty4-http-2.14.0.jar:2.14.0]
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
~[na:1.8.0]
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) ~[na:1.8.0]
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) ~[na:1.8.0]
at java.io.InputStreamReader.read(InputStreamReader.java:184)
~[na:1.8.0]
at java.io.BufferedReader.fill(BufferedReader.java:161) ~[na:1.8.0]
at java.io.BufferedReader.read1(BufferedReader.java:212) ~[na:1.8.0]
at java.io.BufferedReader.read(BufferedReader.java:286) ~[na:1.8.0]
at java.io.Reader.read(Reader.java:140) ~[na:1.8.0]
at
org.apache.camel.converter.IOConverter.toString(IOConverter.java:304)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.converter.IOConverter.toString(IOConverter.java:290)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.converter.IOConverter.toString(IOConverter.java:351)
~[camel-core-2.14.0.jar:2.14.0]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[na:1.8.0]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[na:1.8.0]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[na:1.8.0]
at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0]
at
org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1002)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:276)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.mandatoryConvertTo(BaseTypeConverterRegistry.java:165)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.impl.MessageSupport.getMandatoryBody(MessageSupport.java:99)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.builder.ExpressionBuilder$41.evaluate(ExpressionBuilder.java:1011)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:36)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.component.bean.MethodInfo$2.evaluateParameterBinding(MethodInfo.java:595)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.component.bean.MethodInfo$2.evaluate(MethodInfo.java:485)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.component.bean.MethodInfo.createMethodInvocation(MethodInfo.java:240)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:280)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.component.bean.BeanInfo.createInvocation(BeanInfo.java:180)
~[camel-core-2.14.0.jar:2.14.0]
at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:149)
[jira] [Commented] (CAMEL-7883) XSD decoding bad guess in Validator
[ https://issues.apache.org/jira/browse/CAMEL-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153949#comment-14153949 ] Benjamin BONNET commented on CAMEL-7883: Hi, when an imported XSD is decoded, Camel uses a converter defined in context. That converter involves a reader that will not take into account the XSD XML prolog. If that reader does not use the same encoding as one of the imported XSD, you may get into trouble while validating XML files. Instead of providing the content of XSD as char stream, I think it is more appropriate to provide it as a binary stream and let Sax make a good guess about the XSD encoding. I made a pull request on github with a unit test and a fix : see https://github.com/apache/camel/pull/291 Regards > XSD decoding bad guess in Validator > --- > > Key: CAMEL-7883 > URL: https://issues.apache.org/jira/browse/CAMEL-7883 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.13.2, 2.15.0 >Reporter: Benjamin BONNET > > Validator component does not take imported XSD encoding into account when > validating XML. That may lead to validation errors if an imported XSD is > ISO-8859-1 encoded and containing non ASCII caracters, even though that XSD > declares its encoding correctly in its XML prolog. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7883) XSD decoding bad guess in Validator
[ https://issues.apache.org/jira/browse/CAMEL-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153928#comment-14153928 ] ASF GitHub Bot commented on CAMEL-7883: --- GitHub user bonnetb opened a pull request: https://github.com/apache/camel/pull/291 CAMEL-7883 : Validator XSD decoding issue with non UTF-8 imported XSD Let SAX do a good guess for XSD encoding (it uses XSD prolog) instead of using a converter that may not fit. You can merge this pull request into a Git repository by running: $ git pull https://github.com/bonnetb/camel xsdBadDecoding Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/291.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 #291 commit cd5ae15b21762513f8242429f734113c301b08f8 Author: Benjamin BONNET Date: 2014-09-30T22:36:43Z fix for CAMEL-7883 > XSD decoding bad guess in Validator > --- > > Key: CAMEL-7883 > URL: https://issues.apache.org/jira/browse/CAMEL-7883 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.13.2, 2.15.0 >Reporter: Benjamin BONNET > > Validator component does not take imported XSD encoding into account when > validating XML. That may lead to validation errors if an imported XSD is > ISO-8859-1 encoded and containing non ASCII caracters, even though that XSD > declares its encoding correctly in its XML prolog. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7883) XSD decoding bad guess in Validator
Benjamin BONNET created CAMEL-7883: -- Summary: XSD decoding bad guess in Validator Key: CAMEL-7883 URL: https://issues.apache.org/jira/browse/CAMEL-7883 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.13.2, 2.15.0 Reporter: Benjamin BONNET Validator component does not take imported XSD encoding into account when validating XML. That may lead to validation errors if an imported XSD is ISO-8859-1 encoded and containing non ASCII caracters, even though that XSD declares its encoding correctly in its XML prolog. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7766) Exception in split does not trigger onException in main route
[ https://issues.apache.org/jira/browse/CAMEL-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153886#comment-14153886 ] Benjamin BONNET commented on CAMEL-7766: Hi, after cleaning-up my repo, I created pull request 290 : https://github.com/apache/camel/pull/290 Regards > Exception in split does not trigger onException in main route > - > > Key: CAMEL-7766 > URL: https://issues.apache.org/jira/browse/CAMEL-7766 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.13.2 > Environment: JDK7 / W7 >Reporter: Benjamin BONNET > > Exception thrown in a sequential split does not trigger onException applying > to main route. > That bug may be a regression linked to commit#78c7350 (CAMEL-5681 fix) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7766) Exception in split does not trigger onException in main route
[ https://issues.apache.org/jira/browse/CAMEL-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153782#comment-14153782 ] ASF GitHub Bot commented on CAMEL-7766: --- Github user bonnetb closed the pull request at: https://github.com/apache/camel/pull/260 > Exception in split does not trigger onException in main route > - > > Key: CAMEL-7766 > URL: https://issues.apache.org/jira/browse/CAMEL-7766 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.13.2 > Environment: JDK7 / W7 >Reporter: Benjamin BONNET > > Exception thrown in a sequential split does not trigger onException applying > to main route. > That bug may be a regression linked to commit#78c7350 (CAMEL-5681 fix) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7777) GitHub component
[ https://issues.apache.org/jira/browse/CAMEL-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153449#comment-14153449 ] Brett E. Meyer commented on CAMEL-: --- Hey guys, created an additional pull request to add a new producer: automatically close a pull request. There were a few additional cleanup items. https://github.com/apache/camel/pull/289 > GitHub component > > > Key: CAMEL- > URL: https://issues.apache.org/jira/browse/CAMEL- > Project: Camel > Issue Type: New Feature >Reporter: Brett E. Meyer >Assignee: Willem Jiang > Fix For: 2.15.0 > > > For Overlord (http://projectoverlord.io), we need to consume "events" from > GitHub, as well as produce "actions". We're moving towards using Camel as a > backbone for various capabilities, and as such are writing the endpoint > functionality as new Camel components. I'd love to see this incorporated as > another mainline Camel component. > Work in progress: > https://github.com/brmeyer/camel-github > Consumer ideas: > github://pullRequest (new pull requests) > github://pullRequestComment (new pull request comments) > github://commit/[branch] (new commits) > github://tag (new tags) > Producer ideas: > github://pullRequestComment/[pr #] > Obviously, that's only a small portion of the capabilities. The GitHub API > is extensive and opens a large variety of possibilities. > It uses the org.eclipse.egit.github.core SDK > (https://github.com/eclipse/egit-github/tree/master/org.eclipse.egit.github.core), > which is a part of Mylyn and licensed under the EPL. So, there shouldn't be > any reason why this would need to be restricted to Camel Extras. > Similar to what I did for camel-twitter, the Exchange payloads would be the > SDK-provided objects themselves (PullRequest, CommitComment, RepositoryTag, > RepositoryCommit, etc.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7777) GitHub component
[ https://issues.apache.org/jira/browse/CAMEL-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153445#comment-14153445 ] ASF GitHub Bot commented on CAMEL-: --- GitHub user brmeyer opened a pull request: https://github.com/apache/camel/pull/289 camel-github producer to close pull requests (CAMEL-) - created camel-github producer to close pull requests - automatically set "GitHubPullRequest" header on pull request consumers You can merge this pull request into a Git repository by running: $ git pull https://github.com/brmeyer/camel camel-github-close-pr Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/289.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 #289 commit f3a5f872ec97e8e91f072018575b3a52cf16ff43 Author: Brett Meyer Date: 2014-09-30T17:41:55Z - created camel-github producer to close pull requests - automatically set "GitHubPullRequest" header on pull request consumers > GitHub component > > > Key: CAMEL- > URL: https://issues.apache.org/jira/browse/CAMEL- > Project: Camel > Issue Type: New Feature >Reporter: Brett E. Meyer >Assignee: Willem Jiang > Fix For: 2.15.0 > > > For Overlord (http://projectoverlord.io), we need to consume "events" from > GitHub, as well as produce "actions". We're moving towards using Camel as a > backbone for various capabilities, and as such are writing the endpoint > functionality as new Camel components. I'd love to see this incorporated as > another mainline Camel component. > Work in progress: > https://github.com/brmeyer/camel-github > Consumer ideas: > github://pullRequest (new pull requests) > github://pullRequestComment (new pull request comments) > github://commit/[branch] (new commits) > github://tag (new tags) > Producer ideas: > github://pullRequestComment/[pr #] > Obviously, that's only a small portion of the capabilities. The GitHub API > is extensive and opens a large variety of possibilities. > It uses the org.eclipse.egit.github.core SDK > (https://github.com/eclipse/egit-github/tree/master/org.eclipse.egit.github.core), > which is a part of Mylyn and licensed under the EPL. So, there shouldn't be > any reason why this would need to be restricted to Camel Extras. > Similar to what I did for camel-twitter, the Exchange payloads would be the > SDK-provided objects themselves (PullRequest, CommitComment, RepositoryTag, > RepositoryCommit, etc.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7882) camel-syslog's CamelSyslogTimestamp header is suddenly a GregorianCalendar
Jan-Helge Bergesen created CAMEL-7882:
-
Summary: camel-syslog's CamelSyslogTimestamp header is suddenly a
GregorianCalendar
Key: CAMEL-7882
URL: https://issues.apache.org/jira/browse/CAMEL-7882
Project: Camel
Issue Type: Bug
Components: camel-syslog
Affects Versions: 2.14.0
Environment: RHEL 2.6.32-431.20.3.el6.x86_64
Java 8
Reporter: Jan-Helge Bergesen
Priority: Minor
This is mostly to help others facing the same issue, as we just spent 4x3 hours
figuring this out.
An app, that consumes syslog entries and forwards JMS (over OpenMQ), was
upgraded from camel 2.13.0 to 2.14.0.
Afterwards many things broke upstream, which was masked by poor logging in some
Glassfish servers (truncating stacktraces).
Turns out that the {{CamelSyslogTimestamp}} header was silently discarded,
being a {{java.util.GregorianCalendar}} instance.
Forcing it into a {{java.util.Date}} before routing to the JMS endpoint
restored service throughout the valuechain.
As I wrote; this is mostly a FYI to others :-).
But perhaps the documentation might reflect the lack of guaranteed conversion?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
