[jira] [Commented] (CAMEL-9733) enable dynamic job name in component spring-batch
[ https://issues.apache.org/jira/browse/CAMEL-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262174#comment-15262174 ] Tomas Rohovsky commented on CAMEL-9733: --- You still need to declare initial path of the endpoint. There isn't (and shouldn't exist) a way how to omit it > enable dynamic job name in component spring-batch > - > > Key: CAMEL-9733 > URL: https://issues.apache.org/jira/browse/CAMEL-9733 > Project: Camel > Issue Type: Wish > Components: camel-spring-batch >Affects Versions: 2.16.2, 2.17.0 > Environment: any >Reporter: Jose Luis Pedrosa >Priority: Minor > Fix For: 2.17.2, 2.18.0 > > Original Estimate: 16m > Remaining Estimate: 16m > > Hi > Currently springBatch accepts a parameter jobName in the url, which is > evaluated during the creation of the endpoint. > This makes impossible to launch different jobs dinamically.The requested > feature would be to make it message context based, in the headers with a > parameter > "jobNameHeader", which would be evaluated per message. In a similar way as > SQL and the columns value parameters. > If the project is interested and willing to incorporate it into the sources, > I could offer me to code it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-9866) @PropertyInject doesn't work with Spring-Boot
[
https://issues.apache.org/jira/browse/CAMEL-9866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-9866:
--
Component/s: (was: camel-core)
camel-spring-boot
> @PropertyInject doesn't work with Spring-Boot
> -
>
> Key: CAMEL-9866
> URL: https://issues.apache.org/jira/browse/CAMEL-9866
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot
>Affects Versions: 2.16.3, 2.17.0
>Reporter: Jussi Nupponen
>Assignee: Tomas Rohovsky
>
> When I upgraded Camel Spring-Boot project to use Camel 2.16.3 from Camel
> 2.16.2 the @PropertyInject annotations broke.
> The problem occurs when using the annotation in a Spring-Boot application
> like this
> {code:java}
> @SpringBootApplication
> public class MySpringBootRouter extends FatJarRouter {
> @PropertyInject("inject-value")
> private String injectedValue;
>
> @Override
> public void configure() {
> from("timer:trigger")
> .log("PropertyInject: "+injectedValue);
> }
> }
> {code}
> Running the code above with command
> {noformat}
> mvn spring-boot:run
> {noformat}
> causes the following exception:
> {noformat}
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:478)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'mySpringBootRouter': Initialization of bean failed;
> nested exception is org.apache.camel.spring.GenericBeansException: Error post
> processing bean: mySpringBootRouter; nested exception is
> org.apache.camel.RuntimeCamelException: java.lang.IllegalArgumentException:
> Cannot add component as its already previously added: properties
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:772)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:839)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:538)
> at
> org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118)
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:766)
> at
> org.springframework.boot.SpringApplication.createAndRefreshContext(SpringApplication.java:361)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:307)
> at org.apache.camel.spring.boot.FatJarRouter.main(FatJarRouter.java:26)
> ... 6 more
> Caused by: org.apache.camel.spring.GenericBeansException: Error post
> processing bean: mySpringBootRouter; nested exception is
> org.apache.camel.RuntimeCamelException: java.lang.IllegalArgumentException:
> Cannot add component as its already previously added: properties
> at
> org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:154)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:408)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1570)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
> ... 19 more
> Caused by: org.apache.camel.RuntimeCamelExce
[jira] [Assigned] (CAMEL-9866) @PropertyInject doesn't work with Spring-Boot
[
https://issues.apache.org/jira/browse/CAMEL-9866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky reassigned CAMEL-9866:
-
Assignee: Tomas Rohovsky
> @PropertyInject doesn't work with Spring-Boot
> -
>
> Key: CAMEL-9866
> URL: https://issues.apache.org/jira/browse/CAMEL-9866
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.16.3, 2.17.0
>Reporter: Jussi Nupponen
>Assignee: Tomas Rohovsky
>
> When I upgraded Camel Spring-Boot project to use Camel 2.16.3 from Camel
> 2.16.2 the @PropertyInject annotations broke.
> The problem occurs when using the annotation in a Spring-Boot application
> like this
> {code:java}
> @SpringBootApplication
> public class MySpringBootRouter extends FatJarRouter {
> @PropertyInject("inject-value")
> private String injectedValue;
>
> @Override
> public void configure() {
> from("timer:trigger")
> .log("PropertyInject: "+injectedValue);
> }
> }
> {code}
> Running the code above with command
> {noformat}
> mvn spring-boot:run
> {noformat}
> causes the following exception:
> {noformat}
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:478)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'mySpringBootRouter': Initialization of bean failed;
> nested exception is org.apache.camel.spring.GenericBeansException: Error post
> processing bean: mySpringBootRouter; nested exception is
> org.apache.camel.RuntimeCamelException: java.lang.IllegalArgumentException:
> Cannot add component as its already previously added: properties
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:772)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:839)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:538)
> at
> org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118)
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:766)
> at
> org.springframework.boot.SpringApplication.createAndRefreshContext(SpringApplication.java:361)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:307)
> at org.apache.camel.spring.boot.FatJarRouter.main(FatJarRouter.java:26)
> ... 6 more
> Caused by: org.apache.camel.spring.GenericBeansException: Error post
> processing bean: mySpringBootRouter; nested exception is
> org.apache.camel.RuntimeCamelException: java.lang.IllegalArgumentException:
> Cannot add component as its already previously added: properties
> at
> org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:154)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:408)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1570)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
> ... 19 more
> Caused by: org.apache.camel.RuntimeCamelException:
> java.lang.IllegalArgumentException:
[jira] [Commented] (CAMEL-9866) @PropertyInject doesn't work with Spring-Boot
[
https://issues.apache.org/jira/browse/CAMEL-9866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240002#comment-15240002
]
Tomas Rohovsky commented on CAMEL-9866:
---
The problem was introduced in CAMEL-9431. It should be enough to not add the
properties component in
https://github.com/apache/camel/blob/master/components/camel-spring-boot/src/main/java/org/apache/camel/spring/boot/CamelAutoConfiguration.java#L132,
because it is added later later in
https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/apache/camel/util/CamelContextHelper.java#L578
> @PropertyInject doesn't work with Spring-Boot
> -
>
> Key: CAMEL-9866
> URL: https://issues.apache.org/jira/browse/CAMEL-9866
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.16.3, 2.17.0
>Reporter: Jussi Nupponen
>
> When I upgraded Camel Spring-Boot project to use Camel 2.16.3 from Camel
> 2.16.2 the @PropertyInject annotations broke.
> The problem occurs when using the annotation in a Spring-Boot application
> like this
> {code:java}
> @SpringBootApplication
> public class MySpringBootRouter extends FatJarRouter {
> @PropertyInject("inject-value")
> private String injectedValue;
>
> @Override
> public void configure() {
> from("timer:trigger")
> .log("PropertyInject: "+injectedValue);
> }
> }
> {code}
> Running the code above with command
> {noformat}
> mvn spring-boot:run
> {noformat}
> causes the following exception:
> {noformat}
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:478)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'mySpringBootRouter': Initialization of bean failed;
> nested exception is org.apache.camel.spring.GenericBeansException: Error post
> processing bean: mySpringBootRouter; nested exception is
> org.apache.camel.RuntimeCamelException: java.lang.IllegalArgumentException:
> Cannot add component as its already previously added: properties
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:772)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:839)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:538)
> at
> org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118)
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:766)
> at
> org.springframework.boot.SpringApplication.createAndRefreshContext(SpringApplication.java:361)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:307)
> at org.apache.camel.spring.boot.FatJarRouter.main(FatJarRouter.java:26)
> ... 6 more
> Caused by: org.apache.camel.spring.GenericBeansException: Error post
> processing bean: mySpringBootRouter; nested exception is
> org.apache.camel.RuntimeCamelException: java.lang.IllegalArgumentException:
> Cannot add component as its already previously added: properties
> at
> org.apache.camel.spring.CamelBeanPostProcessor.postProcessBeforeInitialization(CamelBeanPostProcessor.java:154)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:408)
> at
> org.
[jira] [Closed] (CAMEL-9741) recipientList stop if the second endpoint throw exception
[
https://issues.apache.org/jira/browse/CAMEL-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky closed CAMEL-9741.
-
Resolution: Not A Bug
I am closing the issue as this is not a bug.
> recipientList stop if the second endpoint throw exception
> -
>
> Key: CAMEL-9741
> URL: https://issues.apache.org/jira/browse/CAMEL-9741
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.16.2
>Reporter: courtin
>Assignee: Tomas Rohovsky
> Fix For: 2.16.3, 2.18.0, 2.17.1
>
> Attachments: recipientList.rar, recipientList.zip
>
>
> this code is ok and do the agregate :
> from("direct:rlAggregate")
> .process(new Processor() { String destinations =
> "bean:throwingExceptionConsumerB, bean:consumerC";} })
> .recipientList(header("destinations"),
> ",").parallelProcessing().aggregationStrategy(agg);
> an this one not :
> from("direct:rlAggregate")
> .process(new Processor() { String destinations =
> "bean:consumerC, bean:throwingExceptionConsumerB";} })
> .recipientList(header("destinations"),
> ",").parallelProcessing().aggregationStrategy(agg);
> it's throwing :
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange
> they should have the same results. And only the option stopOnException should
> allow to stop when an Exception rise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-9771) Adding XML routes with spring boot error
[ https://issues.apache.org/jira/browse/CAMEL-9771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216738#comment-15216738 ] Tomas Rohovsky edited comment on CAMEL-9771 at 3/29/16 8:01 PM: Adding XML routes will work if you remove the enclosing `beans` element, see: https://github.com/apache/camel/blob/master/components/camel-spring-boot/src/test/resources/camel/camelContext.xml https://github.com/apache/camel/blob/master/components/camel-spring-boot/src/test/java/org/apache/camel/spring/boot/CamelAutoConfigurationTest.java#L156 The question is if it is desired to skip the `beans` element. If not the documentation should be updated to not confuse other people: http://camel.apache.org/spring-boot.html#SpringBoot-AddingXMLroutes was (Author: trohovsky): Adding XML routes will work if you remove the enclosing `beans` element, see https://github.com/apache/camel/blob/master/components/camel-spring-boot/src/test/resources/camel/camelContext.xml The question is if it is desired to skip the `beans` element. If not the documentation should be updated to not confuse other people: http://camel.apache.org/spring-boot.html#SpringBoot-AddingXMLroutes > Adding XML routes with spring boot error > > > Key: CAMEL-9771 > URL: https://issues.apache.org/jira/browse/CAMEL-9771 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Affects Versions: 2.17.0 > Environment: Mac, Java 8. please visit > https://github.com/qiuzhanghua/spring-boot-camel >Reporter: qiuzhanghua > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-9771) Adding XML routes with spring boot error
[ https://issues.apache.org/jira/browse/CAMEL-9771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216738#comment-15216738 ] Tomas Rohovsky commented on CAMEL-9771: --- Adding XML routes will work if you remove the enclosing `beans` element, see https://github.com/apache/camel/blob/master/components/camel-spring-boot/src/test/resources/camel/camelContext.xml The question is if it is desired to skip the `beans` element. If not the documentation should be updated to not confuse other people: http://camel.apache.org/spring-boot.html#SpringBoot-AddingXMLroutes > Adding XML routes with spring boot error > > > Key: CAMEL-9771 > URL: https://issues.apache.org/jira/browse/CAMEL-9771 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Affects Versions: 2.17.0 > Environment: Mac, Java 8. please visit > https://github.com/qiuzhanghua/spring-boot-camel >Reporter: qiuzhanghua > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-9741) recipientList stop if the second endpoint throw exception
[
https://issues.apache.org/jira/browse/CAMEL-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212443#comment-15212443
]
Tomas Rohovsky edited comment on CAMEL-9741 at 3/29/16 8:51 AM:
I couldn't open your archive, as Claus suggests zip would be better.
I suppose that you aggregates to/returns newExchange in your
AggregationStrategy. This means that the exchange which you returns from
recipientLIst is the exchange retrieved form the last endpoint in
recipientList, which is "bean:throwingExceptionConsumerB" in your second
example (analogically, if you aggregated to/returned the oldExchange, then the
exchange from the first ednpoint would be returned). And because the exchange
from the last endpoint has an exception set, it is thrown.
If you want to suppress the exception, you can do the following at the
beginning of the aggregate method:
{code}
Exception exception = newExchange.getException();
if (exception != null) {
return oldExchange;
}
{code}
however, I rather suggest proper handling of the exception by [an error
handler|http://camel.apache.org/error-handler.html].
was (Author: trohovsky):
I couldn't open your archive, as Claus suggests zip would be better.
I suppose that you aggregates to/returns newExchange in your
AggregationStrategy. This means that the exchange which you returns from
recipientLIst is the exchange retrieved form the last endpoint in
recipientList, which is "bean:throwingExceptionConsumerB" in your second
example (analogically, if you aggregated to/returned the oldExchange, then the
exchange from the first ednpoint would be returned). And because the exchange
from the last endpoint has an exception set, it is thrown.
If you want to suppress the exception, you can do the following before
returning an exchange form the aggregation strategy:
{code}
Exception exception = newExchange.getException();
if (exception != null) {
newExchange.setException(null);
}
{code}
however, I rather suggest proper handling of the exception by [an error
handler|http://camel.apache.org/error-handler.html].
> recipientList stop if the second endpoint throw exception
> -
>
> Key: CAMEL-9741
> URL: https://issues.apache.org/jira/browse/CAMEL-9741
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.16.2
>Reporter: courtin
>Assignee: Tomas Rohovsky
> Fix For: 2.16.3, 2.18.0, 2.17.1
>
> Attachments: recipientList.rar
>
>
> this code is ok and do the agregate :
> from("direct:rlAggregate")
> .process(new Processor() { String destinations =
> "bean:throwingExceptionConsumerB, bean:consumerC";} })
> .recipientList(header("destinations"),
> ",").parallelProcessing().aggregationStrategy(agg);
> an this one not :
> from("direct:rlAggregate")
> .process(new Processor() { String destinations =
> "bean:consumerC, bean:throwingExceptionConsumerB";} })
> .recipientList(header("destinations"),
> ",").parallelProcessing().aggregationStrategy(agg);
> it's throwing :
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange
> they should have the same results. And only the option stopOnException should
> allow to stop when an Exception rise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-9741) recipientList stop if the second endpoint throw exception
[
https://issues.apache.org/jira/browse/CAMEL-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky reassigned CAMEL-9741:
-
Assignee: Tomas Rohovsky (was: Claus Ibsen)
> recipientList stop if the second endpoint throw exception
> -
>
> Key: CAMEL-9741
> URL: https://issues.apache.org/jira/browse/CAMEL-9741
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.16.2
>Reporter: courtin
>Assignee: Tomas Rohovsky
> Fix For: 2.16.3, 2.18.0, 2.17.1
>
> Attachments: recipientList.rar
>
>
> this code is ok and do the agregate :
> from("direct:rlAggregate")
> .process(new Processor() { String destinations =
> "bean:throwingExceptionConsumerB, bean:consumerC";} })
> .recipientList(header("destinations"),
> ",").parallelProcessing().aggregationStrategy(agg);
> an this one not :
> from("direct:rlAggregate")
> .process(new Processor() { String destinations =
> "bean:consumerC, bean:throwingExceptionConsumerB";} })
> .recipientList(header("destinations"),
> ",").parallelProcessing().aggregationStrategy(agg);
> it's throwing :
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange
> they should have the same results. And only the option stopOnException should
> allow to stop when an Exception rise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9741) recipientList stop if the second endpoint throw exception
[
https://issues.apache.org/jira/browse/CAMEL-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212443#comment-15212443
]
Tomas Rohovsky commented on CAMEL-9741:
---
I couldn't open your archive, as Claus suggests zip would be better.
I suppose that you aggregates to/returns newExchange in your
AggregationStrategy. This means that the exchange which you returns from
recipientLIst is the exchange retrieved form the last endpoint in
recipientList, which is "bean:throwingExceptionConsumerB" in your second
example (analogically, if you aggregated to/returned the oldExchange, then the
exchange from the first ednpoint would be returned). And because the exchange
from the last endpoint has an exception set, it is thrown.
If you want to suppress the exception, you can do the following before
returning an exchange form the aggregation strategy:
{code}
Exception exception = newExchange.getException();
if (exception != null) {
newExchange.setException(null);
}
{code}
however, I rather suggest proper handling of the exception by [an error
handler|http://camel.apache.org/error-handler.html].
> recipientList stop if the second endpoint throw exception
> -
>
> Key: CAMEL-9741
> URL: https://issues.apache.org/jira/browse/CAMEL-9741
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.16.2
>Reporter: courtin
>Assignee: Claus Ibsen
> Fix For: 2.16.3, 2.18.0, 2.17.1
>
> Attachments: recipientList.rar
>
>
> this code is ok and do the agregate :
> from("direct:rlAggregate")
> .process(new Processor() { String destinations =
> "bean:throwingExceptionConsumerB, bean:consumerC";} })
> .recipientList(header("destinations"),
> ",").parallelProcessing().aggregationStrategy(agg);
> an this one not :
> from("direct:rlAggregate")
> .process(new Processor() { String destinations =
> "bean:consumerC, bean:throwingExceptionConsumerB";} })
> .recipientList(header("destinations"),
> ",").parallelProcessing().aggregationStrategy(agg);
> it's throwing :
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange
> they should have the same results. And only the option stopOnException should
> allow to stop when an Exception rise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-9733) enable dynamic job name in component spring-batch
[
https://issues.apache.org/jira/browse/CAMEL-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205303#comment-15205303
]
Tomas Rohovsky edited comment on CAMEL-9733 at 3/21/16 10:42 PM:
-
Hi Jose,
IMO with introduction of a [dynamic
to|http://camel.apache.org/message-endpoint.html#MessageEndpoint-DynamicTo]
{{toD}} in Camel 2.16, the component specific headers for overriding URI's
"host" part (like in camel-sql) lost their meaning. The advantage of {{toD}} is
that caching of produces for reuse is provided OOTB.
was (Author: trohovsky):
Hi Jose,
IMO with introduction of a dynamic to {{toD}} in Camel 2.16, the component
specific headers for overriding URI's "host" part (like in camel-sql) lost
their meaning. The advantage of {{toD}} is that caching of produces for reuse
is provided OOTB.
> enable dynamic job name in component spring-batch
> -
>
> Key: CAMEL-9733
> URL: https://issues.apache.org/jira/browse/CAMEL-9733
> Project: Camel
> Issue Type: Wish
> Components: camel-spring-batch
>Affects Versions: 2.16.2, 2.17.0
> Environment: any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.1
>
> Original Estimate: 16m
> Remaining Estimate: 16m
>
> Hi
> Currently springBatch accepts a parameter jobName in the url, which is
> evaluated during the creation of the endpoint.
> This makes impossible to launch different jobs dinamically.The requested
> feature would be to make it message context based, in the headers with a
> parameter
> "jobNameHeader", which would be evaluated per message. In a similar way as
> SQL and the columns value parameters.
> If the project is interested and willing to incorporate it into the sources,
> I could offer me to code it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9733) enable dynamic job name in component spring-batch
[
https://issues.apache.org/jira/browse/CAMEL-9733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205303#comment-15205303
]
Tomas Rohovsky commented on CAMEL-9733:
---
Hi Jose,
IMO with introduction of a dynamic to {{toD}} in Camel 2.16, the component
specific headers for overriding URI's "host" part (like in camel-sql) lost
their meaning. The advantage of {{toD}} is that caching of produces for reuse
is provided OOTB.
> enable dynamic job name in component spring-batch
> -
>
> Key: CAMEL-9733
> URL: https://issues.apache.org/jira/browse/CAMEL-9733
> Project: Camel
> Issue Type: Wish
> Components: camel-spring-batch
>Affects Versions: 2.16.2, 2.17.0
> Environment: any
>Reporter: Jose Luis Pedrosa
>Priority: Minor
> Fix For: 2.17.1
>
> Original Estimate: 16m
> Remaining Estimate: 16m
>
> Hi
> Currently springBatch accepts a parameter jobName in the url, which is
> evaluated during the creation of the endpoint.
> This makes impossible to launch different jobs dinamically.The requested
> feature would be to make it message context based, in the headers with a
> parameter
> "jobNameHeader", which would be evaluated per message. In a similar way as
> SQL and the columns value parameters.
> If the project is interested and willing to incorporate it into the sources,
> I could offer me to code it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-9710) Camel Dozer Component - Fails to load custom function due to NPE
[
https://issues.apache.org/jira/browse/CAMEL-9710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky reassigned CAMEL-9710:
-
Assignee: Tomas Rohovsky
> Camel Dozer Component - Fails to load custom function due to NPE
> -
>
> Key: CAMEL-9710
> URL: https://issues.apache.org/jira/browse/CAMEL-9710
> Project: Camel
> Issue Type: Bug
> Components: camel-dozer
>Affects Versions: 2.16.1
> Environment: Any
>Reporter: Ranjit Nethi
>Assignee: Tomas Rohovsky
>Priority: Minor
>
> Camel Dozer component throws NPE, when using custom converter as shown in the
> following example.
>
> org.example.A
> org.example.B
> custom-converter-param="org.example.CustomMapper,mapCustomer">
> sourceField
> destinationField
>
>
> When the sourceField value is null in the Class A,Fails to load custom
> function and throws RuntimeException caused due to NPE.
> Issue with Code: (
>
> Class: CustomMapper
> Method: invokeFunction
> Line# 117
> Object customObj;
> Method method = null;
> try {
> Class customClass = resolver.resolveClass(className);
> customObj = customClass.newInstance();
> // If a specific mapping operation has been supplied use that
> if (operation != null && prmTypesAndValues != null) {
> method = selectMethod(customClass, operation, source,
> prmTypesAndValues);
> } else if (operation != null) {
> method = customClass.getMethod(operation, source.getClass());
> // * THIS LINE CAUSES NPE, as source is NULL */
> } else {
> method = selectMethod(customClass, source);
> }
> } catch (Exception e) {
> throw new RuntimeException("Failed to load custom function", e);
> }
> StackTrace:
> ---
> java.lang.RuntimeException: Failed to load custom function
> at
> org.apache.camel.component.dozer.CustomMapper.mapCustom(CustomMapper.java:122)
> at
> org.apache.camel.component.dozer.CustomMapper.convert(CustomMapper.java:46)
> at
> org.dozer.MappingProcessor.mapUsingCustomConverterInstance(MappingProcessor.java:977)
> at org.dozer.MappingProcessor.mapFromFieldMap(MappingProcessor.java:355)
> at org.dozer.MappingProcessor.mapField(MappingProcessor.java:307)
> at org.dozer.MappingProcessor.map(MappingProcessor.java:267)
> at org.dozer.MappingProcessor.mapToDestObject(MappingProcessor.java:216)
> at
> org.dozer.MappingProcessor.createByCreationDirectiveAndMap(MappingProcessor.java:196)
> at org.dozer.MappingProcessor.mapGeneral(MappingProcessor.java:170)
> at org.dozer.MappingProcessor.map(MappingProcessor.java:104)
> at org.dozer.MappingProcessor.map(MappingProcessor.java:99)
> at org.dozer.DozerBeanMapper.map(DozerBeanMapper.java:120)
> at
> org.apache.camel.component.dozer.DozerProducer.process(DozerProducer.java:82)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:141)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.interceptor.HandleFaultInterceptor.process(HandleFaultInterceptor.java:42)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:91)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:460)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:121)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109)
> at
> org.apache.camel.processor.UnitOfWorkProducer.process(UnitOfWorkProducer.java:68)
> at
> org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:412)
> at
> org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:380)
> at
> org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java:270)
> at
> org.apache.camel.impl.ProducerCache.sendExchange(Pr
[jira] [Commented] (CAMEL-9710) Camel Dozer Component - Fails to load custom function due to NPE
[
https://issues.apache.org/jira/browse/CAMEL-9710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196069#comment-15196069
]
Tomas Rohovsky commented on CAMEL-9710:
---
I am working on the fix, will be available soon.
> Camel Dozer Component - Fails to load custom function due to NPE
> -
>
> Key: CAMEL-9710
> URL: https://issues.apache.org/jira/browse/CAMEL-9710
> Project: Camel
> Issue Type: Bug
> Components: camel-dozer
>Affects Versions: 2.16.1
> Environment: Any
>Reporter: Ranjit Nethi
>Assignee: Tomas Rohovsky
>Priority: Minor
>
> Camel Dozer component throws NPE, when using custom converter as shown in the
> following example.
>
> org.example.A
> org.example.B
> custom-converter-param="org.example.CustomMapper,mapCustomer">
> sourceField
> destinationField
>
>
> When the sourceField value is null in the Class A,Fails to load custom
> function and throws RuntimeException caused due to NPE.
> Issue with Code: (
>
> Class: CustomMapper
> Method: invokeFunction
> Line# 117
> Object customObj;
> Method method = null;
> try {
> Class customClass = resolver.resolveClass(className);
> customObj = customClass.newInstance();
> // If a specific mapping operation has been supplied use that
> if (operation != null && prmTypesAndValues != null) {
> method = selectMethod(customClass, operation, source,
> prmTypesAndValues);
> } else if (operation != null) {
> method = customClass.getMethod(operation, source.getClass());
> // * THIS LINE CAUSES NPE, as source is NULL */
> } else {
> method = selectMethod(customClass, source);
> }
> } catch (Exception e) {
> throw new RuntimeException("Failed to load custom function", e);
> }
> StackTrace:
> ---
> java.lang.RuntimeException: Failed to load custom function
> at
> org.apache.camel.component.dozer.CustomMapper.mapCustom(CustomMapper.java:122)
> at
> org.apache.camel.component.dozer.CustomMapper.convert(CustomMapper.java:46)
> at
> org.dozer.MappingProcessor.mapUsingCustomConverterInstance(MappingProcessor.java:977)
> at org.dozer.MappingProcessor.mapFromFieldMap(MappingProcessor.java:355)
> at org.dozer.MappingProcessor.mapField(MappingProcessor.java:307)
> at org.dozer.MappingProcessor.map(MappingProcessor.java:267)
> at org.dozer.MappingProcessor.mapToDestObject(MappingProcessor.java:216)
> at
> org.dozer.MappingProcessor.createByCreationDirectiveAndMap(MappingProcessor.java:196)
> at org.dozer.MappingProcessor.mapGeneral(MappingProcessor.java:170)
> at org.dozer.MappingProcessor.map(MappingProcessor.java:104)
> at org.dozer.MappingProcessor.map(MappingProcessor.java:99)
> at org.dozer.DozerBeanMapper.map(DozerBeanMapper.java:120)
> at
> org.apache.camel.component.dozer.DozerProducer.process(DozerProducer.java:82)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:141)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.interceptor.HandleFaultInterceptor.process(HandleFaultInterceptor.java:42)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:91)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:460)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:121)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109)
> at
> org.apache.camel.processor.UnitOfWorkProducer.process(UnitOfWorkProducer.java:68)
> at
> org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:412)
> at
> org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:380)
> at
> org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java
[jira] [Commented] (CAMEL-9710) Camel Dozer Component - Fails to load custom function due to NPE
[
https://issues.apache.org/jira/browse/CAMEL-9710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195819#comment-15195819
]
Tomas Rohovsky commented on CAMEL-9710:
---
I guess your Dozer mapping definition is incorrect, specifically
{{custom-converter-param="org.example.CustomMapper,mapCustomer"}}. See
http://dozer.sourceforge.net/documentation/customconverter.html#Configurable_Custom_Converters.
> Camel Dozer Component - Fails to load custom function due to NPE
> -
>
> Key: CAMEL-9710
> URL: https://issues.apache.org/jira/browse/CAMEL-9710
> Project: Camel
> Issue Type: Bug
> Components: camel-dozer
>Affects Versions: 2.16.1
> Environment: Any
>Reporter: Ranjit Nethi
>
> Camel Dozer component throws NPE, when using custom converter as shown in the
> following example.
>
> org.example.A
> org.example.B
> custom-converter-param="org.example.CustomMapper,mapCustomer">
> sourceField
> destinationField
>
>
> When the sourceField value is null in the Class A,Fails to load custom
> function and throws RuntimeException caused due to NPE.
> Issue with Code: (
>
> Class: CustomMapper
> Method: invokeFunction
> Line# 117
> Object customObj;
> Method method = null;
> try {
> Class customClass = resolver.resolveClass(className);
> customObj = customClass.newInstance();
> // If a specific mapping operation has been supplied use that
> if (operation != null && prmTypesAndValues != null) {
> method = selectMethod(customClass, operation, source,
> prmTypesAndValues);
> } else if (operation != null) {
> method = customClass.getMethod(operation, source.getClass());
> // * THIS LINE CAUSES NPE, as source is NULL */
> } else {
> method = selectMethod(customClass, source);
> }
> } catch (Exception e) {
> throw new RuntimeException("Failed to load custom function", e);
> }
> StackTrace:
> ---
> java.lang.RuntimeException: Failed to load custom function
> at
> org.apache.camel.component.dozer.CustomMapper.mapCustom(CustomMapper.java:122)
> at
> org.apache.camel.component.dozer.CustomMapper.convert(CustomMapper.java:46)
> at
> org.dozer.MappingProcessor.mapUsingCustomConverterInstance(MappingProcessor.java:977)
> at org.dozer.MappingProcessor.mapFromFieldMap(MappingProcessor.java:355)
> at org.dozer.MappingProcessor.mapField(MappingProcessor.java:307)
> at org.dozer.MappingProcessor.map(MappingProcessor.java:267)
> at org.dozer.MappingProcessor.mapToDestObject(MappingProcessor.java:216)
> at
> org.dozer.MappingProcessor.createByCreationDirectiveAndMap(MappingProcessor.java:196)
> at org.dozer.MappingProcessor.mapGeneral(MappingProcessor.java:170)
> at org.dozer.MappingProcessor.map(MappingProcessor.java:104)
> at org.dozer.MappingProcessor.map(MappingProcessor.java:99)
> at org.dozer.DozerBeanMapper.map(DozerBeanMapper.java:120)
> at
> org.apache.camel.component.dozer.DozerProducer.process(DozerProducer.java:82)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:141)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.interceptor.HandleFaultInterceptor.process(HandleFaultInterceptor.java:42)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:91)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:460)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:121)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109)
> at
> org.apache.camel.processor.UnitOfWorkProducer.process(UnitOfWorkProducer.java:68)
> at
> org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:412)
> at
> org.apache.camel.impl.ProducerCache$2.
[jira] [Updated] (CAMEL-8470) Several small fixes for camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8470:
--
Assignee: Tomas Rohovsky (was: Willem Jiang)
> Several small fixes for camel-linkedin
> --
>
> Key: CAMEL-8470
> URL: https://issues.apache.org/jira/browse/CAMEL-8470
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.2
>Reporter: Tomas Rohovsky
>Assignee: Tomas Rohovsky
> Fix For: 2.14.3, 2.15.2, 2.16.0
>
>
> # companies/addShare should return the created Update
> # Share#comment should be String instead of Comment
> # Group#isOpenToNonMembers and Group#allowMemberInvites should be Boolean
> instead of boolean
> Otherwise invoking of people/addGroupMembership causes
> {code}
> Error invoking addGroupMembership: Unexpected
> {group-membership/group/is-open-to-non-members} element, Unexpected
> {group-membership/group/allow-member-invites}
> {code}
> because both attributes (that are not valid for this resource) are present.
> # remove role from people/getSuggestedGroupPosts
> It is only for group-memberships/\{id\}/posts resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8465) Add groups/getPosts endpoint to camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8465:
--
Assignee: Tomas Rohovsky (was: Willem Jiang)
> Add groups/getPosts endpoint to camel-linkedin
> --
>
> Key: CAMEL-8465
> URL: https://issues.apache.org/jira/browse/CAMEL-8465
> Project: Camel
> Issue Type: New Feature
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>Assignee: Tomas Rohovsky
> Fix For: 2.14.3, 2.15.1, 2.16.0
>
>
> Add groups/getPosts endpint that covers following resource:
> {code}
> https://api.linkedin.com/v1/groups/{group-id}/posts
> {code}
> Similar functionality as this resource provides people/getPosts mapped to
> {code}
> https://api.linkedin.com/v1/people/~/group-memberships/{group-id}/posts
> {code}
> , but it requires role to be set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8458) camel-linkedin - public_profile_url option should be String
[
https://issues.apache.org/jira/browse/CAMEL-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8458:
--
Assignee: Tomas Rohovsky
> camel-linkedin - public_profile_url option should be String
> ---
>
> Key: CAMEL-8458
> URL: https://issues.apache.org/jira/browse/CAMEL-8458
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>Assignee: Tomas Rohovsky
> Fix For: 2.14.3, 2.15.1
>
>
> public_profile_url should be String instead of URI. The value of
> public_profile_url must be URL encoded what is not possible with URI.
> Currently I am getting
> {code}
> Error invoking getPersonByUrl: Unknown field {pub} in resource {Person}
> {code}
> for https://www.linkedin.com/pub/jboss-fuse-qe/b4/14b/b
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8464) Remove likeCompanyUpdate endpoint from camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8464:
--
Assignee: Tomas Rohovsky (was: Willem Jiang)
> Remove likeCompanyUpdate endpoint from camel-linkedin
> -
>
> Key: CAMEL-8464
> URL: https://issues.apache.org/jira/browse/CAMEL-8464
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>Assignee: Tomas Rohovsky
> Fix For: 2.14.3, 2.15.1, 2.16.0
>
>
> Similar as CAMEL-8456. The underlying resource
> {code}
> /companies/{company-id}/updates/key={update-key}/is-liked
> {code}
> doesn't exist. It was probably added by mistake instead of
> {code}
> https://api.linkedin.com/v1/people/~/network/updates/key={update-key}/is-liked
> {code}
> mentioned in the documentation
> https://developer-programs.linkedin.com/documents/commenting-and-liking-company-share.
> The resource is already mapped to linkedin://people/likeUpdate so there is
> no need to add it to companies prefixed endpoints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8456) Remove addCompanyUpdateComment endpoint from camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8456:
--
Assignee: Tomas Rohovsky (was: Willem Jiang)
> Remove addCompanyUpdateComment endpoint from camel-linkedin
> ---
>
> Key: CAMEL-8456
> URL: https://issues.apache.org/jira/browse/CAMEL-8456
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>Assignee: Tomas Rohovsky
> Fix For: 2.14.3, 2.15.1, 2.16.0
>
>
> Underlying resource
> {code}
> /companies/{company-id}/updates/key={update-key}/update-comments
> {code}
> does not exist. It was probably added by mistake instead of
> {code}
> https://api.linkedin.com/v1/people/~/network/updates/key={update-key}/update-comments
> {code}
> mentioned in the documentation
> [https://developer-programs.linkedin.com/documents/commenting-and-liking-company-share].
> The resource is already mapped to linkedin://people/addUpdateComment so
> there is no need to add it to companies prefixed endpoints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8457) Correct return types of some endpoints in camel-linkedin
[ https://issues.apache.org/jira/browse/CAMEL-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Rohovsky updated CAMEL-8457: -- Assignee: Tomas Rohovsky (was: Willem Jiang) > Correct return types of some endpoints in camel-linkedin > > > Key: CAMEL-8457 > URL: https://issues.apache.org/jira/browse/CAMEL-8457 > Project: Camel > Issue Type: Bug >Affects Versions: 2.14.1 >Reporter: Tomas Rohovsky >Assignee: Tomas Rohovsky > Fix For: 2.14.3, 2.15.1, 2.16.0 > > > These endpoints return wrong type: > - companies/getCompanyUpdateComments - Comments/UpdateComments > - companies/getUpdateComments - Comments/UpdateComments > - people/getGroupMembershipSettings - GroupMemberships/GroupMembership > so it results in java.lang.ClassCastException. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8455) camel-linkedin - update_key option should be optional in getHistoricalStatusUpdateStatistics
[
https://issues.apache.org/jira/browse/CAMEL-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8455:
--
Assignee: Tomas Rohovsky (was: Willem Jiang)
> camel-linkedin - update_key option should be optional in
> getHistoricalStatusUpdateStatistics
>
>
> Key: CAMEL-8455
> URL: https://issues.apache.org/jira/browse/CAMEL-8455
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>Assignee: Tomas Rohovsky
> Fix For: 2.14.3, 2.15.1, 2.16.0
>
>
> update_key option should be optional in getHistoricalStatusUpdateStatistics
> endpoint. Currently it ends with an exception if the option is not specified:
> {{org.apache.camel.RuntimeCamelException: Missing properties for
> getHistoricalStatusUpdateStatistics, need one or more from \[end_timestamp,
> update_key\]}} See the LinkedIn API docs:
> https://developer-programs.linkedin.com/historical-company-statistics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8454) Correct a comment in files generated by camel-api-component-maven-plugin
[ https://issues.apache.org/jira/browse/CAMEL-8454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Rohovsky updated CAMEL-8454: -- Assignee: Tomas Rohovsky (was: Willem Jiang) > Correct a comment in files generated by camel-api-component-maven-plugin > > > Key: CAMEL-8454 > URL: https://issues.apache.org/jira/browse/CAMEL-8454 > Project: Camel > Issue Type: Task > Components: tooling >Affects Versions: 2.14.1 >Reporter: Tomas Rohovsky >Assignee: Tomas Rohovsky >Priority: Trivial > Fix For: 2.14.3, 2.15.1, 2.16.0 > > > Generted files contains original name of the plugin > (camel-component-util-maven-plugin) instead of > camel-api-component-maven-plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-9384) Host HTTP header should contain a port number if it differs form 80
Tomas Rohovsky created CAMEL-9384:
-
Summary: Host HTTP header should contain a port number if it
differs form 80
Key: CAMEL-9384
URL: https://issues.apache.org/jira/browse/CAMEL-9384
Project: Camel
Issue Type: Bug
Components: camel-netty-http, camel-netty4-http
Reporter: Tomas Rohovsky
Assignee: Tomas Rohovsky
Priority: Minor
{quote}
Host = "Host" ":" host [ ":" port ] ; Section 3.2.2
A "host" without any trailing port information implies the default port for the
service requested (e.g., "80" for an HTTP URL).
{quote}
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23
The problem is in netty-http and netty4-http, jetty works as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-9047) Replace deprecated boxjavalibv2 with box-java-sdk
Tomas Rohovsky created CAMEL-9047: - Summary: Replace deprecated boxjavalibv2 with box-java-sdk Key: CAMEL-9047 URL: https://issues.apache.org/jira/browse/CAMEL-9047 Project: Camel Issue Type: Improvement Components: camel-box Affects Versions: 2.15.2 Reporter: Tomas Rohovsky camel-box component is based on boxjavalibv2 \[1\], which was made deprecated in favour of box-java-sdk \[2\] \[3\]. "The new SDK is not backwards compatible and any code using this SDK will need to be migrated in order to take advantage of any new features and bug fixes." \[1\] https://github.com/box/deprecated-box-java-sdk-v2 \[2\] http://opensource.box.com/box-java-sdk/ \[3\] https://www.box.com/blog/the-new-box-java-sdk/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-9043) Fix camel-example-cxf-osgi/blueprint examples
[ https://issues.apache.org/jira/browse/CAMEL-9043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649588#comment-14649588 ] Tomas Rohovsky commented on CAMEL-9043: --- https://github.com/apache/camel/pull/582 > Fix camel-example-cxf-osgi/blueprint examples > - > > Key: CAMEL-9043 > URL: https://issues.apache.org/jira/browse/CAMEL-9043 > Project: Camel > Issue Type: Bug > Components: examples >Affects Versions: 2.15.2 >Reporter: Tomas Rohovsky >Assignee: Tomas Rohovsky > > Cannot deploy camel-example-cxf-osgi because of wrong Import-Package > requirement. Expression for output filename is not evaluated properly in both > examples. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-9043) Fix camel-example-cxf-osgi/blueprint examples
Tomas Rohovsky created CAMEL-9043: - Summary: Fix camel-example-cxf-osgi/blueprint examples Key: CAMEL-9043 URL: https://issues.apache.org/jira/browse/CAMEL-9043 Project: Camel Issue Type: Bug Components: examples Affects Versions: 2.15.2 Reporter: Tomas Rohovsky Assignee: Tomas Rohovsky Cannot deploy camel-example-cxf-osgi because of wrong Import-Package requirement. Expression for output filename is not evaluated properly in both examples. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-9030) The instructions for camel-example-box-osgi are incorrect
Tomas Rohovsky created CAMEL-9030:
-
Summary: The instructions for camel-example-box-osgi are incorrect
Key: CAMEL-9030
URL: https://issues.apache.org/jira/browse/CAMEL-9030
Project: Camel
Issue Type: Bug
Components: examples
Affects Versions: 2.15.2
Reporter: Tomas Rohovsky
Step 3 in the example's instructions reads as follows:
{quote}
3) Create a `box.properties` file in the Karaf working directory with the
following properties set to your box account credentials.
{quote}
However, the camel-context.xml file sets up the PropertyPlaceholderConfigurer
locations property to look for the "box.com.properties" file instead.
{code:xml}
file:box.com.properties
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-9030) The instructions for camel-example-box-osgi are incorrect
[
https://issues.apache.org/jira/browse/CAMEL-9030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky reassigned CAMEL-9030:
-
Assignee: Tomas Rohovsky
> The instructions for camel-example-box-osgi are incorrect
> -
>
> Key: CAMEL-9030
> URL: https://issues.apache.org/jira/browse/CAMEL-9030
> Project: Camel
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.15.2
>Reporter: Tomas Rohovsky
>Assignee: Tomas Rohovsky
>
> Step 3 in the example's instructions reads as follows:
> {quote}
> 3) Create a `box.properties` file in the Karaf working directory with the
> following properties set to your box account credentials.
> {quote}
> However, the camel-context.xml file sets up the PropertyPlaceholderConfigurer
> locations property to look for the "box.com.properties" file instead.
> {code:xml}
> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>
>
> file:box.com.properties
>
>
>
>
> value="SYSTEM_PROPERTIES_MODE_OVERRIDE" />
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8853) CXF endpoint with a relative address cannot be invoked by a producer template
Tomas Rohovsky created CAMEL-8853:
-
Summary: CXF endpoint with a relative address cannot be invoked by
a producer template
Key: CAMEL-8853
URL: https://issues.apache.org/jira/browse/CAMEL-8853
Project: Camel
Issue Type: Bug
Components: camel-cxf
Affects Versions: 2.15.2
Reporter: Tomas Rohovsky
Attachments: cxf-producer-template.zip
If you invoke this Camel CXF endpoint by a producer template:
{code}
{code}
you will get:
{code}
org.apache.camel.CamelExecutionException: Exception occurred during execution
on the exchange: Exchange[Message: Tom]
at
org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1635)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:645)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:133)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:149)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:301)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:331)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.example.cxf_producer_template.ProducerProcessor.process(ProducerProcessor.java:12)[265:cxf-producer-template:0.0.1.SNAPSHOT]
at
org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:103)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:129)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:448)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:165)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at
org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:73)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
at java.util.TimerThread.mainLoop(Timer.java:555)[:1.7.0_71]
at java.util.TimerThread.run(Timer.java:505)[:1.7.0_71]
Caused by: java.lang.IllegalArgumentException: URI is not absolute
at java.net.URI.toURL(URI.java:1095)[:1.7.0_71]
at
org.apache.cxf.transport.http.Address.getURL(Address.java:45)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
at
org.apache.cxf.transport.http.URLConnectionHTTPConduit.createConnection(URLConnectionHTTPConduit.java:93)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
at
org.apache.cxf.transport.http.URLConnectionHTTPConduit.setupConnection(URLConnectionHTTPConduit.java:105)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
at
org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.java:496)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
at
org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:46)[118:org.apache.cxf.cxf-core:3.0.4.redhat-620123]
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)[118:org.apache.cxf.cxf-core:3.0.4.redhat-620123]
at
org.apache.cxf.endpoint.ClientImpl.d
[jira] [Updated] (CAMEL-8853) CXF endpoint with a relative address cannot be invoked by a producer template
[
https://issues.apache.org/jira/browse/CAMEL-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8853:
--
Attachment: cxf-producer-template.zip
> CXF endpoint with a relative address cannot be invoked by a producer template
> -
>
> Key: CAMEL-8853
> URL: https://issues.apache.org/jira/browse/CAMEL-8853
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.15.2
>Reporter: Tomas Rohovsky
> Attachments: cxf-producer-template.zip
>
>
> If you invoke this Camel CXF endpoint by a producer template:
> {code}
> serviceClass="org.example.cxf_producer_template.GreetingService"/>
> {code}
> you will get:
> {code}
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange: Exchange[Message: Tom]
> at
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1635)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:645)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:133)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:149)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:301)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:331)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.example.cxf_producer_template.ProducerProcessor.process(ProducerProcessor.java:12)[265:cxf-producer-template:0.0.1.SNAPSHOT]
> at
> org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:103)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:129)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:448)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:165)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:73)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at java.util.TimerThread.mainLoop(Timer.java:555)[:1.7.0_71]
> at java.util.TimerThread.run(Timer.java:505)[:1.7.0_71]
> Caused by: java.lang.IllegalArgumentException: URI is not absolute
> at java.net.URI.toURL(URI.java:1095)[:1.7.0_71]
> at
> org.apache.cxf.transport.http.Address.getURL(Address.java:45)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
> at
> org.apache.cxf.transport.http.URLConnectionHTTPConduit.createConnection(URLConnectionHTTPConduit.java:93)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
> at
> org.apache.cxf.transport.http.URLConnectionHTTPConduit.setupConnection(URLConnectionHTTPConduit.java:105)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
> at
> org.apache.cxf.transport.http.HTTPConduit.prepare(HTTPConduit.java:496)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.red
[jira] [Closed] (CAMEL-8814) Correct/update camel-hazelcast documentation
[
https://issues.apache.org/jira/browse/CAMEL-8814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky closed CAMEL-8814.
-
Resolution: Duplicate
> Correct/update camel-hazelcast documentation
>
>
> Key: CAMEL-8814
> URL: https://issues.apache.org/jira/browse/CAMEL-8814
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Tomas Rohovsky
>
> * "Usage of Multi Map" section is present two times
> *# the first should be removed as it contains description for unsupported
> operations (update, query) and miss description for removevalue.
> * Add newly added operations to map producer (PUT_IF_ABSENT_OPERATION,
> GET_ALL_OPERATION, CLEAR_OPERATION)
> * Add newly added operation to multimap producer (CLEAR_OPERATION)
> * Change to("hazelcast:atomicnumber:foo") to to("hazelcast:atomicvalue:foo")
> *# IMO atomicnumber is actually a better name for this endpoint, but changing
> it would break backward compatibility
> * Mention that OBJECT_POS header is used for indexing in list producer
> * Remove non-actual comments like "Please note that set,get and removevalue
> and not yet supported by hazelcast, will be added in the future.."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8814) Correct/update camel-hazelcast documentation
[
https://issues.apache.org/jira/browse/CAMEL-8814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564471#comment-14564471
]
Tomas Rohovsky commented on CAMEL-8814:
---
I am closing this one as I unintentionally submitted it two times. The JIRA
didn't respond yesterday, so I tried to create it again.
> Correct/update camel-hazelcast documentation
>
>
> Key: CAMEL-8814
> URL: https://issues.apache.org/jira/browse/CAMEL-8814
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Tomas Rohovsky
>
> * "Usage of Multi Map" section is present two times
> *# the first should be removed as it contains description for unsupported
> operations (update, query) and miss description for removevalue.
> * Add newly added operations to map producer (PUT_IF_ABSENT_OPERATION,
> GET_ALL_OPERATION, CLEAR_OPERATION)
> * Add newly added operation to multimap producer (CLEAR_OPERATION)
> * Change to("hazelcast:atomicnumber:foo") to to("hazelcast:atomicvalue:foo")
> *# IMO atomicnumber is actually a better name for this endpoint, but changing
> it would break backward compatibility
> * Mention that OBJECT_POS header is used for indexing in list producer
> * Remove non-actual comments like "Please note that set,get and removevalue
> and not yet supported by hazelcast, will be added in the future.."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8814) Correct/update camel-hazelcast documentation
Tomas Rohovsky created CAMEL-8814:
-
Summary: Correct/update camel-hazelcast documentation
Key: CAMEL-8814
URL: https://issues.apache.org/jira/browse/CAMEL-8814
Project: Camel
Issue Type: Task
Components: documentation
Reporter: Tomas Rohovsky
* "Usage of Multi Map" section is present two times
*# the first should be removed as it contains description for unsupported
operations (update, query) and miss description for removevalue.
* Add newly added operations to map producer (PUT_IF_ABSENT_OPERATION,
GET_ALL_OPERATION, CLEAR_OPERATION)
* Add newly added operation to multimap producer (CLEAR_OPERATION)
* Change to("hazelcast:atomicnumber:foo") to to("hazelcast:atomicvalue:foo")
*# IMO atomicnumber is actually a better name for this endpoint, but changing
it would break backward compatibility
* Mention that OBJECT_POS header is used for indexing in list producer
* Remove non-actual comments like "Please note that set,get and removevalue and
not yet supported by hazelcast, will be added in the future.."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8813) Correct/update camel-hazelcast documentation
Tomas Rohovsky created CAMEL-8813:
-
Summary: Correct/update camel-hazelcast documentation
Key: CAMEL-8813
URL: https://issues.apache.org/jira/browse/CAMEL-8813
Project: Camel
Issue Type: Task
Components: documentation
Reporter: Tomas Rohovsky
* "Usage of Multi Map" section is present two times
*# the first should be removed as it contains description for unsupported
operations (update, query) and miss description for removevalue.
* Add newly added operations to map producer (PUT_IF_ABSENT_OPERATION,
GET_ALL_OPERATION, CLEAR_OPERATION)
* Add newly added operation to multimap producer (CLEAR_OPERATION)
* Change to("hazelcast:atomicnumber:foo") to to("hazelcast:atomicvalue:foo")
*# IMO atomicnumber is actually a better name for this endpoint, but changing
it would break backward compatibility
* Mention that OBJECT_POS header is used for indexing in list producer
* Remove non-actual comments like "Please note that set,get and removevalue and
not yet supported by hazelcast, will be added in the future.."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (CAMEL-8470) Several small fixes for camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky reopened CAMEL-8470:
---
Estimated Complexity: Novice (was: Unknown)
Share#comment is not fixed to be of String type
> Several small fixes for camel-linkedin
> --
>
> Key: CAMEL-8470
> URL: https://issues.apache.org/jira/browse/CAMEL-8470
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.2
>Reporter: Tomas Rohovsky
>Assignee: Willem Jiang
> Fix For: 2.14.3, 2.15.1, 2.16.0
>
>
> # companies/addShare should return the created Update
> # Share#comment should be String instead of Comment
> # Group#isOpenToNonMembers and Group#allowMemberInvites should be Boolean
> instead of boolean
> Otherwise invoking of people/addGroupMembership causes
> {code}
> Error invoking addGroupMembership: Unexpected
> {group-membership/group/is-open-to-non-members} element, Unexpected
> {group-membership/group/allow-member-invites}
> {code}
> because both attributes (that are not valid for this resource) are present.
> # remove role from people/getSuggestedGroupPosts
> It is only for group-memberships/\{id\}/posts resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CAMEL-8469) Several enum types should generate lower case values in camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky closed CAMEL-8469.
-
> Several enum types should generate lower case values in camel-linkedin
> --
>
> Key: CAMEL-8469
> URL: https://issues.apache.org/jira/browse/CAMEL-8469
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>Assignee: Dhiraj Bokde
>
> Following parameters - types should generate values in lower case:
> - event_type - org.apache.camel.component.linkedin.api.Eventtype
> - category - org.apache.camel.component.linkedin.api.Category
> - order - org.apache.camel.component.linkedin.api.Order
> - role - org.apache.camel.component.linkedin.api.Role
> - postcategorycode -
> org.apache.camel.component.linkedin.api.model.PostCategoryCode
> Also notice that postcategory code should contain 'job' and 'promotion'
> values - https://developer-programs.linkedin.com/documents/groups-api.
> I've tried to fix that with adding of
> {code}
>
>
>
> {code}
> to linkedin-api-schema.xjb as well as appropriate simpleType to
> linkedin-api-schema.xsd, but it was without success. I still got:
> {code}
> Error invoking getCompanyUpdates: Invalid filter {STATUS_UPDATE}
> {code}
> Names of enum values are used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8469) Several enum types should generate lower case values in camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526705#comment-14526705
]
Tomas Rohovsky commented on CAMEL-8469:
---
verified
> Several enum types should generate lower case values in camel-linkedin
> --
>
> Key: CAMEL-8469
> URL: https://issues.apache.org/jira/browse/CAMEL-8469
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>Assignee: Dhiraj Bokde
>
> Following parameters - types should generate values in lower case:
> - event_type - org.apache.camel.component.linkedin.api.Eventtype
> - category - org.apache.camel.component.linkedin.api.Category
> - order - org.apache.camel.component.linkedin.api.Order
> - role - org.apache.camel.component.linkedin.api.Role
> - postcategorycode -
> org.apache.camel.component.linkedin.api.model.PostCategoryCode
> Also notice that postcategory code should contain 'job' and 'promotion'
> values - https://developer-programs.linkedin.com/documents/groups-api.
> I've tried to fix that with adding of
> {code}
>
>
>
> {code}
> to linkedin-api-schema.xjb as well as appropriate simpleType to
> linkedin-api-schema.xsd, but it was without success. I still got:
> {code}
> Error invoking getCompanyUpdates: Invalid filter {STATUS_UPDATE}
> {code}
> Names of enum values are used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8470) Several small fixes for camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366929#comment-14366929
]
Tomas Rohovsky commented on CAMEL-8470:
---
Can someone merge this PR please?
> Several small fixes for camel-linkedin
> --
>
> Key: CAMEL-8470
> URL: https://issues.apache.org/jira/browse/CAMEL-8470
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.2
>Reporter: Tomas Rohovsky
>
> # companies/addShare should return the created Update
> # Share#comment should be String instead of Comment
> # Group#isOpenToNonMembers and Group#allowMemberInvites should be Boolean
> instead of boolean
> Otherwise invoking of people/addGroupMembership causes
> {code}
> Error invoking addGroupMembership: Unexpected
> {group-membership/group/is-open-to-non-members} element, Unexpected
> {group-membership/group/allow-member-invites}
> {code}
> because both attributes (that are not valid for this resource) are present.
> # remove role from people/getSuggestedGroupPosts
> It is only for group-memberships/\{id\}/posts resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8470) Several small fixes for camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8470:
--
Description:
# companies/addShare should return the created Update
# Share#comment should be String instead of Comment
# Group#isOpenToNonMembers and Group#allowMemberInvites should be Boolean
instead of boolean
Otherwise invoking of people/addGroupMembership causes
{code}
Error invoking addGroupMembership: Unexpected
{group-membership/group/is-open-to-non-members} element, Unexpected
{group-membership/group/allow-member-invites}
{code}
because both attributes (that are not valid for this resource) are present.
# remove role from people/getSuggestedGroupPosts
It is only for group-memberships/\{id\}/posts resource.
was:
# companies/addShare should return the created Update
# Share#comment should be String instead of Comment
# Group#isOpenToNonMembers and Group#allowMemberInvites should be Boolean
instead of boolean
Otherwise invoking of people/addGroupMembership causes
{code}
Error invoking addGroupMembership: Unexpected
{group-membership/group/is-open-to-non-members} element, Unexpected
{group-membership/group/allow-member-invites}
{code}
because both attributes (that are not valid for this resource) are present.
# remove role from people/getSuggestedGroupPosts
It is only for group-memberships/{id}/posts resource.
> Several small fixes for camel-linkedin
> --
>
> Key: CAMEL-8470
> URL: https://issues.apache.org/jira/browse/CAMEL-8470
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.2
>Reporter: Tomas Rohovsky
>
> # companies/addShare should return the created Update
> # Share#comment should be String instead of Comment
> # Group#isOpenToNonMembers and Group#allowMemberInvites should be Boolean
> instead of boolean
> Otherwise invoking of people/addGroupMembership causes
> {code}
> Error invoking addGroupMembership: Unexpected
> {group-membership/group/is-open-to-non-members} element, Unexpected
> {group-membership/group/allow-member-invites}
> {code}
> because both attributes (that are not valid for this resource) are present.
> # remove role from people/getSuggestedGroupPosts
> It is only for group-memberships/\{id\}/posts resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8470) Several small fixes for camel-linkedin
Tomas Rohovsky created CAMEL-8470:
-
Summary: Several small fixes for camel-linkedin
Key: CAMEL-8470
URL: https://issues.apache.org/jira/browse/CAMEL-8470
Project: Camel
Issue Type: Bug
Affects Versions: 2.14.2
Reporter: Tomas Rohovsky
# companies/addShare should return the created Update
# Share#comment should be String instead of Comment
# Group#isOpenToNonMembers and Group#allowMemberInvites should be Boolean
instead of boolean
Otherwise invoking of people/addGroupMembership causes
{code}
Error invoking addGroupMembership: Unexpected
{group-membership/group/is-open-to-non-members} element, Unexpected
{group-membership/group/allow-member-invites}
{code}
because both attributes (that are not valid for this resource) are present.
# remove role from people/getSuggestedGroupPosts
It is only for group-memberships/{id}/posts resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8469) Several enum types should generate lower case values in camel-linkedin
Tomas Rohovsky created CAMEL-8469:
-
Summary: Several enum types should generate lower case values in
camel-linkedin
Key: CAMEL-8469
URL: https://issues.apache.org/jira/browse/CAMEL-8469
Project: Camel
Issue Type: Bug
Affects Versions: 2.14.1
Reporter: Tomas Rohovsky
Following parameters - types should generate values in lower case:
- event_type - org.apache.camel.component.linkedin.api.Eventtype
- category - org.apache.camel.component.linkedin.api.Category
- order - org.apache.camel.component.linkedin.api.Order
- role - org.apache.camel.component.linkedin.api.Role
- postcategorycode -
org.apache.camel.component.linkedin.api.model.PostCategoryCode
Also notice that postcategory code should contain 'job' and 'promotion' values
- https://developer-programs.linkedin.com/documents/groups-api.
I've tried to fix that with adding of
{code}
{code}
to linkedin-api-schema.xjb as well as appropriate simpleType to
linkedin-api-schema.xsd, but it was without success. I still got:
{code}
Error invoking getCompanyUpdates: Invalid filter {STATUS_UPDATE}
{code}
Names of enum values are used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8465) Add groups/getPosts endpoint to camel-linkedin
Tomas Rohovsky created CAMEL-8465:
-
Summary: Add groups/getPosts endpoint to camel-linkedin
Key: CAMEL-8465
URL: https://issues.apache.org/jira/browse/CAMEL-8465
Project: Camel
Issue Type: New Feature
Affects Versions: 2.14.1
Reporter: Tomas Rohovsky
Add groups/getPosts endpint that covers following resource:
{code}
https://api.linkedin.com/v1/groups/{group-id}/posts
{code}
Similar functionality as this resource provides people/getPosts mapped to
{code}
https://api.linkedin.com/v1/people/~/group-memberships/{group-id}/posts
{code}
, but it requires role to be set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8464) Remove likeCompanyUpdate endpoint from camel-linkedin
Tomas Rohovsky created CAMEL-8464:
-
Summary: Remove likeCompanyUpdate endpoint from camel-linkedin
Key: CAMEL-8464
URL: https://issues.apache.org/jira/browse/CAMEL-8464
Project: Camel
Issue Type: Bug
Affects Versions: 2.14.1
Reporter: Tomas Rohovsky
Similar as CAMEL-8456. The underlying resource
{code}
/companies/{company-id}/updates/key={update-key}/is-liked
{code}
doesn't exist. It was probably added by mistake instead of
{code}
https://api.linkedin.com/v1/people/~/network/updates/key={update-key}/is-liked
{code}
mentioned in the documentation
https://developer-programs.linkedin.com/documents/commenting-and-liking-company-share.
The resource is already mapped to linkedin://people/likeUpdate so there is no
need to add it to companies prefixed endpoints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8456) Remove addCompanyUpdateComment endpoint from camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8456:
--
Summary: Remove addCompanyUpdateComment endpoint from camel-linkedin (was:
Remove endpoints for unexisting resources from camel-linkedin)
> Remove addCompanyUpdateComment endpoint from camel-linkedin
> ---
>
> Key: CAMEL-8456
> URL: https://issues.apache.org/jira/browse/CAMEL-8456
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>
> Underlying resource
> {code}
> /companies/{company-id}/updates/key={update-key}/update-comments
> {code}
> does not exist. It was probably added by mistake instead of
> {code}
> https://api.linkedin.com/v1/people/~/network/updates/key={update-key}/update-comments
> {code}
> mentioned in the documentation
> [https://developer-programs.linkedin.com/documents/commenting-and-liking-company-share].
> The resource is already mapped to linkedin://people/addUpdateComment so
> there is no need to add it to companies prefixed endpoints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8456) Remove endpoints for unexisting resources from camel-linkedin
[
https://issues.apache.org/jira/browse/CAMEL-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8456:
--
Summary: Remove endpoints for unexisting resources from camel-linkedin
(was: Remove addCompanyUpdateComment endpoint from camel-linkedin)
> Remove endpoints for unexisting resources from camel-linkedin
> -
>
> Key: CAMEL-8456
> URL: https://issues.apache.org/jira/browse/CAMEL-8456
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>
> Underlying resource
> {code}
> /companies/{company-id}/updates/key={update-key}/update-comments
> {code}
> does not exist. It was probably added by mistake instead of
> {code}
> https://api.linkedin.com/v1/people/~/network/updates/key={update-key}/update-comments
> {code}
> mentioned in the documentation
> [https://developer-programs.linkedin.com/documents/commenting-and-liking-company-share].
> The resource is already mapped to linkedin://people/addUpdateComment so
> there is no need to add it to companies prefixed endpoints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8458) camel-linkedin - public_profile_url option should be String
[
https://issues.apache.org/jira/browse/CAMEL-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351110#comment-14351110
]
Tomas Rohovsky commented on CAMEL-8458:
---
https://github.com/apache/camel/pull/426. It is rebased with a branch for
https://github.com/apache/camel/pull/425.
> camel-linkedin - public_profile_url option should be String
> ---
>
> Key: CAMEL-8458
> URL: https://issues.apache.org/jira/browse/CAMEL-8458
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>
> public_profile_url should be String instead of URI. The value of
> public_profile_url must be URL encoded what is not possible with URI.
> Currently I am getting
> {code}
> Error invoking getPersonByUrl: Unknown field {pub} in resource {Person}
> {code}
> for https://www.linkedin.com/pub/jboss-fuse-qe/b4/14b/b
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8458) camel-linkedin - public_profile_url option should be String
Tomas Rohovsky created CAMEL-8458:
-
Summary: camel-linkedin - public_profile_url option should be
String
Key: CAMEL-8458
URL: https://issues.apache.org/jira/browse/CAMEL-8458
Project: Camel
Issue Type: Bug
Affects Versions: 2.14.1
Reporter: Tomas Rohovsky
public_profile_url should be String instead of URI. The value of
public_profile_url must be URL encoded what is not possible with URI.
Currently I am getting
{code}
Error invoking getPersonByUrl: Unknown field {pub} in resource {Person}
{code}
for https://www.linkedin.com/pub/jboss-fuse-qe/b4/14b/b
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8457) Correct return types of some endpoints in camel-linkedin
[ https://issues.apache.org/jira/browse/CAMEL-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350923#comment-14350923 ] Tomas Rohovsky commented on CAMEL-8457: --- I also removed start and count options for getGroupMembershipSettings because they are only for collections of objects. The documentation for camel-linkedin should be corrected when the PR is merged. > Correct return types of some endpoints in camel-linkedin > > > Key: CAMEL-8457 > URL: https://issues.apache.org/jira/browse/CAMEL-8457 > Project: Camel > Issue Type: Bug >Affects Versions: 2.14.1 >Reporter: Tomas Rohovsky > > These endpoints return wrong type: > - companies/getCompanyUpdateComments - Comments/UpdateComments > - companies/getUpdateComments - Comments/UpdateComments > - people/getGroupMembershipSettings - GroupMemberships/GroupMembership > so it results in java.lang.ClassCastException. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8457) Correct return types of some endpoints in camel-linkedin
Tomas Rohovsky created CAMEL-8457: - Summary: Correct return types of some endpoints in camel-linkedin Key: CAMEL-8457 URL: https://issues.apache.org/jira/browse/CAMEL-8457 Project: Camel Issue Type: Bug Affects Versions: 2.14.1 Reporter: Tomas Rohovsky These endpoints return wrong type: - companies/getCompanyUpdateComments - Comments/UpdateComments - companies/getUpdateComments - Comments/UpdateComments - people/getGroupMembershipSettings - GroupMemberships/GroupMembership so it results in java.lang.ClassCastException. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8456) Remove addCompanyUpdateComment endpoint from camel-linkedin
Tomas Rohovsky created CAMEL-8456:
-
Summary: Remove addCompanyUpdateComment endpoint from
camel-linkedin
Key: CAMEL-8456
URL: https://issues.apache.org/jira/browse/CAMEL-8456
Project: Camel
Issue Type: Bug
Affects Versions: 2.14.1
Reporter: Tomas Rohovsky
Underlying resource
{code}
/companies/{company-id}/updates/key={update-key}/update-comments
{code}
does not exist. It was probably added by mistake instead of
{code}
https://api.linkedin.com/v1/people/~/network/updates/key={update-key}/update-comments
{code}
mentioned in the documentation
[https://developer-programs.linkedin.com/documents/commenting-and-liking-company-share].
The resource is already mapped to linkedin://people/addUpdateComment so there
is no need to add it to companies prefixed endpoints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8455) camel-linkedin - update_key option should be optional in getHistoricalStatusUpdateStatistics
[
https://issues.apache.org/jira/browse/CAMEL-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-8455:
--
Patch Info: Patch Available
> camel-linkedin - update_key option should be optional in
> getHistoricalStatusUpdateStatistics
>
>
> Key: CAMEL-8455
> URL: https://issues.apache.org/jira/browse/CAMEL-8455
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>
> update_key option should be optional in getHistoricalStatusUpdateStatistics
> endpoint. Currently it ends with an exception if the option is not specified:
> {{org.apache.camel.RuntimeCamelException: Missing properties for
> getHistoricalStatusUpdateStatistics, need one or more from \[end_timestamp,
> update_key\]}} See the LinkedIn API docs:
> https://developer-programs.linkedin.com/historical-company-statistics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8455) camel-linkedin - update_key option should be optional in getHistoricalStatusUpdateStatistics
[
https://issues.apache.org/jira/browse/CAMEL-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350785#comment-14350785
]
Tomas Rohovsky commented on CAMEL-8455:
---
https://github.com/apache/camel/pull/423
> camel-linkedin - update_key option should be optional in
> getHistoricalStatusUpdateStatistics
>
>
> Key: CAMEL-8455
> URL: https://issues.apache.org/jira/browse/CAMEL-8455
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>
> update_key option should be optional in getHistoricalStatusUpdateStatistics
> endpoint. Currently it ends with an exception if the option is not specified:
> {{org.apache.camel.RuntimeCamelException: Missing properties for
> getHistoricalStatusUpdateStatistics, need one or more from \[end_timestamp,
> update_key\]}} See the LinkedIn API docs:
> https://developer-programs.linkedin.com/historical-company-statistics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8455) camel-linkedin - update_key option should be optional in getHistoricalStatusUpdateStatistics
[
https://issues.apache.org/jira/browse/CAMEL-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350778#comment-14350778
]
Tomas Rohovsky commented on CAMEL-8455:
---
update_key was renamed to statistics_update_key due to conflict with update_key
option used in the other company endpoints where it is required
> camel-linkedin - update_key option should be optional in
> getHistoricalStatusUpdateStatistics
>
>
> Key: CAMEL-8455
> URL: https://issues.apache.org/jira/browse/CAMEL-8455
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.14.1
>Reporter: Tomas Rohovsky
>
> update_key option should be optional in getHistoricalStatusUpdateStatistics
> endpoint. Currently it ends with an exception if the option is not specified:
> {{org.apache.camel.RuntimeCamelException: Missing properties for
> getHistoricalStatusUpdateStatistics, need one or more from \[end_timestamp,
> update_key\]}} See the LinkedIn API docs:
> https://developer-programs.linkedin.com/historical-company-statistics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8455) camel-linkedin - update_key option should be optional in getHistoricalStatusUpdateStatistics
Tomas Rohovsky created CAMEL-8455:
-
Summary: camel-linkedin - update_key option should be optional in
getHistoricalStatusUpdateStatistics
Key: CAMEL-8455
URL: https://issues.apache.org/jira/browse/CAMEL-8455
Project: Camel
Issue Type: Bug
Affects Versions: 2.14.1
Reporter: Tomas Rohovsky
update_key option should be optional in getHistoricalStatusUpdateStatistics
endpoint. Currently it ends with an exception if the option is not specified:
{{org.apache.camel.RuntimeCamelException: Missing properties for
getHistoricalStatusUpdateStatistics, need one or more from \[end_timestamp,
update_key\]}} See the LinkedIn API docs:
https://developer-programs.linkedin.com/historical-company-statistics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8454) Correct a comment in files generated by camel-api-component-maven-plugin
[ https://issues.apache.org/jira/browse/CAMEL-8454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Rohovsky updated CAMEL-8454: -- Summary: Correct a comment in files generated by camel-api-component-maven-plugin (was: Correct a comment in files generated by camel-component-util-maven-plugin) > Correct a comment in files generated by camel-api-component-maven-plugin > > > Key: CAMEL-8454 > URL: https://issues.apache.org/jira/browse/CAMEL-8454 > Project: Camel > Issue Type: Task > Components: tooling >Affects Versions: 2.14.1 >Reporter: Tomas Rohovsky >Priority: Trivial > > Generted files contains original name of the plugin > (camel-component-util-maven-plugin) instead of > camel-api-component-maven-plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8454) Correct a comment in files generated by camel-component-util-maven-plugin
Tomas Rohovsky created CAMEL-8454: - Summary: Correct a comment in files generated by camel-component-util-maven-plugin Key: CAMEL-8454 URL: https://issues.apache.org/jira/browse/CAMEL-8454 Project: Camel Issue Type: Task Components: tooling Affects Versions: 2.14.1 Reporter: Tomas Rohovsky Priority: Trivial Generted files contains original name of the plugin (camel-component-util-maven-plugin) instead of camel-api-component-maven-plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7155) Incorrect implementation of the method StringHelper.hasStartToken()
[
https://issues.apache.org/jira/browse/CAMEL-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Rohovsky updated CAMEL-7155:
--
Priority: Minor (was: Major)
> Incorrect implementation of the method StringHelper.hasStartToken()
> ---
>
> Key: CAMEL-7155
> URL: https://issues.apache.org/jira/browse/CAMEL-7155
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.12.2
>Reporter: Tomas Rohovsky
>Priority: Minor
>
> From the semantic point of view the method hasStartToken() should return
> false in case of an expression without language specified, i.e. starting with
> "${".
> However, it is correct to return true in current usage of hasStartToken() in
> camel-core, i.e. checking if an expression is in simple language, since if
> the expression does not contain the language token, then it is a simple
> expression.
> The method calls for checking of simple language should be replaced with a
> newly created method isSimpleLanguage(String expression) that would check if
> the language is a simple expression, i.e. hasStartToken(expression, "simple")
> || expression.indexOf("${") >= 0.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CAMEL-7155) Incorrect implementation of the method StringHelper.hasStartToken()
Tomas Rohovsky created CAMEL-7155:
-
Summary: Incorrect implementation of the method
StringHelper.hasStartToken()
Key: CAMEL-7155
URL: https://issues.apache.org/jira/browse/CAMEL-7155
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.12.2
Reporter: Tomas Rohovsky
>From the semantic point of view the method hasStartToken() should return false
>in case of an expression without language specified, i.e. starting with "${".
However, it is correct to return true in current usage of hasStartToken() in
camel-core, i.e. checking if an expression is in simple language, since if the
expression does not contain the language token, then it is a simple expression.
The method calls for checking of simple language should be replaced with a
newly created method isSimpleLanguage(String expression) that would check if
the language is a simple expression, i.e. hasStartToken(expression, "simple")
|| expression.indexOf("${") >= 0.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
