[jira] [Comment Edited] (CAMEL-14440) Add Workday report as a service component.
[
https://issues.apache.org/jira/browse/CAMEL-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029602#comment-17029602
]
Dmitry Volodin edited comment on CAMEL-14440 at 2/4/20 6:41 AM:
Thanks for response, [~favalos]
I will change the common component syntax to the something like syntax =
{color:#008000}"workday:entity:path"{color}
to keep with the future functions support as we need to fit it to the 3.1.0
release. We could also add message queue support as described
[http://mrichen.github.io/wdlearn/message_queue/index.html]. It a best example
for polling consumer implementation.
You are welcome to extend this component with better functions. However
producer and consumer will require a tenant name setting via X-Tenant header,
as well as producer will have two possible operations GET and DELETE (get and
delete message from queue)
regards,
Dmitry
was (Author: dmvolod):
Thanks for response, [~favalos]
I will change the common component syntax to the something like syntax =
{color:#008000}"workday:entity:path"{color}
to keep with the future functions support as we need to fit it to the 3.1.0
release. We could also add message queue support as described
[here|[http://mrichen.github.io/wdlearn/message_queue/index.html]]. It a best
example for polling consumer implementation.
You are welcome to extend this component with better functions. However
producer and consumer will require a tenant name setting via X-Tenant header,
as well as producer will have two possible operations GET and DELETE (get and
delete message from queue)
regards,
Dmitry
> Add Workday report as a service component.
> --
>
> Key: CAMEL-14440
> URL: https://issues.apache.org/jira/browse/CAMEL-14440
> Project: Camel
> Issue Type: New Feature
>Reporter: Fernando Avalos
>Priority: Minor
> Fix For: 3.1.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Create a Workday component to consume Workday report as a service in Camel.
> The component must be ready to work with a Workday Client API for
> Integrations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14440) Add Workday report as a service component.
[
https://issues.apache.org/jira/browse/CAMEL-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029602#comment-17029602
]
Dmitry Volodin commented on CAMEL-14440:
Thanks for response, [~favalos]
I will change the common component syntax to the something like syntax =
{color:#008000}"workday:entity:path"{color}
to keep with the future functions support as we need to fit it to the 3.1.0
release. We could also add message queue support as described
[here|[http://mrichen.github.io/wdlearn/message_queue/index.html]]. It a best
example for polling consumer implementation.
You are welcome to extend this component with better functions. However
producer and consumer will require a tenant name setting via X-Tenant header,
as well as producer will have two possible operations GET and DELETE (get and
delete message from queue)
regards,
Dmitry
> Add Workday report as a service component.
> --
>
> Key: CAMEL-14440
> URL: https://issues.apache.org/jira/browse/CAMEL-14440
> Project: Camel
> Issue Type: New Feature
>Reporter: Fernando Avalos
>Priority: Minor
> Fix For: 3.1.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Create a Workday component to consume Workday report as a service in Camel.
> The component must be ready to work with a Workday Client API for
> Integrations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14482) Fix broken Javadoc links in the current documentation
[ https://issues.apache.org/jira/browse/CAMEL-14482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PRAVEEN updated CAMEL-14482: - Description: In the old version of the website, Javadoc used to get published at '[http://camel.apache.org/maven/current/*'] . Several pages in the current documentation (107 occurrances) still refers to the non existent Javadoc pages. A sample broken link highlighted below ([source doc page| https://camel.apache.org/manual/latest/processor.html]) !Screenshot 2020-02-04 at 00.02.02.png|width=523,height=300! The proposal is to fix these links, by pointing them to appropriate Javadoc hosted on [https://javadoc.io/] I am already working on this and shall send in a PR shortly. Can someone assign this task to me? Documentation pages with broken Javadoc links are below docs/components/modules/ROOT/pages/mock-component.adoc docs/components/modules/ROOT/pages/log-component.adoc docs/components/modules/ROOT/pages/scp-component.adoc docs/components/modules/ROOT/pages/jpa-component.adoc docs/components/modules/ROOT/pages/bean-component.adoc docs/components/modules/ROOT/pages/dataset-test-component.adoc docs/components/modules/ROOT/pages/xpath-language.adoc docs/components/modules/ROOT/pages/cdi.adoc docs/components/modules/ROOT/pages/cxfrs-component.adoc docs/components/modules/ROOT/pages/dataset-component.adoc docs/components/modules/ROOT/pages/stomp-component.adoc docs/user-manual/modules/ROOT/pages/camelcontext.adoc docs/user-manual/modules/ROOT/pages/type-converter.adoc docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc docs/user-manual/modules/ROOT/pages/faq/running-camel-standalone.adoc docs/user-manual/modules/ROOT/pages/jmx.adoc docs/user-manual/modules/ROOT/pages/lifecycle.adoc docs/user-manual/modules/ROOT/pages/endpoint.adoc docs/user-manual/modules/ROOT/pages/spring.adoc docs/user-manual/modules/ROOT/pages/processor.adoc docs/user-manual/modules/ROOT/pages/message-endpoint.adoc docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc docs/user-manual/modules/ROOT/pages/predicate.adoc docs/user-manual/modules/ROOT/pages/book-getting-started.adoc docs/user-manual/modules/ROOT/pages/process-eip.adoc docs/user-manual/modules/ROOT/pages/expression.adoc docs/user-manual/modules/ROOT/pages/architecture.adoc docs/user-manual/modules/ROOT/pages/injector.adoc docs/user-manual/modules/ROOT/pages/jndi.adoc docs/user-manual/modules/ROOT/pages/browsable-endpoint.adoc docs/user-manual/modules/ROOT/pages/transactional-client.adoc docs/user-manual/modules/ROOT/pages/rollback-eip.adoc docs/user-manual/modules/ROOT/pages/error-handler.adoc docs/user-manual/modules/ROOT/pages/exception-clause.adoc docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc docs/user-manual/modules/ROOT/pages/message.adoc docs/user-manual/modules/ROOT/pages/async.adoc was: In the old version of the website, Javadoc used to get published at '[http://camel.apache.org/maven/current/*'] . Several pages in the current documentation (107 occurrances) still refers to the non existent Javadoc pages. Sample broken link highlighted below !Screenshot 2020-02-04 at 00.02.02.png|width=523,height=300! The proposal is to fix these links, by pointing them to appropriate Javadoc hosted on [https://javadoc.io/] I am already working on this and shall send in a PR shortly. Can someone assign this task to me? Documentation pages with broken Javadoc links are below docs/components/modules/ROOT/pages/mock-component.adoc docs/components/modules/ROOT/pages/log-component.adoc docs/components/modules/ROOT/pages/scp-component.adoc docs/components/modules/ROOT/pages/jpa-component.adoc docs/components/modules/ROOT/pages/bean-component.adoc docs/components/modules/ROOT/pages/dataset-test-component.adoc docs/components/modules/ROOT/pages/xpath-language.adoc docs/components/modules/ROOT/pages/cdi.adoc docs/components/modules/ROOT/pages/cxfrs-component.adoc docs/components/modules/ROOT/pages/dataset-component.adoc docs/components/modules/ROOT/pages/stomp-component.adoc docs/user-manual/modules/ROOT/pages/camelcontext.adoc docs/user-manual/modules/ROOT/pages/type-converter.adoc docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc docs/user-manual/modules/ROOT/pages/faq/running-camel-standalone.adoc docs/user-manual/modules/ROOT/pages/jmx.adoc docs/user-manual/modules/ROOT/pages/lifecycle.adoc docs/user-manual/modules/ROOT/pages/endpoint.adoc docs/user-manual/modules/ROOT/pages/spring.adoc docs/user-manual/modules/ROOT/pages/processor.adoc docs/user-manual/modules/ROOT/pages/message-endpoint.adoc docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc docs/user-manual/modules/ROOT/pages/predicate.adoc docs/user-manual/modules/ROOT/pages/book-getting-started.adoc docs/user-manual/modules/ROOT/pages/process-eip.adoc
[jira] [Updated] (CAMEL-14482) Fix broken Javadoc links in the current documentation
[ https://issues.apache.org/jira/browse/CAMEL-14482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PRAVEEN updated CAMEL-14482: - Attachment: Screenshot 2020-02-04 at 00.02.02.png Description: In the old version of the website, Javadoc used to get published at '[http://camel.apache.org/maven/current/*'] . Several pages in the current documentation (107 occurrances) still refers to the non existent Javadoc pages. Sample broken link highlighted below !Screenshot 2020-02-04 at 00.02.02.png|width=523,height=300! The proposal is to fix these links, by pointing them to appropriate Javadoc hosted on [https://javadoc.io/] I am already working on this and shall send in a PR shortly. Can someone assign this task to me? Documentation pages with broken Javadoc links are below docs/components/modules/ROOT/pages/mock-component.adoc docs/components/modules/ROOT/pages/log-component.adoc docs/components/modules/ROOT/pages/scp-component.adoc docs/components/modules/ROOT/pages/jpa-component.adoc docs/components/modules/ROOT/pages/bean-component.adoc docs/components/modules/ROOT/pages/dataset-test-component.adoc docs/components/modules/ROOT/pages/xpath-language.adoc docs/components/modules/ROOT/pages/cdi.adoc docs/components/modules/ROOT/pages/cxfrs-component.adoc docs/components/modules/ROOT/pages/dataset-component.adoc docs/components/modules/ROOT/pages/stomp-component.adoc docs/user-manual/modules/ROOT/pages/camelcontext.adoc docs/user-manual/modules/ROOT/pages/type-converter.adoc docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc docs/user-manual/modules/ROOT/pages/faq/running-camel-standalone.adoc docs/user-manual/modules/ROOT/pages/jmx.adoc docs/user-manual/modules/ROOT/pages/lifecycle.adoc docs/user-manual/modules/ROOT/pages/endpoint.adoc docs/user-manual/modules/ROOT/pages/spring.adoc docs/user-manual/modules/ROOT/pages/processor.adoc docs/user-manual/modules/ROOT/pages/message-endpoint.adoc docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc docs/user-manual/modules/ROOT/pages/predicate.adoc docs/user-manual/modules/ROOT/pages/book-getting-started.adoc docs/user-manual/modules/ROOT/pages/process-eip.adoc docs/user-manual/modules/ROOT/pages/expression.adoc docs/user-manual/modules/ROOT/pages/architecture.adoc docs/user-manual/modules/ROOT/pages/injector.adoc docs/user-manual/modules/ROOT/pages/jndi.adoc docs/user-manual/modules/ROOT/pages/browsable-endpoint.adoc docs/user-manual/modules/ROOT/pages/transactional-client.adoc docs/user-manual/modules/ROOT/pages/rollback-eip.adoc docs/user-manual/modules/ROOT/pages/error-handler.adoc docs/user-manual/modules/ROOT/pages/exception-clause.adoc docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc docs/user-manual/modules/ROOT/pages/message.adoc docs/user-manual/modules/ROOT/pages/async.adoc was: In the old version of the website, Javadoc used to get published at '[http://camel.apache.org/maven/current/*'] . Several pages in the current documentation (107 occurrances) still refers to the non existent Javadoc pages. The proposal is to fix these links, by pointing them to appropriate Javadoc hosted on [https://javadoc.io/] I am already working on this and shall send in a PR shortly. Can someone assign this task to me? Documentation pages with broken Javadoc links are below docs/components/modules/ROOT/pages/mock-component.adoc docs/components/modules/ROOT/pages/log-component.adoc docs/components/modules/ROOT/pages/scp-component.adoc docs/components/modules/ROOT/pages/jpa-component.adoc docs/components/modules/ROOT/pages/bean-component.adoc docs/components/modules/ROOT/pages/dataset-test-component.adoc docs/components/modules/ROOT/pages/xpath-language.adoc docs/components/modules/ROOT/pages/cdi.adoc docs/components/modules/ROOT/pages/cxfrs-component.adoc docs/components/modules/ROOT/pages/dataset-component.adoc docs/components/modules/ROOT/pages/stomp-component.adoc docs/user-manual/modules/ROOT/pages/camelcontext.adoc docs/user-manual/modules/ROOT/pages/type-converter.adoc docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc docs/user-manual/modules/ROOT/pages/faq/running-camel-standalone.adoc docs/user-manual/modules/ROOT/pages/jmx.adoc docs/user-manual/modules/ROOT/pages/lifecycle.adoc docs/user-manual/modules/ROOT/pages/endpoint.adoc docs/user-manual/modules/ROOT/pages/spring.adoc docs/user-manual/modules/ROOT/pages/processor.adoc docs/user-manual/modules/ROOT/pages/message-endpoint.adoc docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc docs/user-manual/modules/ROOT/pages/predicate.adoc docs/user-manual/modules/ROOT/pages/book-getting-started.adoc docs/user-manual/modules/ROOT/pages/process-eip.adoc docs/user-manual/modules/ROOT/pages/expression.adoc docs/user-manual/modules/ROOT/pages/architecture.adoc
[jira] [Updated] (CAMEL-14482) Fix broken Javadoc links in the current documentation
[ https://issues.apache.org/jira/browse/CAMEL-14482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PRAVEEN updated CAMEL-14482: - Description: In the old version of the website, Javadoc used to get published at '[http://camel.apache.org/maven/current/*'] . Several pages in the current documentation (107 occurrances) still refers to the non existent Javadoc pages. The proposal is to fix these links, by pointing them to appropriate Javadoc hosted on [https://javadoc.io/] I am already working on this and shall send in a PR shortly. Can someone assign this task to me? Documentation pages with broken Javadoc links are below docs/components/modules/ROOT/pages/mock-component.adoc docs/components/modules/ROOT/pages/log-component.adoc docs/components/modules/ROOT/pages/scp-component.adoc docs/components/modules/ROOT/pages/jpa-component.adoc docs/components/modules/ROOT/pages/bean-component.adoc docs/components/modules/ROOT/pages/dataset-test-component.adoc docs/components/modules/ROOT/pages/xpath-language.adoc docs/components/modules/ROOT/pages/cdi.adoc docs/components/modules/ROOT/pages/cxfrs-component.adoc docs/components/modules/ROOT/pages/dataset-component.adoc docs/components/modules/ROOT/pages/stomp-component.adoc docs/user-manual/modules/ROOT/pages/camelcontext.adoc docs/user-manual/modules/ROOT/pages/type-converter.adoc docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc docs/user-manual/modules/ROOT/pages/faq/running-camel-standalone.adoc docs/user-manual/modules/ROOT/pages/jmx.adoc docs/user-manual/modules/ROOT/pages/lifecycle.adoc docs/user-manual/modules/ROOT/pages/endpoint.adoc docs/user-manual/modules/ROOT/pages/spring.adoc docs/user-manual/modules/ROOT/pages/processor.adoc docs/user-manual/modules/ROOT/pages/message-endpoint.adoc docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc docs/user-manual/modules/ROOT/pages/predicate.adoc docs/user-manual/modules/ROOT/pages/book-getting-started.adoc docs/user-manual/modules/ROOT/pages/process-eip.adoc docs/user-manual/modules/ROOT/pages/expression.adoc docs/user-manual/modules/ROOT/pages/architecture.adoc docs/user-manual/modules/ROOT/pages/injector.adoc docs/user-manual/modules/ROOT/pages/jndi.adoc docs/user-manual/modules/ROOT/pages/browsable-endpoint.adoc docs/user-manual/modules/ROOT/pages/transactional-client.adoc docs/user-manual/modules/ROOT/pages/rollback-eip.adoc docs/user-manual/modules/ROOT/pages/error-handler.adoc docs/user-manual/modules/ROOT/pages/exception-clause.adoc docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc docs/user-manual/modules/ROOT/pages/message.adoc docs/user-manual/modules/ROOT/pages/async.adoc was: In the old version of the website, Javadoc used to get published at '[http://camel.apache.org/maven/current/*'] . Several pages in the current documentation (107 occurrances) still refers to the non existent Javadoc pages. The proposal is to fix these links, by pointing them to appropriate Javadoc hosted on [https://javadoc.io/] Documentation pages with broken Javadoc links are below docs/components/modules/ROOT/pages/mock-component.adoc docs/components/modules/ROOT/pages/log-component.adoc docs/components/modules/ROOT/pages/scp-component.adoc docs/components/modules/ROOT/pages/jpa-component.adoc docs/components/modules/ROOT/pages/bean-component.adoc docs/components/modules/ROOT/pages/dataset-test-component.adoc docs/components/modules/ROOT/pages/xpath-language.adoc docs/components/modules/ROOT/pages/cdi.adoc docs/components/modules/ROOT/pages/cxfrs-component.adoc docs/components/modules/ROOT/pages/dataset-component.adoc docs/components/modules/ROOT/pages/stomp-component.adoc docs/user-manual/modules/ROOT/pages/camelcontext.adoc docs/user-manual/modules/ROOT/pages/type-converter.adoc docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc docs/user-manual/modules/ROOT/pages/faq/running-camel-standalone.adoc docs/user-manual/modules/ROOT/pages/jmx.adoc docs/user-manual/modules/ROOT/pages/lifecycle.adoc docs/user-manual/modules/ROOT/pages/endpoint.adoc docs/user-manual/modules/ROOT/pages/spring.adoc docs/user-manual/modules/ROOT/pages/processor.adoc docs/user-manual/modules/ROOT/pages/message-endpoint.adoc docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc docs/user-manual/modules/ROOT/pages/predicate.adoc docs/user-manual/modules/ROOT/pages/book-getting-started.adoc docs/user-manual/modules/ROOT/pages/process-eip.adoc docs/user-manual/modules/ROOT/pages/expression.adoc docs/user-manual/modules/ROOT/pages/architecture.adoc docs/user-manual/modules/ROOT/pages/injector.adoc docs/user-manual/modules/ROOT/pages/jndi.adoc docs/user-manual/modules/ROOT/pages/browsable-endpoint.adoc docs/user-manual/modules/ROOT/pages/transactional-client.adoc docs/user-manual/modules/ROOT/pages/rollback-eip.adoc
[jira] [Created] (CAMEL-14482) Fix broken Javadoc links in the current documentation
PRAVEEN created CAMEL-14482: Summary: Fix broken Javadoc links in the current documentation Key: CAMEL-14482 URL: https://issues.apache.org/jira/browse/CAMEL-14482 Project: Camel Issue Type: Sub-task Components: documentation Reporter: PRAVEEN In the old version of the website, Javadoc used to get published at '[http://camel.apache.org/maven/current/*'] . Several pages in the current documentation (107 occurrances) still refers to the non existent Javadoc pages. The proposal is to fix these links, by pointing them to appropriate Javadoc hosted on [https://javadoc.io/] Documentation pages with broken Javadoc links are below docs/components/modules/ROOT/pages/mock-component.adoc docs/components/modules/ROOT/pages/log-component.adoc docs/components/modules/ROOT/pages/scp-component.adoc docs/components/modules/ROOT/pages/jpa-component.adoc docs/components/modules/ROOT/pages/bean-component.adoc docs/components/modules/ROOT/pages/dataset-test-component.adoc docs/components/modules/ROOT/pages/xpath-language.adoc docs/components/modules/ROOT/pages/cdi.adoc docs/components/modules/ROOT/pages/cxfrs-component.adoc docs/components/modules/ROOT/pages/dataset-component.adoc docs/components/modules/ROOT/pages/stomp-component.adoc docs/user-manual/modules/ROOT/pages/camelcontext.adoc docs/user-manual/modules/ROOT/pages/type-converter.adoc docs/user-manual/modules/ROOT/pages/faq/how-does-the-camel-api-compare-to.adoc docs/user-manual/modules/ROOT/pages/faq/running-camel-standalone.adoc docs/user-manual/modules/ROOT/pages/jmx.adoc docs/user-manual/modules/ROOT/pages/lifecycle.adoc docs/user-manual/modules/ROOT/pages/endpoint.adoc docs/user-manual/modules/ROOT/pages/spring.adoc docs/user-manual/modules/ROOT/pages/processor.adoc docs/user-manual/modules/ROOT/pages/message-endpoint.adoc docs/user-manual/modules/ROOT/pages/dead-letter-channel.adoc docs/user-manual/modules/ROOT/pages/predicate.adoc docs/user-manual/modules/ROOT/pages/book-getting-started.adoc docs/user-manual/modules/ROOT/pages/process-eip.adoc docs/user-manual/modules/ROOT/pages/expression.adoc docs/user-manual/modules/ROOT/pages/architecture.adoc docs/user-manual/modules/ROOT/pages/injector.adoc docs/user-manual/modules/ROOT/pages/jndi.adoc docs/user-manual/modules/ROOT/pages/browsable-endpoint.adoc docs/user-manual/modules/ROOT/pages/transactional-client.adoc docs/user-manual/modules/ROOT/pages/rollback-eip.adoc docs/user-manual/modules/ROOT/pages/error-handler.adoc docs/user-manual/modules/ROOT/pages/exception-clause.adoc docs/user-manual/modules/ROOT/pages/eventDrivenConsumer-eip.adoc docs/user-manual/modules/ROOT/pages/message.adoc docs/user-manual/modules/ROOT/pages/async.adoc -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14481) camel-spring-boot: Remove camel-management to disable JMX by default
Pascal Schumacher created CAMEL-14481: - Summary: camel-spring-boot: Remove camel-management to disable JMX by default Key: CAMEL-14481 URL: https://issues.apache.org/jira/browse/CAMEL-14481 Project: Camel Issue Type: Improvement Components: camel-spring-boot Reporter: Pascal Schumacher Fix For: 3.1.0 Spring Boot 2.2 disables JMX by default (see: https://github.com/spring-projects/spring-boot/issues/16090, https://github.com/spring-projects/spring-boot/issues/16498). We should follow suit and remove the camel-management compile dependency from camel-spring-boot to disable JMX by default. See discussion on the mailing list: http://mail-archives.apache.org/mod_mbox/camel-dev/202002.mbox/%3Caa3aef09-5ff9-d60b-7ef4-2c4c9c30153f%40gmx.net%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14440) Add Workday report as a service component.
[
https://issues.apache.org/jira/browse/CAMEL-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029326#comment-17029326
]
Fernando Avalos commented on CAMEL-14440:
-
Hi [~dmvolod],
There is room to extend this component, I started with RAAS because is the most
common way to extract information from Workday. But Workday also have a REST
API, I am planning at some point to include those endpoints in the component.
It would be good to have something like:
workday:report:uri
For the Rest endpoint for Worker in the future we can use:
workday:worker:\{id}
What are your thoughts?
Thanks,
> Add Workday report as a service component.
> --
>
> Key: CAMEL-14440
> URL: https://issues.apache.org/jira/browse/CAMEL-14440
> Project: Camel
> Issue Type: New Feature
>Reporter: Fernando Avalos
>Priority: Minor
> Fix For: 3.1.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Create a Workday component to consume Workday report as a service in Camel.
> The component must be ready to work with a Workday Client API for
> Integrations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14479) camel-core - Move RuntimeCamelContext to separate JAR
[ https://issues.apache.org/jira/browse/CAMEL-14479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14479. - Resolution: Duplicate > camel-core - Move RuntimeCamelContext to separate JAR > - > > Key: CAMEL-14479 > URL: https://issues.apache.org/jira/browse/CAMEL-14479 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > It would be good to move runtime camel catalog out of camel-core and have it > in its own JAR. Or complete get rid of it. > There are some components that use dynamic send aware that uses it. But we > can find a way to do this in another way as they use only catalog details > from their own component. > And the runtime catalog details on camel-core via JMX are not so useable. > Also this avoids having dependencies on tooling-model JARs in camel-core. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14480) camel-salesforce - Duplicate Properties between Relationship Name and Child Relationship Name
[ https://issues.apache.org/jira/browse/CAMEL-14480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14480: Summary: camel-salesforce - Duplicate Properties between Relationship Name and Child Relationship Name (was: Duplicate Properties between Relationship Name and Child Relationship Name) > camel-salesforce - Duplicate Properties between Relationship Name and Child > Relationship Name > - > > Key: CAMEL-14480 > URL: https://issues.apache.org/jira/browse/CAMEL-14480 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.0.1 >Reporter: Dhimitraq Jorgji >Priority: Major > Fix For: Future > > > When two SObjects have a one-to-one relationship and one of the objects in > that relationship does not have a plural form the resulting DTO has duplicate > properties causing compilation to fail. Similarly when the SObject with no > plural form has a hierarchical child parent relationship with itself. > > EX: *Equipment__c_* _has a relationship with *Yard_Slot*__*_c*__, were they > both lookup to each other for a 1-to-1 relationship. *Yard_Slot_*_*_c.java_* > _DTO has duplicate properties because both its Relationship **and its Child > Relationship are named *Equipment*_*_r*. > > EX2: *Equipment__c_* _has a parent/child relationship with itself causing > both the Parent and Child relationship names to be *Equipment*_*_r.* > > **Salesforce allows and handles both these scenarios properly, however the > resulting DTO classes do not compile because of the duplicate properties and > duplicate getters. > > An easy fix would be to always append the suffix *List* on child relationship > properties in DTO. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14480) camel-salesforce - Duplicate Properties between Relationship Name and Child Relationship Name
[ https://issues.apache.org/jira/browse/CAMEL-14480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14480: Fix Version/s: (was: Future) 3.x > camel-salesforce - Duplicate Properties between Relationship Name and Child > Relationship Name > - > > Key: CAMEL-14480 > URL: https://issues.apache.org/jira/browse/CAMEL-14480 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.0.1 >Reporter: Dhimitraq Jorgji >Priority: Major > Fix For: 3.x > > > When two SObjects have a one-to-one relationship and one of the objects in > that relationship does not have a plural form the resulting DTO has duplicate > properties causing compilation to fail. Similarly when the SObject with no > plural form has a hierarchical child parent relationship with itself. > > EX: *Equipment__c_* _has a relationship with *Yard_Slot*__*_c*__, were they > both lookup to each other for a 1-to-1 relationship. *Yard_Slot_*_*_c.java_* > _DTO has duplicate properties because both its Relationship **and its Child > Relationship are named *Equipment*_*_r*. > > EX2: *Equipment__c_* _has a parent/child relationship with itself causing > both the Parent and Child relationship names to be *Equipment*_*_r.* > > **Salesforce allows and handles both these scenarios properly, however the > resulting DTO classes do not compile because of the duplicate properties and > duplicate getters. > > An easy fix would be to always append the suffix *List* on child relationship > properties in DTO. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14480) Duplicate Properties between Relationship Name and Child Relationship Name
[ https://issues.apache.org/jira/browse/CAMEL-14480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhimitraq Jorgji updated CAMEL-14480: - Description: When two SObjects have a one-to-one relationship and one of the objects in that relationship does not have a plural form the resulting DTO has duplicate properties causing compilation to fail. Similarly when the SObject with no plural form has a hierarchical child parent relationship with itself. EX: *Equipment__c_* _has a relationship with *Yard_Slot_*_*_c_*_, were they both lookup to each other for a 1-to-1 relationship. *Yard_Slot*_*_c.java_* _DTO has duplicate properties because both its Relationship **and its Child Relationship are named *Equipment*_*_r*. EX2: *Equipment__c_* _has a parent/child relationship with itself causing both the Parent and Child relationship names to be *Equipment*_*_r.* **Salesforce allows and handles both these scenarios properly, however the resulting DTO classes do not compile because of the duplicate properties and duplicate getters. An easy fix would be to always append the suffix *List* on child relationship properties in DTO. was: When two SObjects have a one-to-one relationship and one of the objects in that relationship does not have a plural form the resulting DTO has duplicate properties causing compilation to fail. Similarly when the SObject with no plural form has a hierarchical child parent relationship with itself. EX: *Equipment__c* has a relationship with *Yard_Slot__c*, were they both lookup to each other for a 1-to-1 relationship. *Yard_Slot__c.java* DTO has duplicate properties because both its Relationship **and its Child Relationship are named *Equipment__r*. EX2: *Equipment__c* has a parent/child relationship with itself causing both the Parent and Child relationship names to be *Equipment__r.* **Salesforce allows and handles both these scenarios properly, however the resulting DTO classes do not compile because of the duplicate properties and duplicate getters. An easy fix would be to always append the suffix *List* on child relationship properties in DTO. > Duplicate Properties between Relationship Name and Child Relationship Name > -- > > Key: CAMEL-14480 > URL: https://issues.apache.org/jira/browse/CAMEL-14480 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.0.1 >Reporter: Dhimitraq Jorgji >Priority: Major > Fix For: Future > > > When two SObjects have a one-to-one relationship and one of the objects in > that relationship does not have a plural form the resulting DTO has duplicate > properties causing compilation to fail. Similarly when the SObject with no > plural form has a hierarchical child parent relationship with itself. > > EX: *Equipment__c_* _has a relationship with *Yard_Slot_*_*_c_*_, were they > both lookup to each other for a 1-to-1 relationship. *Yard_Slot*_*_c.java_* > _DTO has duplicate properties because both its Relationship **and its Child > Relationship are named *Equipment*_*_r*. > > EX2: *Equipment__c_* _has a parent/child relationship with itself causing > both the Parent and Child relationship names to be *Equipment*_*_r.* > > **Salesforce allows and handles both these scenarios properly, however the > resulting DTO classes do not compile because of the duplicate properties and > duplicate getters. > > An easy fix would be to always append the suffix *List* on child relationship > properties in DTO. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14480) Duplicate Properties between Relationship Name and Child Relationship Name
[ https://issues.apache.org/jira/browse/CAMEL-14480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhimitraq Jorgji updated CAMEL-14480: - Description: When two SObjects have a one-to-one relationship and one of the objects in that relationship does not have a plural form the resulting DTO has duplicate properties causing compilation to fail. Similarly when the SObject with no plural form has a hierarchical child parent relationship with itself. EX: *Equipment__c_* _has a relationship with *Yard_Slot*__*_c*__, were they both lookup to each other for a 1-to-1 relationship. *Yard_Slot_*_*_c.java_* _DTO has duplicate properties because both its Relationship **and its Child Relationship are named *Equipment*_*_r*. EX2: *Equipment__c_* _has a parent/child relationship with itself causing both the Parent and Child relationship names to be *Equipment*_*_r.* **Salesforce allows and handles both these scenarios properly, however the resulting DTO classes do not compile because of the duplicate properties and duplicate getters. An easy fix would be to always append the suffix *List* on child relationship properties in DTO. was: When two SObjects have a one-to-one relationship and one of the objects in that relationship does not have a plural form the resulting DTO has duplicate properties causing compilation to fail. Similarly when the SObject with no plural form has a hierarchical child parent relationship with itself. EX: *Equipment__c_* _has a relationship with *Yard_Slot_*_*_c_*_, were they both lookup to each other for a 1-to-1 relationship. *Yard_Slot*_*_c.java_* _DTO has duplicate properties because both its Relationship **and its Child Relationship are named *Equipment*_*_r*. EX2: *Equipment__c_* _has a parent/child relationship with itself causing both the Parent and Child relationship names to be *Equipment*_*_r.* **Salesforce allows and handles both these scenarios properly, however the resulting DTO classes do not compile because of the duplicate properties and duplicate getters. An easy fix would be to always append the suffix *List* on child relationship properties in DTO. > Duplicate Properties between Relationship Name and Child Relationship Name > -- > > Key: CAMEL-14480 > URL: https://issues.apache.org/jira/browse/CAMEL-14480 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.0.1 >Reporter: Dhimitraq Jorgji >Priority: Major > Fix For: Future > > > When two SObjects have a one-to-one relationship and one of the objects in > that relationship does not have a plural form the resulting DTO has duplicate > properties causing compilation to fail. Similarly when the SObject with no > plural form has a hierarchical child parent relationship with itself. > > EX: *Equipment__c_* _has a relationship with *Yard_Slot*__*_c*__, were they > both lookup to each other for a 1-to-1 relationship. *Yard_Slot_*_*_c.java_* > _DTO has duplicate properties because both its Relationship **and its Child > Relationship are named *Equipment*_*_r*. > > EX2: *Equipment__c_* _has a parent/child relationship with itself causing > both the Parent and Child relationship names to be *Equipment*_*_r.* > > **Salesforce allows and handles both these scenarios properly, however the > resulting DTO classes do not compile because of the duplicate properties and > duplicate getters. > > An easy fix would be to always append the suffix *List* on child relationship > properties in DTO. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14480) Duplicate Properties between Relationship Name and Child Relationship Name
Dhimitraq Jorgji created CAMEL-14480: Summary: Duplicate Properties between Relationship Name and Child Relationship Name Key: CAMEL-14480 URL: https://issues.apache.org/jira/browse/CAMEL-14480 Project: Camel Issue Type: Bug Components: camel-salesforce Affects Versions: 3.0.1 Reporter: Dhimitraq Jorgji Fix For: Future When two SObjects have a one-to-one relationship and one of the objects in that relationship does not have a plural form the resulting DTO has duplicate properties causing compilation to fail. Similarly when the SObject with no plural form has a hierarchical child parent relationship with itself. EX: *Equipment__c* has a relationship with *Yard_Slot__c*, were they both lookup to each other for a 1-to-1 relationship. *Yard_Slot__c.java* DTO has duplicate properties because both its Relationship **and its Child Relationship are named *Equipment__r*. EX2: *Equipment__c* has a parent/child relationship with itself causing both the Parent and Child relationship names to be *Equipment__r.* **Salesforce allows and handles both these scenarios properly, however the resulting DTO classes do not compile because of the duplicate properties and duplicate getters. An easy fix would be to always append the suffix *List* on child relationship properties in DTO. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14477) camel-netty - Disable object serialization
[ https://issues.apache.org/jira/browse/CAMEL-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14477: Summary: camel-netty - Disable object serialization (was: Disable object serialization) > camel-netty - Disable object serialization > -- > > Key: CAMEL-14477 > URL: https://issues.apache.org/jira/browse/CAMEL-14477 > Project: Camel > Issue Type: Improvement > Components: camel-netty >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > Time Spent: 20m > Remaining Estimate: 0h > > For the camel-netty component, we should disallow object serialization by > default, by removing the object encoders/decoders. If the user really wants > object serialization, they can configure custom encoders/decoders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14479) camel-core - Move RuntimeCamelContext to separate JAR
Claus Ibsen created CAMEL-14479: --- Summary: camel-core - Move RuntimeCamelContext to separate JAR Key: CAMEL-14479 URL: https://issues.apache.org/jira/browse/CAMEL-14479 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 3.x It would be good to move runtime camel catalog out of camel-core and have it in its own JAR. Or complete get rid of it. There are some components that use dynamic send aware that uses it. But we can find a way to do this in another way as they use only catalog details from their own component. And the runtime catalog details on camel-core via JMX are not so useable. Also this avoids having dependencies on tooling-model JARs in camel-core. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14478) Create an AWS-KMS component based on SDK v2
Andrea Cosentino created CAMEL-14478: Summary: Create an AWS-KMS component based on SDK v2 Key: CAMEL-14478 URL: https://issues.apache.org/jira/browse/CAMEL-14478 Project: Camel Issue Type: Sub-task Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.1.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14464) Create an AWS-MSK component based on SDK v2
[ https://issues.apache.org/jira/browse/CAMEL-14464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-14464. -- Resolution: Fixed > Create an AWS-MSK component based on SDK v2 > --- > > Key: CAMEL-14464 > URL: https://issues.apache.org/jira/browse/CAMEL-14464 > Project: Camel > Issue Type: Sub-task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14468) Add support for classification in camel-weka
[ https://issues.apache.org/jira/browse/CAMEL-14468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14468. - Fix Version/s: (was: 3.x) 3.1.0 Resolution: Fixed > Add support for classification in camel-weka > > > Key: CAMEL-14468 > URL: https://issues.apache.org/jira/browse/CAMEL-14468 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.1.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14468) Add support for classification in camel-weka
[ https://issues.apache.org/jira/browse/CAMEL-14468?focusedWorklogId=381030=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-381030 ] ASF GitHub Bot logged work on CAMEL-14468: -- Author: ASF GitHub Bot Created on: 03/Feb/20 15:29 Start Date: 03/Feb/20 15:29 Worklog Time Spent: 10m Work Description: davsclaus commented on pull request #3536: [CAMEL-14468] Add support for classification in camel-weka URL: https://github.com/apache/camel/pull/3536 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 381030) Time Spent: 40m (was: 0.5h) > Add support for classification in camel-weka > > > Key: CAMEL-14468 > URL: https://issues.apache.org/jira/browse/CAMEL-14468 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.x > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14464) Create an AWS-MSK component based on SDK v2
[ https://issues.apache.org/jira/browse/CAMEL-14464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-14464: - Summary: Create an AWS-MSK component based on SDK v2 (was: Create an AWS-MKS component based on SDK v2) > Create an AWS-MSK component based on SDK v2 > --- > > Key: CAMEL-14464 > URL: https://issues.apache.org/jira/browse/CAMEL-14464 > Project: Camel > Issue Type: Sub-task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14475) camel-core - Make loading XML pluggable via SPI
[ https://issues.apache.org/jira/browse/CAMEL-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14475. - Resolution: Fixed > camel-core - Make loading XML pluggable via SPI > --- > > Key: CAMEL-14475 > URL: https://issues.apache.org/jira/browse/CAMEL-14475 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > So we can use the camel-xml-io with camel-main etc to load XML routes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14475) camel-core - Make loading XML pluggable via SPI
[ https://issues.apache.org/jira/browse/CAMEL-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028928#comment-17028928 ] Claus Ibsen commented on CAMEL-14475: - Just add camel-xml-io to the classpath and Camel will use it. Notice this is not for spring xml with as that is still spring parsing. And ditto for blueprint etc. But for camel only xml in xml > camel-core - Make loading XML pluggable via SPI > --- > > Key: CAMEL-14475 > URL: https://issues.apache.org/jira/browse/CAMEL-14475 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > So we can use the camel-xml-io with camel-main etc to load XML routes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14477) Disable object serialization
[ https://issues.apache.org/jira/browse/CAMEL-14477?focusedWorklogId=380934=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-380934 ] ASF GitHub Bot logged work on CAMEL-14477: -- Author: ASF GitHub Bot Created on: 03/Feb/20 13:17 Start Date: 03/Feb/20 13:17 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #3537: CAMEL-14477 - Disable object serialization URL: https://github.com/apache/camel/pull/3537 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 380934) Time Spent: 20m (was: 10m) > Disable object serialization > > > Key: CAMEL-14477 > URL: https://issues.apache.org/jira/browse/CAMEL-14477 > Project: Camel > Issue Type: Improvement > Components: camel-netty >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > Time Spent: 20m > Remaining Estimate: 0h > > For the camel-netty component, we should disallow object serialization by > default, by removing the object encoders/decoders. If the user really wants > object serialization, they can configure custom encoders/decoders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14477) Disable object serialization
[ https://issues.apache.org/jira/browse/CAMEL-14477?focusedWorklogId=380900=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-380900 ] ASF GitHub Bot logged work on CAMEL-14477: -- Author: ASF GitHub Bot Created on: 03/Feb/20 11:27 Start Date: 03/Feb/20 11:27 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #3537: CAMEL-14477 - Disable object serialization URL: https://github.com/apache/camel/pull/3537 For backwards compatibility reasons, it falls back to allowing String serialization only. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 380900) Remaining Estimate: 0h Time Spent: 10m > Disable object serialization > > > Key: CAMEL-14477 > URL: https://issues.apache.org/jira/browse/CAMEL-14477 > Project: Camel > Issue Type: Improvement > Components: camel-netty >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > Time Spent: 10m > Remaining Estimate: 0h > > For the camel-netty component, we should disallow object serialization by > default, by removing the object encoders/decoders. If the user really wants > object serialization, they can configure custom encoders/decoders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14477) Disable object serialization
Colm O hEigeartaigh created CAMEL-14477: --- Summary: Disable object serialization Key: CAMEL-14477 URL: https://issues.apache.org/jira/browse/CAMEL-14477 Project: Camel Issue Type: Improvement Components: camel-netty Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.1.0, 3.0.2, 2.25.1 For the camel-netty component, we should disallow object serialization by default, by removing the object encoders/decoders. If the user really wants object serialization, they can configure custom encoders/decoders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14476) Able to extend workday component for futher entities support
Dmitry Volodin created CAMEL-14476: -- Summary: Able to extend workday component for futher entities support Key: CAMEL-14476 URL: https://issues.apache.org/jira/browse/CAMEL-14476 Project: Camel Issue Type: Sub-task Components: camel-workday Affects Versions: 3.x Reporter: Dmitry Volodin Assignee: Dmitry Volodin Fix For: 3.1.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14463) Create an AWS-MQ component based on SDK v2
[ https://issues.apache.org/jira/browse/CAMEL-14463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-14463. -- Resolution: Fixed > Create an AWS-MQ component based on SDK v2 > -- > > Key: CAMEL-14463 > URL: https://issues.apache.org/jira/browse/CAMEL-14463 > Project: Camel > Issue Type: Sub-task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14475) camel-core - Make loading XML pluggable via SPI
[ https://issues.apache.org/jira/browse/CAMEL-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-14475: --- Assignee: Claus Ibsen > camel-core - Make loading XML pluggable via SPI > --- > > Key: CAMEL-14475 > URL: https://issues.apache.org/jira/browse/CAMEL-14475 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > > So we can use the camel-xml-io with camel-main etc to load XML routes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14475) camel-core - Make loading XML pluggable via SPI
Claus Ibsen created CAMEL-14475: --- Summary: camel-core - Make loading XML pluggable via SPI Key: CAMEL-14475 URL: https://issues.apache.org/jira/browse/CAMEL-14475 Project: Camel Issue Type: New Feature Components: camel-core Reporter: Claus Ibsen Fix For: 3.1.0 So we can use the camel-xml-io with camel-main etc to load XML routes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14440) Add Workday report as a service component.
[ https://issues.apache.org/jira/browse/CAMEL-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028826#comment-17028826 ] Andrea Cosentino commented on CAMEL-14440: -- I'm fine with multiple entities, I'd just would like to introduce the new syntax before 3.1.0 > Add Workday report as a service component. > -- > > Key: CAMEL-14440 > URL: https://issues.apache.org/jira/browse/CAMEL-14440 > Project: Camel > Issue Type: New Feature >Reporter: Fernando Avalos >Priority: Minor > Fix For: 3.1.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Create a Workday component to consume Workday report as a service in Camel. > The component must be ready to work with a Workday Client API for > Integrations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14440) Add Workday report as a service component.
[
https://issues.apache.org/jira/browse/CAMEL-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028822#comment-17028822
]
Dmitry Volodin commented on CAMEL-14440:
[~favalos] thanks a lot for component adding
Do you have a plans for another integration or Workday entities type to be
adding. If yes and and it's possible it would be nice to have a two options for
better component using in the future:
* rename this producer and component to WorkdayReport...
* or have a prefix type on the Endpoint level like syntax =
{color:#008000}"workday:report:uri"{color}
I can take care about this but don't have a real workday instance for testing.
[~acosentino] what do you think about it?
> Add Workday report as a service component.
> --
>
> Key: CAMEL-14440
> URL: https://issues.apache.org/jira/browse/CAMEL-14440
> Project: Camel
> Issue Type: New Feature
>Reporter: Fernando Avalos
>Priority: Minor
> Fix For: 3.1.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Create a Workday component to consume Workday report as a service in Camel.
> The component must be ready to work with a Workday Client API for
> Integrations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14474) Dead link in "Message Exchange" doc to "Exchange" doc
[ https://issues.apache.org/jira/browse/CAMEL-14474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14474: Priority: Trivial (was: Major) > Dead link in "Message Exchange" doc to "Exchange" doc > - > > Key: CAMEL-14474 > URL: https://issues.apache.org/jira/browse/CAMEL-14474 > Project: Camel > Issue Type: Task > Components: website >Reporter: Aurélien Pupier >Priority: Trivial > > in page, https://camel.apache.org/manual/latest/exchange.html > link to > http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html > which doesn't exist. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14474) Dead link in "Message Exchange" doc to "Exchange" doc
[ https://issues.apache.org/jira/browse/CAMEL-14474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14474: Issue Type: Task (was: Bug) > Dead link in "Message Exchange" doc to "Exchange" doc > - > > Key: CAMEL-14474 > URL: https://issues.apache.org/jira/browse/CAMEL-14474 > Project: Camel > Issue Type: Task > Components: website >Reporter: Aurélien Pupier >Priority: Major > > in page, https://camel.apache.org/manual/latest/exchange.html > link to > http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html > which doesn't exist. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14474) Dead link in "Message Exchange" doc to "Exchange" doc
[ https://issues.apache.org/jira/browse/CAMEL-14474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14474. - Fix Version/s: 3.1.0 Resolution: Fixed > Dead link in "Message Exchange" doc to "Exchange" doc > - > > Key: CAMEL-14474 > URL: https://issues.apache.org/jira/browse/CAMEL-14474 > Project: Camel > Issue Type: Task > Components: website >Reporter: Aurélien Pupier >Priority: Trivial > Fix For: 3.1.0 > > > in page, https://camel.apache.org/manual/latest/exchange.html > link to > http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html > which doesn't exist. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14474) Dead link in "Message Exchange" doc to "Exchange" doc
Aurélien Pupier created CAMEL-14474: --- Summary: Dead link in "Message Exchange" doc to "Exchange" doc Key: CAMEL-14474 URL: https://issues.apache.org/jira/browse/CAMEL-14474 Project: Camel Issue Type: Bug Components: website Reporter: Aurélien Pupier in page, https://camel.apache.org/manual/latest/exchange.html link to http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html which doesn't exist. -- This message was sent by Atlassian Jira (v8.3.4#803005)
