[jira] [Created] (CAMEL-17926) Spring Boot related documentation issues
Zoran Regvart created CAMEL-17926:
-
Summary: Spring Boot related documentation issues
Key: CAMEL-17926
URL: https://issues.apache.org/jira/browse/CAMEL-17926
Project: Camel
Issue Type: Bug
Components: camel-spring-boot-starters, documentation
Affects Versions: 3.17.0
Reporter: Zoran Regvart
During the recent troubleshooting of the differences between the documentation
in Camel Spring Boot and Camel I've identified some long standing issues with
the documentation.
# To appease the referential integrity checks a placeholder [springdoc
component
|https://github.com/apache/camel/blob/04999556a32af90bd40548f04f89c215a193d8e6/components/camel-openapi-java/src/main/docs/springdoc.adoc]
documentation was created. This should be removed and the SpringDoc Starter
documentation should remain only visible via the Camel Spring Boot
documentation.
# DSLs in Camel do not include the Camel Spring Boot configuration snippet
like the component documentation has. It should be added to the DSLs as they
have starters much like the component documentation it includes now.
# DSLs in Camel do not have the {{camel-spring-boot-name}} attribute, it
should be set for the referential integrity to notice issues other than the
mismatch in component vs starter counts.
# Camel metadata JSON (in {{{}src/main/docs{}}}) is missing for debug,
cloudevents and DSLs. It was manually copied over from the Camel project in
[this
commit|https://github.com/apache/camel-spring-boot/commit/503b25ce7024e71430a426badc828d76fe5eb345].
Automation should be done to make sure those are present and updated with
changes in the Camel repository.
# DSL documentation doesn't appear in the Camel Spring Boot starter list page.
It should be added, most likely as a separate section.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Work stopped] (CAMEL-12866) camel-restdsl-swagger-plugin - Include api-properties from swagger file
[
https://issues.apache.org/jira/browse/CAMEL-12866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-12866 stopped by Zoran Regvart.
-
> camel-restdsl-swagger-plugin - Include api-properties from swagger file
> ---
>
> Key: CAMEL-12866
> URL: https://issues.apache.org/jira/browse/CAMEL-12866
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: Future
>
>
> The camel-restdsl-swagger-plugin should include additional meta-information
> from an OpenAPI/Swagger definition and add them to the generated code, f.e.
> from the following blocks (info, license, tags) :
> "info":{
> "description":"A description",
> "version":"1.0.0",
> "title":"A title",
> "termsOfService":"http://myhost.com/terms/;,
> "contact":{
> "email":"apit...@myhost.com"
> },
> "license":{
> "name":"Apache 2.0",
> "url":"http://www.apache.org/licenses/LICENSE-2.0.html;
> }
> },
> "tags":[]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-12866) camel-restdsl-swagger-plugin - Include api-properties from swagger file
[
https://issues.apache.org/jira/browse/CAMEL-12866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-12866:
--
Labels: help-wanted (was: )
> camel-restdsl-swagger-plugin - Include api-properties from swagger file
> ---
>
> Key: CAMEL-12866
> URL: https://issues.apache.org/jira/browse/CAMEL-12866
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Priority: Minor
> Labels: help-wanted
> Fix For: Future
>
>
> The camel-restdsl-swagger-plugin should include additional meta-information
> from an OpenAPI/Swagger definition and add them to the generated code, f.e.
> from the following blocks (info, license, tags) :
> "info":{
> "description":"A description",
> "version":"1.0.0",
> "title":"A title",
> "termsOfService":"http://myhost.com/terms/;,
> "contact":{
> "email":"apit...@myhost.com"
> },
> "license":{
> "name":"Apache 2.0",
> "url":"http://www.apache.org/licenses/LICENSE-2.0.html;
> }
> },
> "tags":[]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (CAMEL-12866) camel-restdsl-swagger-plugin - Include api-properties from swagger file
[
https://issues.apache.org/jira/browse/CAMEL-12866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart reassigned CAMEL-12866:
-
Assignee: Zoran Regvart
> camel-restdsl-swagger-plugin - Include api-properties from swagger file
> ---
>
> Key: CAMEL-12866
> URL: https://issues.apache.org/jira/browse/CAMEL-12866
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: Future
>
>
> The camel-restdsl-swagger-plugin should include additional meta-information
> from an OpenAPI/Swagger definition and add them to the generated code, f.e.
> from the following blocks (info, license, tags) :
> "info":{
> "description":"A description",
> "version":"1.0.0",
> "title":"A title",
> "termsOfService":"http://myhost.com/terms/;,
> "contact":{
> "email":"apit...@myhost.com"
> },
> "license":{
> "name":"Apache 2.0",
> "url":"http://www.apache.org/licenses/LICENSE-2.0.html;
> }
> },
> "tags":[]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (CAMEL-12866) camel-restdsl-swagger-plugin - Include api-properties from swagger file
[
https://issues.apache.org/jira/browse/CAMEL-12866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart reassigned CAMEL-12866:
-
Assignee: (was: Zoran Regvart)
> camel-restdsl-swagger-plugin - Include api-properties from swagger file
> ---
>
> Key: CAMEL-12866
> URL: https://issues.apache.org/jira/browse/CAMEL-12866
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Priority: Minor
> Fix For: Future
>
>
> The camel-restdsl-swagger-plugin should include additional meta-information
> from an OpenAPI/Swagger definition and add them to the generated code, f.e.
> from the following blocks (info, license, tags) :
> "info":{
> "description":"A description",
> "version":"1.0.0",
> "title":"A title",
> "termsOfService":"http://myhost.com/terms/;,
> "contact":{
> "email":"apit...@myhost.com"
> },
> "license":{
> "name":"Apache 2.0",
> "url":"http://www.apache.org/licenses/LICENSE-2.0.html;
> }
> },
> "tags":[]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (CAMEL-12866) camel-restdsl-swagger-plugin - Include api-properties from swagger file
[
https://issues.apache.org/jira/browse/CAMEL-12866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart reassigned CAMEL-12866:
-
Assignee: (was: Zoran Regvart)
> camel-restdsl-swagger-plugin - Include api-properties from swagger file
> ---
>
> Key: CAMEL-12866
> URL: https://issues.apache.org/jira/browse/CAMEL-12866
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 2.22.1
>Reporter: Jochen Cordes
>Priority: Minor
> Fix For: Future
>
>
> The camel-restdsl-swagger-plugin should include additional meta-information
> from an OpenAPI/Swagger definition and add them to the generated code, f.e.
> from the following blocks (info, license, tags) :
> "info":{
> "description":"A description",
> "version":"1.0.0",
> "title":"A title",
> "termsOfService":"http://myhost.com/terms/;,
> "contact":{
> "email":"apit...@myhost.com"
> },
> "license":{
> "name":"Apache 2.0",
> "url":"http://www.apache.org/licenses/LICENSE-2.0.html;
> }
> },
> "tags":[]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17608) camel-salesforce: allow overriding sobject name when using DTOs
[
https://issues.apache.org/jira/browse/CAMEL-17608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488078#comment-17488078
]
Zoran Regvart commented on CAMEL-17608:
---
Yeah, if folk provide the {{sObjectName}} that should be taken as is and
override the name derived from the body. It does change the behavior from what
we do for a long time, but I don't think it breaks the backward compatibility
for most folks as they would either use {{sObjectName}} or they would rely on
the class name; if both are specified and they differ this will, most likely,
break for folk, so it might be a good idea to either throw an exception or log
a warning. I suspect the logic as it stands today is in a number places so
changing this we'd need to be a bit careful to stay consistent.
> camel-salesforce: allow overriding sobject name when using DTOs
> ---
>
> Key: CAMEL-17608
> URL: https://issues.apache.org/jira/browse/CAMEL-17608
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
>Affects Versions: 3.15.0
>Reporter: Jeremy Ross
>Priority: Major
>
> When subclasses of the generated DTOs are used, Camel uses the name of the
> subclass as the sobject name, which won't work. Also, because instanceof
> check passes, camel ignores the sObjectName option. The solution would be for
> Camel to always honor the sObjectName option.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17598) camel-bindy: Handle parse failures
[
https://issues.apache.org/jira/browse/CAMEL-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486867#comment-17486867
]
Zoran Regvart commented on CAMEL-17598:
---
I think on a framework (i.e. Camel) level, adding an error handler that folk
can provide implementations of could be helpful. Perhaps something like:
{code:java}
class ParseException extends Exception {
int lineNumber;
String line;
// perhaps some other context needed here
}
interface ParserErrorHandler {
/**
* Given a ParseException that occurred while trying to parse a record choose
to either rethrow the exception preventing further parsing, ignore it returning
{@code null} or provide a substitute object for the parsed row.
*/
Object handle(ParseException e);
}{code}
(2c)
> camel-bindy: Handle parse failures
> --
>
> Key: CAMEL-17598
> URL: https://issues.apache.org/jira/browse/CAMEL-17598
> Project: Camel
> Issue Type: Improvement
> Components: camel-bindy
>Affects Versions: 3.14.1
>Reporter: Jeremy Ross
>Priority: Minor
>
> If bindy fails to parse a value, say a date, an exception is thrown and the
> entire unmarshal operation is aborted. It would be nice if the exception
> could be handled and processing could resume. We'd probably also want a way
> to specify a default value in the case of a parse failure.
> Here are some choices that need to be made:
> * A way to indicate unmarshaling should resume in the event of a parse
> failure. Where would this live? Options are at the component option level,
> {{@CsvRecord}} level, and {{@DataField}} level. Maybe all of these with each
> one successively overriding the higher level setting. But maybe that's too
> complex. What would this be called? {{continueOnParseFailure}}? Is this even
> the right concept?
> * A way to specify a default value to use when a parse fails. {{@DataField}}
> already has a {{defaultValue}} element, so maybe we use this value in the
> event of a failure. If {{defaultValue}} is not set, it could default to null
> or the default value for a primitive type.
> Zulip chat:
> https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Bindy.20continue.20on.20parse.20exception
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17565) JmsBinding not closing the InputStream
Zoran Regvart created CAMEL-17565: - Summary: JmsBinding not closing the InputStream Key: CAMEL-17565 URL: https://issues.apache.org/jira/browse/CAMEL-17565 Project: Camel Issue Type: Bug Components: camel-jms Reporter: Zoran Regvart Seems that the InputStream obtained [here|https://github.com/apache/camel/blob/e5ed4509711c0f117ce9d1e6be59c24938d4bd1d/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsBinding.java#L702] is not closed, which could lead to file descriptor leaks. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17550) Use same-version image container for Pulsar as client
[ https://issues.apache.org/jira/browse/CAMEL-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-17550. --- Resolution: Fixed > Use same-version image container for Pulsar as client > - > > Key: CAMEL-17550 > URL: https://issues.apache.org/jira/browse/CAMEL-17550 > Project: Camel > Issue Type: Task > Components: camel-pulsar >Affects Versions: 3.15.0 >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Minor > Fix For: 3.15.0 > > > We should use the same version of container image as we use for the client. > Currently we use 2.9.1 client and 2.9.0 container image version. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (CAMEL-17550) Use same-version image container for Pulsar as client
[ https://issues.apache.org/jira/browse/CAMEL-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-17550 started by Zoran Regvart. - > Use same-version image container for Pulsar as client > - > > Key: CAMEL-17550 > URL: https://issues.apache.org/jira/browse/CAMEL-17550 > Project: Camel > Issue Type: Task > Components: camel-pulsar >Affects Versions: 3.15.0 >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Minor > Fix For: 3.15.0 > > > We should use the same version of container image as we use for the client. > Currently we use 2.9.1 client and 2.9.0 container image version. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17550) Use same-version image container for Pulsar as client
Zoran Regvart created CAMEL-17550: - Summary: Use same-version image container for Pulsar as client Key: CAMEL-17550 URL: https://issues.apache.org/jira/browse/CAMEL-17550 Project: Camel Issue Type: Task Components: camel-pulsar Affects Versions: 3.15.0 Reporter: Zoran Regvart Assignee: Zoran Regvart Fix For: 3.15.0 We should use the same version of container image as we use for the client. Currently we use 2.9.1 client and 2.9.0 container image version. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-11001) Improve camel-salesforce documentation
[ https://issues.apache.org/jira/browse/CAMEL-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472346#comment-17472346 ] Zoran Regvart commented on CAMEL-11001: --- [~jeremyross] wow, that is amazing! Thank you for undertaking this, the documentation is much better now. > Improve camel-salesforce documentation > -- > > Key: CAMEL-11001 > URL: https://issues.apache.org/jira/browse/CAMEL-11001 > Project: Camel > Issue Type: Improvement > Components: camel-salesforce >Affects Versions: 2.19.0 >Reporter: Zoran Regvart >Assignee: Jeremy Ross >Priority: Minor > Labels: easytask, help-wanted > Fix For: 3.15.0 > > > The Camel Salesforce component contains a number of operations that are not > accompanied with examples of usage or at least general usage notes: for > instance what is expected in the body or header of the message. > Also general configuration getting started instructions should be provided. > A FAQ section would be nice as well. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17198) Camel Salesforce Maven Plugin generates 'PicklistEnumConverter' imports, but that class doesn't exist
[
https://issues.apache.org/jira/browse/CAMEL-17198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-17198.
---
Resolution: Fixed
> Camel Salesforce Maven Plugin generates 'PicklistEnumConverter' imports, but
> that class doesn't exist
> -
>
> Key: CAMEL-17198
> URL: https://issues.apache.org/jira/browse/CAMEL-17198
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.12.0
>Reporter: Adam
>Priority: Minor
> Fix For: 3.13.0
>
>
> I'm generating code with the Camel Salesforce Maven plugin v3.12.0, and it's
> creating valid Java classes except for an import {{import
> org.apache.camel.component.salesforce.api.PicklistEnumConverter;}} - that
> class doesn't exist.
> I can see lots of references to that class [in
> Github|https://github.com/search?q=PicklistEnumConverter=code], and I
> can find
> [Javadoc|(https://javadoc.io/static/org.apache.camel/camel-salesforce/3.4.4/org/apache/camel/component/salesforce/api/PicklistEnumConverter.html)
> for it, but it's Camel v3.4.4.
> I'm using the basic options when using the plugin (just authentication and
> regex-filtering on a specific object), so I'm not sure what could be going
> wrong.
> I'm using Maven 3.8.3.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CAMEL-17198) Camel Salesforce Maven Plugin generates 'PicklistEnumConverter' imports, but that class doesn't exist
[
https://issues.apache.org/jira/browse/CAMEL-17198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-17198:
--
Fix Version/s: 3.13.0
> Camel Salesforce Maven Plugin generates 'PicklistEnumConverter' imports, but
> that class doesn't exist
> -
>
> Key: CAMEL-17198
> URL: https://issues.apache.org/jira/browse/CAMEL-17198
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.12.0
>Reporter: Adam
>Priority: Minor
> Fix For: 3.13.0
>
>
> I'm generating code with the Camel Salesforce Maven plugin v3.12.0, and it's
> creating valid Java classes except for an import {{import
> org.apache.camel.component.salesforce.api.PicklistEnumConverter;}} - that
> class doesn't exist.
> I can see lots of references to that class [in
> Github|https://github.com/search?q=PicklistEnumConverter=code], and I
> can find
> [Javadoc|(https://javadoc.io/static/org.apache.camel/camel-salesforce/3.4.4/org/apache/camel/component/salesforce/api/PicklistEnumConverter.html)
> for it, but it's Camel v3.4.4.
> I'm using the basic options when using the plugin (just authentication and
> regex-filtering on a specific object), so I'm not sure what could be going
> wrong.
> I'm using Maven 3.8.3.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17198) Camel Salesforce Maven Plugin generates 'PicklistEnumConverter' imports, but that class doesn't exist
[
https://issues.apache.org/jira/browse/CAMEL-17198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443788#comment-17443788
]
Zoran Regvart commented on CAMEL-17198:
---
This issue [was
fixed|https://github.com/apache/camel/commit/827644dd7c463d2a80a9808bb801e43c725af3f0]
in 3.13.0.
> Camel Salesforce Maven Plugin generates 'PicklistEnumConverter' imports, but
> that class doesn't exist
> -
>
> Key: CAMEL-17198
> URL: https://issues.apache.org/jira/browse/CAMEL-17198
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.12.0
>Reporter: Adam
>Priority: Minor
>
> I'm generating code with the Camel Salesforce Maven plugin v3.12.0, and it's
> creating valid Java classes except for an import {{import
> org.apache.camel.component.salesforce.api.PicklistEnumConverter;}} - that
> class doesn't exist.
> I can see lots of references to that class [in
> Github|https://github.com/search?q=PicklistEnumConverter=code], and I
> can find
> [Javadoc|(https://javadoc.io/static/org.apache.camel/camel-salesforce/3.4.4/org/apache/camel/component/salesforce/api/PicklistEnumConverter.html)
> for it, but it's Camel v3.4.4.
> I'm using the basic options when using the plugin (just authentication and
> regex-filtering on a specific object), so I'm not sure what could be going
> wrong.
> I'm using Maven 3.8.3.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17165) camel-salesforce - Upgrade to newer API version than v50.0
[ https://issues.apache.org/jira/browse/CAMEL-17165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438547#comment-17438547 ] Zoran Regvart commented on CAMEL-17165: --- Latest version is 53, version 50 is now about a year old which to me strikes a good balance between latest and conservative enough choice. For any clients wanting the latest API version it's simple and easy to change it via parameter. > camel-salesforce - Upgrade to newer API version than v50.0 > -- > > Key: CAMEL-17165 > URL: https://issues.apache.org/jira/browse/CAMEL-17165 > Project: Camel > Issue Type: Improvement > Components: camel-salesforce >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.x > > > Today its > DEFAULT_VERSION = "50.0"; > But there are newer API versions from salesforce which introduces more > features etc. > Wonder if [~jeremyross] thought? and if you could do the upgrade? > The last upgrade is in this commit > https://github.com/apache/camel/commit/46c8bc22b73a24ddb0e0014311b2a637a1719891 > There are some unit tests etc that uses different api versions, so it may be > worth to add more versions for testing, such as in this file > camel-salesforce-maven-plugin/src/test/resources/line_item.json: -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-13704) Add github pull request template for PR instruction
[
https://issues.apache.org/jira/browse/CAMEL-13704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-13704.
---
Resolution: Implemented
> Add github pull request template for PR instruction
> ---
>
> Key: CAMEL-13704
> URL: https://issues.apache.org/jira/browse/CAMEL-13704
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: Willem Jiang
>Priority: Major
> Labels: help-wanted
> Time Spent: 50m
> Remaining Estimate: 0h
>
> It's standard procedure to accept the big contribution with iCLA granted in
> ASF.
> We should list this information when the contributor send the PR by
> specifying a PR template for github. It could be annoying for the
> experienced contributors, but it could save us some time for the new
> contributors.
> Here is a draft I have, please add comment for it.
> {code}
> - [ ] Make sure there is a [JIRA
> issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change
> (usually before you start working on it). Trivial changes like typos do not
> require a JIRA issue. Your pull request should address just this issue,
> without pulling in other changes.
> - [ ] Each commit in the pull request should have a meaningful subject line
> and body.
> - [ ] Format the pull request title like `[CAMEL-XXX] Fixes bug in
> camel-file component`, where you replace `CAMEL-XXX` with the appropriate
> JIRA issue.
> - [ ] Write a pull request description that is detailed enough to understand
> what the pull request does, how, and why.
> - [ ] Run `mvn clean install` in your module to make sure basic checks pass.
> A more thorough check will be performed on your pull request automatically.
> - [ ] If this contribution is large, please file an Apache [Individual
> Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (CAMEL-13704) Add github pull request template for PR instruction
[
https://issues.apache.org/jira/browse/CAMEL-13704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart closed CAMEL-13704.
-
> Add github pull request template for PR instruction
> ---
>
> Key: CAMEL-13704
> URL: https://issues.apache.org/jira/browse/CAMEL-13704
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: Willem Jiang
>Priority: Major
> Labels: help-wanted
> Time Spent: 50m
> Remaining Estimate: 0h
>
> It's standard procedure to accept the big contribution with iCLA granted in
> ASF.
> We should list this information when the contributor send the PR by
> specifying a PR template for github. It could be annoying for the
> experienced contributors, but it could save us some time for the new
> contributors.
> Here is a draft I have, please add comment for it.
> {code}
> - [ ] Make sure there is a [JIRA
> issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change
> (usually before you start working on it). Trivial changes like typos do not
> require a JIRA issue. Your pull request should address just this issue,
> without pulling in other changes.
> - [ ] Each commit in the pull request should have a meaningful subject line
> and body.
> - [ ] Format the pull request title like `[CAMEL-XXX] Fixes bug in
> camel-file component`, where you replace `CAMEL-XXX` with the appropriate
> JIRA issue.
> - [ ] Write a pull request description that is detailed enough to understand
> what the pull request does, how, and why.
> - [ ] Run `mvn clean install` in your module to make sure basic checks pass.
> A more thorough check will be performed on your pull request automatically.
> - [ ] If this contribution is large, please file an Apache [Individual
> Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16998) website - Improve the OpenGraph tags to align with the meta description
[
https://issues.apache.org/jira/browse/CAMEL-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419675#comment-17419675
]
Zoran Regvart commented on CAMEL-16998:
---
This would be a refinement of the changes made in
[98fbb5c41d0c3d2696c8a634ddc477c970dfea64|https://github.com/apache/camel-website/commit/98fbb5c41d0c3d2696c8a634ddc477c970dfea64]
> website - Improve the OpenGraph tags to align with the meta description
> ---
>
> Key: CAMEL-16998
> URL: https://issues.apache.org/jira/browse/CAMEL-16998
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Riccardo Forina
>Priority: Minor
> Fix For: 3.x
>
> Attachments: image-2021-09-23-10-03-24-171.png
>
>
> I noticed that when sharing a deep link on apps like Telegram or Slack, the
> preview shows some generic info about Camel instead of the page's specific
> content. For example, this is a screen of the preview for the link
> [https://camel.apache.org/components/3.11.x/eips/stop-eip.html|https://camel.apache.org/components/3.11.x/eips/stop-eip.html)]
> when sharing it on Telegram:
> !image-2021-09-23-10-03-24-171.png!
> The meta title and description for this page are ok.
> {{Stop :: Apache Camel}}
> {{}}
> Since in the source there are the OpenGraph tags, the original meta title and
> description are discarded by Telegram (and other OG compatible apps) to favor
> them. These are the title and description that will be used instead:
> {{}}
> {{}}
> I suggest updating the OG tags to be specific about the page that's being
> shared. So for the above link the tags could be something like:
> {{}}
> {{}}
> The idea is to merge the generic OG tag with the specific meta title and
> description (plus a bit of info from the breadcrumbs to contextualize the
> content) to provide a more on point description of the content that's being
> shared.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-16998) website - Improve the OpenGraph tags to align with the meta description
[
https://issues.apache.org/jira/browse/CAMEL-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-16998:
--
Labels: help-wanted (was: )
> website - Improve the OpenGraph tags to align with the meta description
> ---
>
> Key: CAMEL-16998
> URL: https://issues.apache.org/jira/browse/CAMEL-16998
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Riccardo Forina
>Priority: Minor
> Labels: help-wanted
> Fix For: 3.x
>
> Attachments: image-2021-09-23-10-03-24-171.png
>
>
> I noticed that when sharing a deep link on apps like Telegram or Slack, the
> preview shows some generic info about Camel instead of the page's specific
> content. For example, this is a screen of the preview for the link
> [https://camel.apache.org/components/3.11.x/eips/stop-eip.html|https://camel.apache.org/components/3.11.x/eips/stop-eip.html)]
> when sharing it on Telegram:
> !image-2021-09-23-10-03-24-171.png!
> The meta title and description for this page are ok.
> {{Stop :: Apache Camel}}
> {{}}
> Since in the source there are the OpenGraph tags, the original meta title and
> description are discarded by Telegram (and other OG compatible apps) to favor
> them. These are the title and description that will be used instead:
> {{}}
> {{}}
> I suggest updating the OG tags to be specific about the page that's being
> shared. So for the above link the tags could be something like:
> {{}}
> {{}}
> The idea is to merge the generic OG tag with the specific meta title and
> description (plus a bit of info from the breadcrumbs to contextualize the
> content) to provide a more on point description of the content that's being
> shared.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16236) camel-website - Download macos should say its x86
[ https://issues.apache.org/jira/browse/CAMEL-16236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-16236. --- Resolution: Fixed > camel-website - Download macos should say its x86 > - > > Key: CAMEL-16236 > URL: https://issues.apache.org/jira/browse/CAMEL-16236 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Minor > > Apple now has x86 and silicon architectures so the binaries should mention > which it uses. > https://camel.apache.org/download/ > For example > MacOS 64bit binary > --> > MacOS (x86) 64bit binary -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16236) camel-website - Download macos should say its x86
[ https://issues.apache.org/jira/browse/CAMEL-16236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart reassigned CAMEL-16236: - Assignee: Zoran Regvart > camel-website - Download macos should say its x86 > - > > Key: CAMEL-16236 > URL: https://issues.apache.org/jira/browse/CAMEL-16236 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Minor > > Apple now has x86 and silicon architectures so the binaries should mention > which it uses. > https://camel.apache.org/download/ > For example > MacOS 64bit binary > --> > MacOS (x86) 64bit binary -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-11522) Include requirements
[ https://issues.apache.org/jira/browse/CAMEL-11522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-11522: -- Fix Version/s: 3.13.0 > Include requirements > > > Key: CAMEL-11522 > URL: https://issues.apache.org/jira/browse/CAMEL-11522 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.13.0 > > Attachments: Include Requirement.png > > > We should have a requirements page, a getting started page, or what version > page, that lists, at least, JVM versions per Camel version required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13804) website - Add page which lists which components supports which runtimes
[ https://issues.apache.org/jira/browse/CAMEL-13804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-13804: -- Fix Version/s: (was: 3.x) 3.13.0 > website - Add page which lists which components supports which runtimes > --- > > Key: CAMEL-13804 > URL: https://issues.apache.org/jira/browse/CAMEL-13804 > Project: Camel > Issue Type: Task > Components: documentation, website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted, outreachy2020 > Fix For: 3.13.0 > > > With CAMEL-13803 we should have a catalog that knows which component support > which runtimes. > Then we can make a page with a table of each component with a matrix with [x] > for which they support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-11522) Include requirements
[ https://issues.apache.org/jira/browse/CAMEL-11522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417943#comment-17417943 ] Zoran Regvart commented on CAMEL-11522: --- We [recently discussed|https://lists.apache.org/thread.html/r33ea6b94c7f4158346fb067633cb3b62eb7a07b81a878d6a3cdb0de3%40%3Cdev.camel.apache.org%3E] dropping Java 8 and this issue was brought back. Lets figure out where to place the requirements and what information to include. Also related to CAMEL-13804. > Include requirements > > > Key: CAMEL-11522 > URL: https://issues.apache.org/jira/browse/CAMEL-11522 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: Include Requirement.png > > > We should have a requirements page, a getting started page, or what version > page, that lists, at least, JVM versions per Camel version required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-12671) camel-iec60870 - Add documentation for missing field
[ https://issues.apache.org/jira/browse/CAMEL-12671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-12671. --- Resolution: Fixed Seems to be fixed via CAMEL-13870 > camel-iec60870 - Add documentation for missing field > > > Key: CAMEL-12671 > URL: https://issues.apache.org/jira/browse/CAMEL-12671 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Assignee: Jens Reimann >Priority: Minor > Labels: help-wanted > Fix For: Future > > > This field did not have documentation. So I added something > https://github.com/apache/camel/blob/48539d7156a5d4795f0dc593c6334427fc8450e1/components/camel-iec60870/src/main/java/org/apache/camel/component/iec60870/client/ClientOptions.java#L48 > Jens do you mind taking a look, and add the correct documentation, and also > set the correct default value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-12671) camel-iec60870 - Add documentation for missing field
[ https://issues.apache.org/jira/browse/CAMEL-12671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-12671: -- Fix Version/s: (was: Future) 3.12.0 > camel-iec60870 - Add documentation for missing field > > > Key: CAMEL-12671 > URL: https://issues.apache.org/jira/browse/CAMEL-12671 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Assignee: Jens Reimann >Priority: Minor > Labels: help-wanted > Fix For: 3.12.0 > > > This field did not have documentation. So I added something > https://github.com/apache/camel/blob/48539d7156a5d4795f0dc593c6334427fc8450e1/components/camel-iec60870/src/main/java/org/apache/camel/component/iec60870/client/ClientOptions.java#L48 > Jens do you mind taking a look, and add the correct documentation, and also > set the correct default value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16854) Component docs -- generate tables from json during website build
[ https://issues.apache.org/jira/browse/CAMEL-16854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-16854: -- Fix Version/s: 3.12.0 > Component docs -- generate tables from json during website build > > > Key: CAMEL-16854 > URL: https://issues.apache.org/jira/browse/CAMEL-16854 > Project: Camel > Issue Type: Task > Components: documentation >Affects Versions: 3.11.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.12.0 > > > Investigate how to generate the options tables for components from json > during the website build using an Asciidoctor extension. > Also, upgrade to Antora 3 (alpha) and use symlinks rather than copying adoc > files for components. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16854) Component docs -- generate tables from json during website build
[
https://issues.apache.org/jira/browse/CAMEL-16854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-16854.
---
Resolution: Fixed
This is done on the {{main}} branch.
> Component docs -- generate tables from json during website build
>
>
> Key: CAMEL-16854
> URL: https://issues.apache.org/jira/browse/CAMEL-16854
> Project: Camel
> Issue Type: Task
> Components: documentation
>Affects Versions: 3.11.0
>Reporter: David Jencks
>Assignee: David Jencks
>Priority: Major
>
> Investigate how to generate the options tables for components from json
> during the website build using an Asciidoctor extension.
> Also, upgrade to Antora 3 (alpha) and use symlinks rather than copying adoc
> files for components.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16982) Bindy dataformat documentation - three dataformats documented as one
[
https://issues.apache.org/jira/browse/CAMEL-16982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17416709#comment-17416709
]
Zoran Regvart commented on CAMEL-16982:
---
There seems to be some special handling of Bindy in the tooling:
{code}
tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/PrepareCatalogMojo.java
740:// special for bindy
741:if (dataformat.startsWith("bindy")) {
742:dataformat = "bindy";
tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/UpdateReadmeMojo.java
288:if ("bindy".equals(dataFormatName)) {
304:// for now it's only applied to bindy but can be
unlocked for other dataformats if needed
305:if ("bindy".equals(dataFormatName)) {
446:if (name.startsWith("bindy")) {
447:return "bindy";
455:if (name.startsWith("bindy")) {
tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/PackageDataFormatMojo.java
343:if ("type".equals(option.getName()) &&
"bindy".equals(model.getModelName())) {
345:case "bindy-csv":
348:case "bindy-fixed":
351:case "bindy-kvp":
431:} else if ("bindy-csv".equals(name) || "bindy-fixed".equals(name)
|| "bindy-kvp".equals(name)) {
432:return "bindy";
466:// TODO: split json / bindy into multiple jsons descriptors
485:} else if ("bindy-csv".equals(name)) {
487:} else if ("bindy-fixed".equals(name)) {
489:} else if ("bindy-kvp".equals(name)) {
{code}
> Bindy dataformat documentation - three dataformats documented as one
>
>
> Key: CAMEL-16982
> URL: https://issues.apache.org/jira/browse/CAMEL-16982
> Project: Camel
> Issue Type: Task
> Components: documentation
>Affects Versions: 3.x
>Reporter: Zoran Regvart
>Priority: Major
> Fix For: 3.x
>
>
> Bindy dataformat is composed of three components which all (currently) have
> identical options. Our current documentation approach is to use single set of
> options for
> all three and with the `jsonpathTable2` macro we needed to pick one (see
> [PR#6096|https://github.com/apache/camel/pull/6096]).
> Should we split into three asciidoc files for each option - that would be in
> line with how other components are documented?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16982) Bindy dataformat documentation - three dataformats documented as one
Zoran Regvart created CAMEL-16982: - Summary: Bindy dataformat documentation - three dataformats documented as one Key: CAMEL-16982 URL: https://issues.apache.org/jira/browse/CAMEL-16982 Project: Camel Issue Type: Task Components: documentation Affects Versions: 3.x Reporter: Zoran Regvart Fix For: 3.x Bindy dataformat is composed of three components which all (currently) have identical options. Our current documentation approach is to use single set of options for all three and with the `jsonpathTable2` macro we needed to pick one (see [PR#6096|https://github.com/apache/camel/pull/6096]). Should we split into three asciidoc files for each option - that would be in line with how other components are documented? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16929) Document DSLs
[
https://issues.apache.org/jira/browse/CAMEL-16929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17413037#comment-17413037
]
Zoran Regvart commented on CAMEL-16929:
---
I agree. Bit odd that in Camel K those are called "languages", overrides the
"languages" used in [Expression
Languages|https://camel.apache.org/components/latest/languages/index.html] in
Camel, we should try to be more consistent with the terminology not to confuse
the users.
> Document DSLs
> -
>
> Key: CAMEL-16929
> URL: https://issues.apache.org/jira/browse/CAMEL-16929
> Project: Camel
> Issue Type: Task
> Components: documentation
>Affects Versions: 3.x
>Reporter: Zoran Regvart
>Priority: Major
> Labels: help-wanted
> Fix For: 3.x
>
>
> We're lacking documentation for a number of DSLs. These files are virtually
> empty:
> {code}
> dsl/camel-java-joor-dsl/src/main/docs/java-joor-dsl.adoc
> dsl/camel-xml-jaxb-dsl/src/main/docs/java-xml-jaxb-dsl.adoc
> dsl/camel-groovy-dsl/camel-groovy-dsl/src/main/docs/groovy-dsl.adoc
> dsl/camel-kotlin-dsl/src/main/docs/kotlin-dsl.adoc
> dsl/camel-xml-io-dsl/src/main/docs/java-xml-io-dsl.adoc
> dsl/camel-js-dsl/src/main/docs/js-dsl.adoc
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16929) Document DSLs
Zoran Regvart created CAMEL-16929:
-
Summary: Document DSLs
Key: CAMEL-16929
URL: https://issues.apache.org/jira/browse/CAMEL-16929
Project: Camel
Issue Type: Task
Components: documentation
Affects Versions: 3.x
Reporter: Zoran Regvart
We're lacking documentation for a number of DSLs. These files are virtually
empty:
{code}
dsl/camel-java-joor-dsl/src/main/docs/java-joor-dsl.adoc
dsl/camel-xml-jaxb-dsl/src/main/docs/java-xml-jaxb-dsl.adoc
dsl/camel-groovy-dsl/camel-groovy-dsl/src/main/docs/groovy-dsl.adoc
dsl/camel-kotlin-dsl/src/main/docs/kotlin-dsl.adoc
dsl/camel-xml-io-dsl/src/main/docs/java-xml-io-dsl.adoc
dsl/camel-js-dsl/src/main/docs/js-dsl.adoc
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-16850) Unable to reference properties after bootstrap
[
https://issues.apache.org/jira/browse/CAMEL-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-16850:
--
Description:
The {{MainBootstrapCloseable}} clears and sets to {{null}} initial properties,
override properties wildcard properties and main configuration properties on
bootstrap of Camel context. Adding a route that depends on those properties
after bootstrap is therefore no longer possible.
The value {{MainBootstrapCloseable}} has in static route configurations is at
odds in dynamic route configurations.
Example (obviously not production code):
{code:java}
final Main main = new Main();main.addInitialProperty("prop", "value");
try (MainConfigurationProperties conf = main.configure()) {
conf.addRoutesBuilder(new RouteBuilder() {
@Override
public void configure() throws Exception {
from("timer:one").log("{{prop}}").process(e ->
e.getContext().addRoutes(new RouteBuilder() {
@Override
public void configure() throws Exception {
from("timer:two").log("{{prop}}");
}
}));
}
});
main.run();
} {code}
Should the {{MainBootstrapCloseable}} be removed, or should the properties
component be configured to incorporate these properties?
was:
The {{MainBootstrapCloseable}} clears and sets to {{null}} initial properties,
override properties wildcard properties and main configuration properties on
bootstrap of Camel context. Adding a route that depends on those properties
after bootstrap is therefore no longer possible.
The value {{MainBootstrapCloseable}} has in static route configurations is at
odds in dynamic route configurations.
Example (obviously not production code):
{code:java}
final Main main = new Main();main.addInitialProperty("prop", "value");
try (MainConfigurationProperties conf = main.configure()) {
conf.addRoutesBuilder(new RouteBuilder() {
@Override
public void configure() throws Exception {
from("timer:one").log("{{prop}}").process(e ->
e.getContext().addRoutes(new RouteBuilder() {
@Override
public void configure() throws Exception {
from("timer:two").log("{{prop}}");
}
}));
}
}); main.run();
} {code}
Should the {{MainBootstrapCloseable}} be removed, or should the properties
component be configured to incorporate these properties?
> Unable to reference properties after bootstrap
> --
>
> Key: CAMEL-16850
> URL: https://issues.apache.org/jira/browse/CAMEL-16850
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 3.11.0
>Reporter: Zoran Regvart
>Priority: Major
>
> The {{MainBootstrapCloseable}} clears and sets to {{null}} initial
> properties, override properties wildcard properties and main configuration
> properties on bootstrap of Camel context. Adding a route that depends on
> those properties after bootstrap is therefore no longer possible.
> The value {{MainBootstrapCloseable}} has in static route configurations is at
> odds in dynamic route configurations.
> Example (obviously not production code):
> {code:java}
> final Main main = new Main();main.addInitialProperty("prop", "value");
> try (MainConfigurationProperties conf = main.configure()) {
> conf.addRoutesBuilder(new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from("timer:one").log("{{prop}}").process(e ->
> e.getContext().addRoutes(new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from("timer:two").log("{{prop}}");
> }
> }));
> }
> });
> main.run();
> } {code}
> Should the {{MainBootstrapCloseable}} be removed, or should the properties
> component be configured to incorporate these properties?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16850) Unable to reference properties after bootstrap
Zoran Regvart created CAMEL-16850:
-
Summary: Unable to reference properties after bootstrap
Key: CAMEL-16850
URL: https://issues.apache.org/jira/browse/CAMEL-16850
Project: Camel
Issue Type: Bug
Components: camel-main
Affects Versions: 3.11.0
Reporter: Zoran Regvart
The {{MainBootstrapCloseable}} clears and sets to {{null}} initial properties,
override properties wildcard properties and main configuration properties on
bootstrap of Camel context. Adding a route that depends on those properties
after bootstrap is therefore no longer possible.
The value {{MainBootstrapCloseable}} has in static route configurations is at
odds in dynamic route configurations.
Example (obviously not production code):
{code:java}
final Main main = new Main();main.addInitialProperty("prop", "value");
try (MainConfigurationProperties conf = main.configure()) {
conf.addRoutesBuilder(new RouteBuilder() {
@Override
public void configure() throws Exception {
from("timer:one").log("{{prop}}").process(e ->
e.getContext().addRoutes(new RouteBuilder() {
@Override
public void configure() throws Exception {
from("timer:two").log("{{prop}}");
}
}));
}
}); main.run();
} {code}
Should the {{MainBootstrapCloseable}} be removed, or should the properties
component be configured to incorporate these properties?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16499) camel-website - Add documentation how xref links works
[
https://issues.apache.org/jira/browse/CAMEL-16499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-16499.
---
Resolution: Fixed
Big thanks to [~djencks] for doing this!
> camel-website - Add documentation how xref links works
> --
>
> Key: CAMEL-16499
> URL: https://issues.apache.org/jira/browse/CAMEL-16499
> Project: Camel
> Issue Type: Improvement
> Components: documentation, website
>Reporter: Claus Ibsen
>Assignee: David Jencks
>Priority: Major
> Fix For: 3.x
>
>
> We need a section on camel-website root readme page, that talks about how you
> do links between pages on the website.
> The xref: syntax is confusing and not intuitive how you link between: eips,
> components, user-manual, fag, pages between sub-projects (eg camel ->
> camel-k) and so forth.
> For example in kamelet-eip.adoc as EIP doc, I could not link with
> {code}
> == More details
> - xref:components::kamelet-component.adoc[Kamelet component]
> - xref:manual::route-tepmplate.adoc[Route Template]
> - xref:latest@camel-k:ROOT::kamelets-user.adoc[Kamelets user guide]
> We also provided a small
> https://github.com/apache/camel-examples/tree/master/examples/kamelet[Kamelet
> example].
> {code}
> I tried 10 different things for the last two bullets, and looked other xref
> links, and nothing kinda worked.
> So what you end up doing is NOT to have xref links at all.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-16499) camel-website - Add documentation how xref links works
[
https://issues.apache.org/jira/browse/CAMEL-16499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart reassigned CAMEL-16499:
-
Assignee: David Jencks (was: Zoran Regvart)
> camel-website - Add documentation how xref links works
> --
>
> Key: CAMEL-16499
> URL: https://issues.apache.org/jira/browse/CAMEL-16499
> Project: Camel
> Issue Type: Improvement
> Components: documentation, website
>Reporter: Claus Ibsen
>Assignee: David Jencks
>Priority: Major
> Fix For: 3.x
>
>
> We need a section on camel-website root readme page, that talks about how you
> do links between pages on the website.
> The xref: syntax is confusing and not intuitive how you link between: eips,
> components, user-manual, fag, pages between sub-projects (eg camel ->
> camel-k) and so forth.
> For example in kamelet-eip.adoc as EIP doc, I could not link with
> {code}
> == More details
> - xref:components::kamelet-component.adoc[Kamelet component]
> - xref:manual::route-tepmplate.adoc[Route Template]
> - xref:latest@camel-k:ROOT::kamelets-user.adoc[Kamelets user guide]
> We also provided a small
> https://github.com/apache/camel-examples/tree/master/examples/kamelet[Kamelet
> example].
> {code}
> I tried 10 different things for the last two bullets, and looked other xref
> links, and nothing kinda worked.
> So what you end up doing is NOT to have xref links at all.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16804) NullPointerException when using try-with-resources and MainConfigurationProperties
[
https://issues.apache.org/jira/browse/CAMEL-16804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-16804.
---
Resolution: Fixed
> NullPointerException when using try-with-resources and
> MainConfigurationProperties
> --
>
> Key: CAMEL-16804
> URL: https://issues.apache.org/jira/browse/CAMEL-16804
> Project: Camel
> Issue Type: Bug
> Components: camel-main
>Affects Versions: 3.11.0
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 3.11.1, 3.12.0
>
>
> When using try-with-resources with {{MainConfigurationProperties}},
> {{MainConfigurationProperties::close}} might be invoked twice leading to
> {{NullPointerException}} on shutdown:
> {code}
> ...
> Caused by: java.lang.NullPointerException
> at
> all//org.apache.camel.main.MainConfigurationProperties.close(MainConfigurationProperties.java:88)
> at all//io.github.zregvart.dbzcamel.dbtodb.App.main(App.java:26)
> ... 4 more
> {code}
> I.e. the Camel's shutdown will invoke {{MainConfigurationProperties::close}},
> but also the try-with-resources bit if used like:
> {code}
> try (MainConfigurationProperties configure = main.configure()) {
> configure.addRoutesBuilder(Route.class);
> main.run(args);
> } catch (final Exception e) {
> throw new RuntimeException(e);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16804) NullPointerException when using try-with-resources and MainConfigurationProperties
Zoran Regvart created CAMEL-16804:
-
Summary: NullPointerException when using try-with-resources and
MainConfigurationProperties
Key: CAMEL-16804
URL: https://issues.apache.org/jira/browse/CAMEL-16804
Project: Camel
Issue Type: Bug
Components: camel-main
Affects Versions: 3.11.0
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Fix For: 3.11.1, 3.12.0
When using try-with-resources with {{MainConfigurationProperties}},
{{MainConfigurationProperties::close}} might be invoked twice leading to
{{NullPointerException}} on shutdown:
{code}
...
Caused by: java.lang.NullPointerException
at
all//org.apache.camel.main.MainConfigurationProperties.close(MainConfigurationProperties.java:88)
at all//io.github.zregvart.dbzcamel.dbtodb.App.main(App.java:26)
... 4 more
{code}
I.e. the Camel's shutdown will invoke {{MainConfigurationProperties::close}},
but also the try-with-resources bit if used like:
{code}
try (MainConfigurationProperties configure = main.configure()) {
configure.addRoutesBuilder(Route.class);
main.run(args);
} catch (final Exception e) {
throw new RuntimeException(e);
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16686) camel-website - Asciidoc ERROR/WARN during build
[ https://issues.apache.org/jira/browse/CAMEL-16686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-16686. --- Fix Version/s: 3.7.5 Resolution: Fixed > camel-website - Asciidoc ERROR/WARN during build > > > Key: CAMEL-16686 > URL: https://issues.apache.org/jira/browse/CAMEL-16686 > Project: Camel > Issue Type: Task > Components: documentation, website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Minor > Fix For: 3.7.5, 3.11.0 > > > ➤ YN: asciidoctor: ERROR: properties-component.adoc: line 618: include > target not found: > example$/components/camel-spring/src/test/resources/org/apache/camel/components/properties/CamelSpringPropertyPlaceholderConfigurerTest.xml > ➤ YN: asciidoctor: ERROR: properties-component.adoc: line 630: include > target not found: > example$/components/camel-spring/src/test/resources/org/apache/camel/components/properties/CamelSpringPropertyPlaceholderConfigurerTest.xml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16686) camel-website - Asciidoc ERROR/WARN during build
[
https://issues.apache.org/jira/browse/CAMEL-16686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17357330#comment-17357330
]
Zoran Regvart commented on CAMEL-16686:
---
There was an issue in the Gulp script that copies over examples to the docs
directory, and a small typo in the {{properties-component.adoc}} on
camel-3.7.x. I've updated the script on the main branch also in case we create
any examples in components outside of the components directory. I've scheduled
a build of the website, let's see if that fixes this:
https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/164/
> camel-website - Asciidoc ERROR/WARN during build
>
>
> Key: CAMEL-16686
> URL: https://issues.apache.org/jira/browse/CAMEL-16686
> Project: Camel
> Issue Type: Task
> Components: documentation, website
>Reporter: Claus Ibsen
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 3.11.0
>
>
> ➤ YN: asciidoctor: ERROR: properties-component.adoc: line 618: include
> target not found:
> example$/components/camel-spring/src/test/resources/org/apache/camel/components/properties/CamelSpringPropertyPlaceholderConfigurerTest.xml
> ➤ YN: asciidoctor: ERROR: properties-component.adoc: line 630: include
> target not found:
> example$/components/camel-spring/src/test/resources/org/apache/camel/components/properties/CamelSpringPropertyPlaceholderConfigurerTest.xml
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-16686) camel-website - Asciidoc ERROR/WARN during build
[ https://issues.apache.org/jira/browse/CAMEL-16686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart reassigned CAMEL-16686: - Assignee: Zoran Regvart > camel-website - Asciidoc ERROR/WARN during build > > > Key: CAMEL-16686 > URL: https://issues.apache.org/jira/browse/CAMEL-16686 > Project: Camel > Issue Type: Task > Components: documentation, website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Minor > Fix For: 3.11.0 > > > ➤ YN: asciidoctor: ERROR: properties-component.adoc: line 618: include > target not found: > example$/components/camel-spring/src/test/resources/org/apache/camel/components/properties/CamelSpringPropertyPlaceholderConfigurerTest.xml > ➤ YN: asciidoctor: ERROR: properties-component.adoc: line 630: include > target not found: > example$/components/camel-spring/src/test/resources/org/apache/camel/components/properties/CamelSpringPropertyPlaceholderConfigurerTest.xml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16686) camel-website - Asciidoc ERROR/WARN during build
[ https://issues.apache.org/jira/browse/CAMEL-16686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17357271#comment-17357271 ] Zoran Regvart commented on CAMEL-16686: --- I can have a look, seems to originate on the camel-3.7.x branch. > camel-website - Asciidoc ERROR/WARN during build > > > Key: CAMEL-16686 > URL: https://issues.apache.org/jira/browse/CAMEL-16686 > Project: Camel > Issue Type: Task > Components: documentation, website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Minor > Fix For: 3.11.0 > > > ➤ YN: asciidoctor: ERROR: properties-component.adoc: line 618: include > target not found: > example$/components/camel-spring/src/test/resources/org/apache/camel/components/properties/CamelSpringPropertyPlaceholderConfigurerTest.xml > ➤ YN: asciidoctor: ERROR: properties-component.adoc: line 630: include > target not found: > example$/components/camel-spring/src/test/resources/org/apache/camel/components/properties/CamelSpringPropertyPlaceholderConfigurerTest.xml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-16669) website - Add EOL column to download page
[ https://issues.apache.org/jira/browse/CAMEL-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-16669. --- Resolution: Fixed > website - Add EOL column to download page > - > > Key: CAMEL-16669 > URL: https://issues.apache.org/jira/browse/CAMEL-16669 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.11.0 > > Attachments: Screenshot_2021-05-31 Downloads - Apache Camel(1).png, > Screenshot_2021-05-31 Downloads - Apache Camel.png > > > After the Version column we need a new EOL column at > https://camel.apache.org/download/ > For the LTS releases then the EOL is +1 year after the first release. > All other kinds should be empty as only LTS releases have an EOL date. > For Camel 2.x the EOL is special as it should be set to Jan 2022. > Instead of some magic algorithm, then maybe we just hardcode the EOL dates as > we only do 2 LTS releases per year, so that is probably simpler. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16669) website - Add EOL column to download page
[ https://issues.apache.org/jira/browse/CAMEL-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354299#comment-17354299 ] Zoran Regvart commented on CAMEL-16669: --- Perhaps something like this on desktop: !Screenshot_2021-05-31 Downloads - Apache Camel.png! and mobile: !Screenshot_2021-05-31 Downloads - Apache Camel(1).png! Those column headings can also be a bit better: * Description -> Notes * Download Link -> Download * PGP Signature file of download -> Signature * SHA512 Checksum file of download -> Checksum Perhaps even joining the PGP and checksum columns into one. > website - Add EOL column to download page > - > > Key: CAMEL-16669 > URL: https://issues.apache.org/jira/browse/CAMEL-16669 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot_2021-05-31 Downloads - Apache Camel(1).png, > Screenshot_2021-05-31 Downloads - Apache Camel.png > > > After the Version column we need a new EOL column at > https://camel.apache.org/download/ > For the LTS releases then the EOL is +1 year after the first release. > All other kinds should be empty as only LTS releases have an EOL date. > For Camel 2.x the EOL is special as it should be set to Jan 2022. > Instead of some magic algorithm, then maybe we just hardcode the EOL dates as > we only do 2 LTS releases per year, so that is probably simpler. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16669) website - Add EOL column to download page
[ https://issues.apache.org/jira/browse/CAMEL-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-16669: -- Attachment: Screenshot_2021-05-31 Downloads - Apache Camel(1).png > website - Add EOL column to download page > - > > Key: CAMEL-16669 > URL: https://issues.apache.org/jira/browse/CAMEL-16669 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot_2021-05-31 Downloads - Apache Camel(1).png, > Screenshot_2021-05-31 Downloads - Apache Camel.png > > > After the Version column we need a new EOL column at > https://camel.apache.org/download/ > For the LTS releases then the EOL is +1 year after the first release. > All other kinds should be empty as only LTS releases have an EOL date. > For Camel 2.x the EOL is special as it should be set to Jan 2022. > Instead of some magic algorithm, then maybe we just hardcode the EOL dates as > we only do 2 LTS releases per year, so that is probably simpler. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-16669) website - Add EOL column to download page
[ https://issues.apache.org/jira/browse/CAMEL-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-16669: -- Attachment: Screenshot_2021-05-31 Downloads - Apache Camel.png > website - Add EOL column to download page > - > > Key: CAMEL-16669 > URL: https://issues.apache.org/jira/browse/CAMEL-16669 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot_2021-05-31 Downloads - Apache Camel(1).png, > Screenshot_2021-05-31 Downloads - Apache Camel.png > > > After the Version column we need a new EOL column at > https://camel.apache.org/download/ > For the LTS releases then the EOL is +1 year after the first release. > All other kinds should be empty as only LTS releases have an EOL date. > For Camel 2.x the EOL is special as it should be set to Jan 2022. > Instead of some magic algorithm, then maybe we just hardcode the EOL dates as > we only do 2 LTS releases per year, so that is probably simpler. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16669) website - Add EOL column to download page
[ https://issues.apache.org/jira/browse/CAMEL-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354287#comment-17354287 ] Zoran Regvart commented on CAMEL-16669: --- We can add a front matter parameter with the date of EOL and then display that on the download and individual release pages. Adding more columns will influence the mobile version, perhaps adding that information in the first column would be better? > website - Add EOL column to download page > - > > Key: CAMEL-16669 > URL: https://issues.apache.org/jira/browse/CAMEL-16669 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > > After the Version column we need a new EOL column at > https://camel.apache.org/download/ > For the LTS releases then the EOL is +1 year after the first release. > All other kinds should be empty as only LTS releases have an EOL date. > For Camel 2.x the EOL is special as it should be set to Jan 2022. > Instead of some magic algorithm, then maybe we just hardcode the EOL dates as > we only do 2 LTS releases per year, so that is probably simpler. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16639) Upgrade to Antora 3.0
Zoran Regvart created CAMEL-16639:
-
Summary: Upgrade to Antora 3.0
Key: CAMEL-16639
URL: https://issues.apache.org/jira/browse/CAMEL-16639
Project: Camel
Issue Type: Task
Components: documentation, website
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Antora 3 will bring several improvements, out of which two are really
significant for Camel:
* [versionless
components|https://docs.antora.org/antora/3.0/whats-new/#specifying-the-versionless-component-version],
this will allow us to remove the {{latest}} from URLs
* [git ref derived versions|https://gitlab.com/antora/antora/issues/296] which
will reduce the maintenance of updating versions in component descriptors
Versionless components is most disruptive, so we'd need to create redirect
directives so we don't break any links.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-11030) Add a vault service to manage secrets
[
https://issues.apache.org/jira/browse/CAMEL-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17321259#comment-17321259
]
Zoran Regvart commented on CAMEL-11030:
---
[~lb] that sounds good to me.
> Add a vault service to manage secrets
> -
>
> Key: CAMEL-11030
> URL: https://issues.apache.org/jira/browse/CAMEL-11030
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.x
>
>
> Lot of components these days are supposed to manage secrets such as auth
> tokens etc. but as there's no common support in camel each component is
> implementing the same concept which increase the maintenance cost.
> It would be nice to have a vault service in camel-core so that components can
> leverage and extend it, some ideas/examples:
> - to store auth tokens and delegate to the vault the notification about
> expiration and renewal when needed (by registering some functions/callbacks)
> - to provide different backends like kubernetes secrets, hashicorp's vault,
> - to provide different workflow (i.e. JSON Web Token)
> - to use the vault as properties source if someone prefix a property with
> vault like {{vault:db.password}}
> The interface should be as simple as possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16443) Yarn failure in the docs module
[
https://issues.apache.org/jira/browse/CAMEL-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-16443.
---
Resolution: Fixed
> Yarn failure in the docs module
> ---
>
> Key: CAMEL-16443
> URL: https://issues.apache.org/jira/browse/CAMEL-16443
> Project: Camel
> Issue Type: Task
> Components: build system, documentation
>Affects Versions: 3.x
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.10.0
>
>
> We're hitting an issue with yarn trying to download the xref-validator:
> {code:java}
> 2021-04-02T07:18:52.6346086Z [INFO] --- frontend-maven-plugin:1.11.2:yarn
> (yarn-install) @ docs ---
> 2021-04-02T07:18:52.6395069Z [INFO] Running 'yarn install --no-progress
> --force --non-interactive --frozen-lockfile' in
> /home/runner/work/camel/camel/docs
> 2021-04-02T07:18:53.1009689Z [INFO] yarn install v1.12.3
> 2021-04-02T07:18:53.1802491Z [INFO] [1/4] Resolving packages...
> 2021-04-02T07:18:53.5469556Z [INFO] [2/4] Fetching packages...
> 2021-04-02T07:18:54.2562888Z [INFO] error
> https://gitlab.com/antora/xref-validator/repository/archive.tar.gz?ref=84f28a20b8be888b7664a4540cda5aca56de0824:
> Extracting tar content of undefined failed, the file appears to be corrupt:
> "Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?"
> 2021-04-02T07:18:54.2576233Z [INFO] error
> https://gitlab.com/antora/xref-validator/repository/archive.tar.gz?ref=84f28a20b8be888b7664a4540cda5aca56de0824:
> Extracting tar content of undefined failed, the file appears to be corrupt:
> "Invalid tar header. Maybe the tar is corrupted or it needs to be
> gunzipped?"info Visit https://yarnpkg.com/en/docs/cli/install for
> documentation about this command. {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16443) Yarn failure in the docs module
Zoran Regvart created CAMEL-16443:
-
Summary: Yarn failure in the docs module
Key: CAMEL-16443
URL: https://issues.apache.org/jira/browse/CAMEL-16443
Project: Camel
Issue Type: Bug
Components: build system, documentation
Affects Versions: 3.x
Reporter: Zoran Regvart
Assignee: Zoran Regvart
We're hitting an issue with yarn trying to download the xref-validator:
{code:java}
2021-04-02T07:18:52.6346086Z [INFO] --- frontend-maven-plugin:1.11.2:yarn
(yarn-install) @ docs ---
2021-04-02T07:18:52.6395069Z [INFO] Running 'yarn install --no-progress --force
--non-interactive --frozen-lockfile' in /home/runner/work/camel/camel/docs
2021-04-02T07:18:53.1009689Z [INFO] yarn install v1.12.3
2021-04-02T07:18:53.1802491Z [INFO] [1/4] Resolving packages...
2021-04-02T07:18:53.5469556Z [INFO] [2/4] Fetching packages...
2021-04-02T07:18:54.2562888Z [INFO] error
https://gitlab.com/antora/xref-validator/repository/archive.tar.gz?ref=84f28a20b8be888b7664a4540cda5aca56de0824:
Extracting tar content of undefined failed, the file appears to be corrupt:
"Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?"
2021-04-02T07:18:54.2576233Z [INFO] error
https://gitlab.com/antora/xref-validator/repository/archive.tar.gz?ref=84f28a20b8be888b7664a4540cda5aca56de0824:
Extracting tar content of undefined failed, the file appears to be corrupt:
"Invalid tar header. Maybe the tar is corrupted or it needs to be
gunzipped?"info Visit https://yarnpkg.com/en/docs/cli/install for documentation
about this command. {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (CAMEL-16443) Yarn failure in the docs module
[
https://issues.apache.org/jira/browse/CAMEL-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-16443 started by Zoran Regvart.
-
> Yarn failure in the docs module
> ---
>
> Key: CAMEL-16443
> URL: https://issues.apache.org/jira/browse/CAMEL-16443
> Project: Camel
> Issue Type: Bug
> Components: build system, documentation
>Affects Versions: 3.x
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>
> We're hitting an issue with yarn trying to download the xref-validator:
> {code:java}
> 2021-04-02T07:18:52.6346086Z [INFO] --- frontend-maven-plugin:1.11.2:yarn
> (yarn-install) @ docs ---
> 2021-04-02T07:18:52.6395069Z [INFO] Running 'yarn install --no-progress
> --force --non-interactive --frozen-lockfile' in
> /home/runner/work/camel/camel/docs
> 2021-04-02T07:18:53.1009689Z [INFO] yarn install v1.12.3
> 2021-04-02T07:18:53.1802491Z [INFO] [1/4] Resolving packages...
> 2021-04-02T07:18:53.5469556Z [INFO] [2/4] Fetching packages...
> 2021-04-02T07:18:54.2562888Z [INFO] error
> https://gitlab.com/antora/xref-validator/repository/archive.tar.gz?ref=84f28a20b8be888b7664a4540cda5aca56de0824:
> Extracting tar content of undefined failed, the file appears to be corrupt:
> "Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped?"
> 2021-04-02T07:18:54.2576233Z [INFO] error
> https://gitlab.com/antora/xref-validator/repository/archive.tar.gz?ref=84f28a20b8be888b7664a4540cda5aca56de0824:
> Extracting tar content of undefined failed, the file appears to be corrupt:
> "Invalid tar header. Maybe the tar is corrupted or it needs to be
> gunzipped?"info Visit https://yarnpkg.com/en/docs/cli/install for
> documentation about this command. {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16388) camel-salesforce: drop support for XML as a serialization format
[
https://issues.apache.org/jira/browse/CAMEL-16388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312432#comment-17312432
]
Zoran Regvart commented on CAMEL-16388:
---
[~jawwad124] do you think in your use case you can utilize mapping technology
instead? We have several mapping components in Camel that could help you. Dozer
and Atlasmap spring to mind first.
> camel-salesforce: drop support for XML as a serialization format
>
>
> Key: CAMEL-16388
> URL: https://issues.apache.org/jira/browse/CAMEL-16388
> Project: Camel
> Issue Type: Wish
> Components: camel-salesforce
>Affects Versions: 3.8.0
>Reporter: Jeremy Ross
>Priority: Major
> Fix For: Future
>
>
> Putting this out here for a discussion.
> The salesforce REST APIs support XML and JSON. However, it's clear from the
> official documentation and examples that JSON is the first-class citizen. All
> the examples are in JSON and there's only this one, sad reference to XML
> serialization:
> {quote}XML serialization is similar to SOAP API. XML requests are supported
> in UTF-8 and UTF-16, and XML responses are provided in UTF-8.{quote}
> This leaves us Camel maintainers with the not-fun activity of guessing how
> salesforce expects its myriad types to be serialized to XML.
> I suspect that Camel users don't really care that much which serialization
> format is used. Both have equal parity with salesforce, and as a Camel user I
> just care that Camel serializes and deserializes my DTOs correctly. Wire
> format is an abstraction that shouldn't matter. This is the crux of my
> argument.
> Camel's support for both formats is a maintenance burden, and a barrier to
> developing future features and support for newer APIs. Serialization format
> isn't a concern to users, and supporting both formats is of no real value.
> Therefore, I'd like to consider dropping XML support, leaving JSON as the
> supported format.
> Note that this does not affect the `rawPayload` option. Users would still be
> welcome to provide their own raw payloads in either format.
> Paging for comment: [~zregvart] [~davsclaus] [~jbonofre]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-11030) Add a vault service to manage secrets
[
https://issues.apache.org/jira/browse/CAMEL-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312294#comment-17312294
]
Zoran Regvart commented on CAMEL-11030:
---
I think it's important to have a API/SPI to notify of any changes to the
credentials. Ideally we would have component or endpoint property metadata that
indicates for what properties notifications are received. I'm not sure if that
way of implementing this would be (really) difficult, it would mean that Camel
core might need to keep track of from where the value of a property was
received.
> Add a vault service to manage secrets
> -
>
> Key: CAMEL-11030
> URL: https://issues.apache.org/jira/browse/CAMEL-11030
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.x
>
>
> Lot of components these days are supposed to manage secrets such as auth
> tokens etc. but as there's no common support in camel each component is
> implementing the same concept which increase the maintenance cost.
> It would be nice to have a vault service in camel-core so that components can
> leverage and extend it, some ideas/examples:
> - to store auth tokens and delegate to the vault the notification about
> expiration and renewal when needed (by registering some functions/callbacks)
> - to provide different backends like kubernetes secrets, hashicorp's vault,
> - to provide different workflow (i.e. JSON Web Token)
> - to use the vault as properties source if someone prefix a property with
> vault like {{vault:db.password}}
> The interface should be as simple as possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16420) include's pointing to spring boot starter documentation don't specify version
[
https://issues.apache.org/jira/browse/CAMEL-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-16420.
---
Resolution: Fixed
> include's pointing to spring boot starter documentation don't specify version
> -
>
> Key: CAMEL-16420
> URL: https://issues.apache.org/jira/browse/CAMEL-16420
> Project: Camel
> Issue Type: Task
> Components: website
>Affects Versions: 3.4.5, 3.7.3, 3.8.0, 3.9.0, 3.x
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>
> This leads to issues like:
> {code:java}
> YN: asciidoctor: ERROR: aws-cw-component.adoc: line 202: include target
> not found: camel-spring-boot::page$aws-cw-starter.adoc {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16420) include's pointing to spring boot starter documentation don't specify version
[
https://issues.apache.org/jira/browse/CAMEL-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310870#comment-17310870
]
Zoran Regvart commented on CAMEL-16420:
---
Looks okay now. There are few other warnings, subject for other issues.
> include's pointing to spring boot starter documentation don't specify version
> -
>
> Key: CAMEL-16420
> URL: https://issues.apache.org/jira/browse/CAMEL-16420
> Project: Camel
> Issue Type: Task
> Components: website
>Affects Versions: 3.4.5, 3.7.3, 3.8.0, 3.9.0, 3.x
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>
> This leads to issues like:
> {code:java}
> YN: asciidoctor: ERROR: aws-cw-component.adoc: line 202: include target
> not found: camel-spring-boot::page$aws-cw-starter.adoc {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16420) include's pointing to spring boot starter documentation don't specify version
[
https://issues.apache.org/jira/browse/CAMEL-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310835#comment-17310835
]
Zoran Regvart commented on CAMEL-16420:
---
There are four that have escaped me, I'm going to have a look now:
{code:java}
➤ YN: asciidoctor: ERROR: caffeine-lrucache.adoc: line 42: include target
not found: 3.8.x@camel-spring-boot::page$caffeine-lrucache-starter.adoc
➤ YN: asciidoctor: ERROR: jfr.adoc: line 36: include target not found:
3.8.x@camel-spring-boot::page$jfr-starter.adoc
➤ YN: asciidoctor: ERROR: azure-summary.adoc: line 17: include target not
found: 3.9.x@camel-spring-boot::page$azure-starter.adoc
➤ YN: asciidoctor: ERROR: spring-xml.adoc: line 40: include target not
found: 3.9.x@camel-spring-boot::page$spring-xml-starter.adoc {code}
> include's pointing to spring boot starter documentation don't specify version
> -
>
> Key: CAMEL-16420
> URL: https://issues.apache.org/jira/browse/CAMEL-16420
> Project: Camel
> Issue Type: Task
> Components: website
>Affects Versions: 3.4.5, 3.7.3, 3.8.0, 3.9.0, 3.x
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>
> This leads to issues like:
> {code:java}
> YN: asciidoctor: ERROR: aws-cw-component.adoc: line 202: include target
> not found: camel-spring-boot::page$aws-cw-starter.adoc {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-16420) include's pointing to spring boot starter documentation don't specify version
[
https://issues.apache.org/jira/browse/CAMEL-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-16420:
--
Affects Version/s: 3.4.5
> include's pointing to spring boot starter documentation don't specify version
> -
>
> Key: CAMEL-16420
> URL: https://issues.apache.org/jira/browse/CAMEL-16420
> Project: Camel
> Issue Type: Task
> Components: website
>Affects Versions: 3.4.5, 3.7.3, 3.8.0, 3.9.0, 3.x
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>
> This leads to issues like:
> {code:java}
> YN: asciidoctor: ERROR: aws-cw-component.adoc: line 202: include target
> not found: camel-spring-boot::page$aws-cw-starter.adoc {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-16420) include's pointing to spring boot starter documentation don't specify version
[
https://issues.apache.org/jira/browse/CAMEL-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart updated CAMEL-16420:
--
Summary: include's pointing to spring boot starter documentation don't
specify version (was: xref's pointing to spring boot starter documentation
don't specify version)
> include's pointing to spring boot starter documentation don't specify version
> -
>
> Key: CAMEL-16420
> URL: https://issues.apache.org/jira/browse/CAMEL-16420
> Project: Camel
> Issue Type: Bug
> Components: website
>Affects Versions: 3.7.3, 3.8.0, 3.9.0, 3.x
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>
> This leads to issues like:
> {code:java}
> YN: asciidoctor: ERROR: aws-cw-component.adoc: line 202: include target
> not found: camel-spring-boot::page$aws-cw-starter.adoc {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16420) xref's pointing to spring boot starter documentation don't specify version
Zoran Regvart created CAMEL-16420:
-
Summary: xref's pointing to spring boot starter documentation
don't specify version
Key: CAMEL-16420
URL: https://issues.apache.org/jira/browse/CAMEL-16420
Project: Camel
Issue Type: Bug
Components: website
Affects Versions: 3.9.0, 3.8.0, 3.7.3, 3.x
Reporter: Zoran Regvart
Assignee: Zoran Regvart
This leads to issues like:
{code:java}
YN: asciidoctor: ERROR: aws-cw-component.adoc: line 202: include target not
found: camel-spring-boot::page$aws-cw-starter.adoc {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (CAMEL-16420) xref's pointing to spring boot starter documentation don't specify version
[
https://issues.apache.org/jira/browse/CAMEL-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-16420 started by Zoran Regvart.
-
> xref's pointing to spring boot starter documentation don't specify version
> --
>
> Key: CAMEL-16420
> URL: https://issues.apache.org/jira/browse/CAMEL-16420
> Project: Camel
> Issue Type: Bug
> Components: website
>Affects Versions: 3.7.3, 3.8.0, 3.9.0, 3.x
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>
> This leads to issues like:
> {code:java}
> YN: asciidoctor: ERROR: aws-cw-component.adoc: line 202: include target
> not found: camel-spring-boot::page$aws-cw-starter.adoc {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16388) camel-salesforce: drop support for XML as a serialization format
[
https://issues.apache.org/jira/browse/CAMEL-16388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309257#comment-17309257
]
Zoran Regvart commented on CAMEL-16388:
---
[~jawwad124] inform our decision, it would be good to explain a bit your use
cases. Do you use data transfer objects (DTOs) generated by the
camel-salesforce-maven-plugin, or pass through the raw XML? Do you rely on the
DTOs being able to serialize to XML?
> camel-salesforce: drop support for XML as a serialization format
>
>
> Key: CAMEL-16388
> URL: https://issues.apache.org/jira/browse/CAMEL-16388
> Project: Camel
> Issue Type: Wish
> Components: camel-salesforce
>Affects Versions: 3.8.0
>Reporter: Jeremy Ross
>Priority: Major
> Fix For: Future
>
>
> Putting this out here for a discussion.
> The salesforce REST APIs support XML and JSON. However, it's clear from the
> official documentation and examples that JSON is the first-class citizen. All
> the examples are in JSON and there's only this one, sad reference to XML
> serialization:
> {quote}XML serialization is similar to SOAP API. XML requests are supported
> in UTF-8 and UTF-16, and XML responses are provided in UTF-8.{quote}
> This leaves us Camel maintainers with the not-fun activity of guessing how
> salesforce expects its myriad types to be serialized to XML.
> I suspect that Camel users don't really care that much which serialization
> format is used. Both have equal parity with salesforce, and as a Camel user I
> just care that Camel serializes and deserializes my DTOs correctly. Wire
> format is an abstraction that shouldn't matter. This is the crux of my
> argument.
> Camel's support for both formats is a maintenance burden, and a barrier to
> developing future features and support for newer APIs. Serialization format
> isn't a concern to users, and supporting both formats is of no real value.
> Therefore, I'd like to consider dropping XML support, leaving JSON as the
> supported format.
> Note that this does not affect the `rawPayload` option. Users would still be
> welcome to provide their own raw payloads in either format.
> Paging for comment: [~zregvart] [~davsclaus] [~jbonofre]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16388) camel-salesforce: drop support for XML as a serialization format
[
https://issues.apache.org/jira/browse/CAMEL-16388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308566#comment-17308566
]
Zoran Regvart commented on CAMEL-16388:
---
+1, we can do this in a minor version right after a LTS version has been
released. This also eliminates the need for xstream and simplifies the code
paths quite a bit.
> camel-salesforce: drop support for XML as a serialization format
>
>
> Key: CAMEL-16388
> URL: https://issues.apache.org/jira/browse/CAMEL-16388
> Project: Camel
> Issue Type: Wish
> Components: camel-salesforce
>Affects Versions: 3.8.0
>Reporter: Jeremy Ross
>Priority: Major
> Fix For: 3.10.0
>
>
> Putting this out here for a discussion.
> The salesforce REST APIs support XML and JSON. However, it's clear from the
> official documentation and examples that JSON is the first-class citizen. All
> the examples are in JSON and there's only this one, sad reference to XML
> serialization:
> {quote}XML serialization is similar to SOAP API. XML requests are supported
> in UTF-8 and UTF-16, and XML responses are provided in UTF-8.{quote}
> This leaves us Camel maintainers with the not-fun activity of guessing how
> salesforce expects its myriad types to be serialized to XML.
> I suspect that Camel users don't really care that much which serialization
> format is used. Both have equal parity with salesforce, and as a Camel user I
> just care that Camel serializes and deserializes my DTOs correctly. Wire
> format is an abstraction that shouldn't matter. This is the crux of my
> argument.
> Camel's support for both formats is a maintenance burden, and a barrier to
> developing future features and support for newer APIs. Serialization format
> isn't a concern to users, and supporting both formats is of no real value.
> Therefore, I'd like to consider dropping XML support, leaving JSON as the
> supported format.
> Note that this does not affect the `rawPayload` option. Users would still be
> welcome to provide their own raw payloads in either format.
> Paging for comment: [~zregvart] [~davsclaus] [~jbonofre]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16228) Documentation: Fix xref link in old branches
[
https://issues.apache.org/jira/browse/CAMEL-16228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17286101#comment-17286101
]
Zoran Regvart commented on CAMEL-16228:
---
Thanks [~djencks] now I understand that we can set attributes per component in
[antora.yml|https://docs.antora.org/antora/2.3/component-attributes/#hard-set],
I was not aware of this until now. This will help when we point from
sub-project to Camel documentation (other than the manual) of specific version.
There are a number of issues that we have with the root cause of poor version
management, I'll try to enumerate the ones I know about:
* Release process doesn't account for changing the (Antora) component version,
this would be a non-issue if we were not publishing LTS, last release and
latest versions. We usually followup a release by changing the {{version}} in
{{antora.yml}} and change the version in {{xref}} links (examples:
[ccfcfcf6|https://github.com/apache/camel/commit/ccfcfcf6023aac038dd60d08071ec4f38a3b3a2e].
[af07b7f4|https://github.com/apache/camel-spring-boot/commit/af07b7f4ee312c4ee9e34077b760ac500b97f7fc],
[baa6bf97|https://github.com/apache/camel-spring-boot/commit/baa6bf9798234e4fac6ccbc12746d5567f3829e3]).
For this I think a proper solution is including a {{camel-version}} attribute
in {{antora.yml}} and referencing that from {{xref}} links. Then we would need
to change the {{version}} and {{camel-version}} in {{antora.yml}}.
* We forget to version links in the (Antora) "components" component, which end
up pointing to the {{latest}} version (examples:
[ae16cbd0|https://github.com/apache/camel/commit/ae16cbd0b86b1d90e4364f8f3de2dd8cffde8be0],
[ae16cbd0|https://github.com/apache/camel/commit/ae16cbd0b86b1d90e4364f8f3de2dd8cffde8be0].
I think same solution should apply here, we add {{camel-version}} attribute.
I think a lot of our problems would go away if we go through all xrefs, and
make sure that all xrefs that do not point to the user manual point to a
version dictated by the attribute, for now I think we only need
{{camel-version}}, we could also need {{camel-quarkus-version}} and similar if
we end up pointing from "components" component to the Camel Quarkus
documentation for example.
We could merge camel-spring-boot and camel-karaf into a distributed
"components" component, but I would not tackle this for this issue.
> Documentation: Fix xref link in old branches
>
>
> Key: CAMEL-16228
> URL: https://issues.apache.org/jira/browse/CAMEL-16228
> Project: Camel
> Issue Type: Task
> Components: documentation, website
>Reporter: Andrea Cosentino
>Priority: Major
> Fix For: 3.x
>
>
> Currently in the .adoc of our documentation we are using (for example)
> xref:components::kafka-component.adoc[KafkaIdempotentRepository]
> This is ok for master branch and latest documentation.
> The problem arises when we look at older active branch, all the link to
> components in 3.7.x for example are still pointi to latest. We need to change
> the docs in the following way
> xref:3.7.x@components::kafka-component.adoc[KafkaIdempotentRepository]
> We need to do this for 3.8.x, 3.7.x and 3.4.x
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16228) Documentation: Fix xref link in old branches
[
https://issues.apache.org/jira/browse/CAMEL-16228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285860#comment-17285860
]
Zoran Regvart commented on CAMEL-16228:
---
The only version that's fixed to {{latest}} is the user manual.
We build against different versions of (Camel) components and sub-projects.
From those we need to point to a specific (compatible) version. I think mostly
we point from (Camel) components to (Camel) components and from sub-projects to
(Camel) component documentation.
For {{xref}} within the same (Antora) component and module, we should use the
shortest version, e.g. {{xref:path}} (as in this
[section|https://docs.antora.org/antora/2.2/asciidoc/page-to-page-xref/#same-module]),
this results in addressing the same (Antora) component and version.
For Camel, Spring Boot and Karaf, that are released at the same time as Camel,
so the version is the same, I _think_ we can use the intrinsic attribute
{{:page-component-version:}} (per Antora
[documentation|https://docs.antora.org/antora/2.3/page/intrinsic-attributes/#page-attributes]),
e.g. {{xref:\{page-component-version\}@components::adoc}}.
For other sub projects (K, Kafka Connector, Quarkus), we need to manage
separately the version of Camel is referenced there. I don't know of a per-
(Antora) component Asciidoc attribute feature, so I don't think we can set an
attribute like {{camel-version}} in (say) Camel K's documentation to (say)
{{3.7.x}}, and have it maintained for across releases. So for this aspect of
the problem I don't have a solution.
Either way, we would need to go through a large number of {{xref}} links across
multiple branches we build and make sure that the version is parameterized. I
remember doing scripts and some Java code around that when we first created the
documentation, so something like that to automate the process would be needed.
[~djencks] your thoughts would be appreciated here.
> Documentation: Fix xref link in old branches
>
>
> Key: CAMEL-16228
> URL: https://issues.apache.org/jira/browse/CAMEL-16228
> Project: Camel
> Issue Type: Task
> Components: documentation, website
>Reporter: Andrea Cosentino
>Priority: Major
> Fix For: 3.x
>
>
> Currently in the .adoc of our documentation we are using (for example)
> xref:components::kafka-component.adoc[KafkaIdempotentRepository]
> This is ok for master branch and latest documentation.
> The problem arises when we look at older active branch, all the link to
> components in 3.7.x for example are still pointi to latest. We need to change
> the docs in the following way
> xref:3.7.x@components::kafka-component.adoc[KafkaIdempotentRepository]
> We need to do this for 3.8.x, 3.7.x and 3.4.x
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-16084) salesforce: Out of order execution
[
https://issues.apache.org/jira/browse/CAMEL-16084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17272807#comment-17272807
]
Zoran Regvart edited comment on CAMEL-16084 at 1/27/21, 12:04 PM:
--
Not 100% sure what the problem is, but I played around with a simple route with
split/aggregation without {{synchronous}} seems to work okay with Salesforce.
This is the route:
{code:java}
import static java.util.Arrays.asList;
import static org.apache.camel.builder.AggregationStrategies.groupedBody;
from("direct:start")
.split(body(), groupedBody())
.to("salesforce:getSObject?sObjectName=Contact=true")
.transform().jsonpath("$.FirstName")
.log("individual: ${body}")
.end()
.log("aggregated: ${body[0]} ${body[1]} ${body[2]}"); // just to get a
nicer output, GroupedExchangeList overrides toString
{code}
I'm triggering the route with a list of IDs:
{code:java}
producer.sendBody("direct:start", asList("0030Y02vBoFQAU",
"0030Y02vBoGQAU", "0030Y02vBoHQAU")){code}
This gives me:
{code:java}
2021-01-27 13:02:02,425 INFO [SalesforceHttpClient@156b88f5-20] route1:
individual: Rose
2021-01-27 13:02:02,503 INFO [SalesforceHttpClient@156b88f5-20] route1:
individual: Sean
2021-01-27 13:02:02,587 INFO [SalesforceHttpClient@156b88f5-19] route1:
individual: Jack
2021-01-27 13:02:02,626 INFO [SalesforceHttpClient@156b88f5-19] route1:
aggregated: Rose Sean Jack
{code}
was (Author: zregvart):
Not 100% sure what the problem is, but I played around with a simple route and
aggregation without {{synchronous}} seems to work okay with Salesforce. This is
the route:
{code:java}
import static java.util.Arrays.asList;
import static org.apache.camel.builder.AggregationStrategies.groupedBody;
from("direct:start")
.split(body(), groupedBody())
.to("salesforce:getSObject?sObjectName=Contact=true")
.transform().jsonpath("$.FirstName")
.log("individual: ${body}")
.end()
.log("aggregated: ${body[0]} ${body[1]} ${body[2]}"); // just to get a
nicer output, GroupedExchangeList overrides toString
{code}
I'm triggering the route with a list of IDs:
{code:java}
producer.sendBody("direct:start", asList("0030Y02vBoFQAU",
"0030Y02vBoGQAU", "0030Y02vBoHQAU")){code}
This gives me:
{code:java}
2021-01-27 13:02:02,425 INFO [SalesforceHttpClient@156b88f5-20] route1:
individual: Rose
2021-01-27 13:02:02,503 INFO [SalesforceHttpClient@156b88f5-20] route1:
individual: Sean
2021-01-27 13:02:02,587 INFO [SalesforceHttpClient@156b88f5-19] route1:
individual: Jack
2021-01-27 13:02:02,626 INFO [SalesforceHttpClient@156b88f5-19] route1:
aggregated: Rose Sean Jack
{code}
> salesforce: Out of order execution
> --
>
> Key: CAMEL-16084
> URL: https://issues.apache.org/jira/browse/CAMEL-16084
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.7.1
>Reporter: Jeremy Ross
>Assignee: Jeremy Ross
>Priority: Major
>
> When using a salesforce operation after an aggregator, control seems to
> return to the aggregate caller immediately instead of proceeding with
> processors downstream from the salesforce operation. This is the behavior I'd
> expect if using the aggregator with parallelProcessing.
> I believe this is longstanding behavior, however with the removal of the
> `synchronous` option from the salesforce component (CAMEL-14138), we've
> removed a workaround to this issue.
> I'm seeing the same behavior with a salesforce operation via a wiretap with a
> threadpool with poolsize, maxsize and queuesize of 1, which should
> effectively behave in a synchronous manner.
> Test case: https://gist.github.com/jeremyross/4d7d14a33452edf236faefda77ad3e3d
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-16084) salesforce: Out of order execution
[
https://issues.apache.org/jira/browse/CAMEL-16084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17272807#comment-17272807
]
Zoran Regvart commented on CAMEL-16084:
---
Not 100% sure what the problem is, but I played around with a simple route and
aggregation without {{synchronous}} seems to work okay with Salesforce. This is
the route:
{code:java}
import static java.util.Arrays.asList;
import static org.apache.camel.builder.AggregationStrategies.groupedBody;
from("direct:start")
.split(body(), groupedBody())
.to("salesforce:getSObject?sObjectName=Contact=true")
.transform().jsonpath("$.FirstName")
.log("individual: ${body}")
.end()
.log("aggregated: ${body[0]} ${body[1]} ${body[2]}"); // just to get a
nicer output, GroupedExchangeList overrides toString
{code}
I'm triggering the route with a list of IDs:
{code:java}
producer.sendBody("direct:start", asList("0030Y02vBoFQAU",
"0030Y02vBoGQAU", "0030Y02vBoHQAU")){code}
This gives me:
{code:java}
2021-01-27 13:02:02,425 INFO [SalesforceHttpClient@156b88f5-20] route1:
individual: Rose
2021-01-27 13:02:02,503 INFO [SalesforceHttpClient@156b88f5-20] route1:
individual: Sean
2021-01-27 13:02:02,587 INFO [SalesforceHttpClient@156b88f5-19] route1:
individual: Jack
2021-01-27 13:02:02,626 INFO [SalesforceHttpClient@156b88f5-19] route1:
aggregated: Rose Sean Jack
{code}
> salesforce: Out of order execution
> --
>
> Key: CAMEL-16084
> URL: https://issues.apache.org/jira/browse/CAMEL-16084
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.7.1
>Reporter: Jeremy Ross
>Assignee: Jeremy Ross
>Priority: Major
>
> When using a salesforce operation after an aggregator, control seems to
> return to the aggregate caller immediately instead of proceeding with
> processors downstream from the salesforce operation. This is the behavior I'd
> expect if using the aggregator with parallelProcessing.
> I believe this is longstanding behavior, however with the removal of the
> `synchronous` option from the salesforce component (CAMEL-14138), we've
> removed a workaround to this issue.
> I'm seeing the same behavior with a salesforce operation via a wiretap with a
> threadpool with poolsize, maxsize and queuesize of 1, which should
> effectively behave in a synchronous manner.
> Test case: https://gist.github.com/jeremyross/4d7d14a33452edf236faefda77ad3e3d
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-16038) Remove binary releases
[
https://issues.apache.org/jira/browse/CAMEL-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-16038.
---
Resolution: Fixed
> Remove binary releases
> --
>
> Key: CAMEL-16038
> URL: https://issues.apache.org/jira/browse/CAMEL-16038
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>
> As
> [discussed|https://lists.apache.org/thread.html/r2b9a9a4d2946608832f68b6144ed35fb7896ed83d7e3b0213202acf4%40%3Cdev.camel.apache.org%3E]
> on user/dev mailing list, there is little use of the Camel binary release.
> For this we'll do:
> # Remove "Binary zip" and "Binary tar.gz" rows from the table in
> [https://camel.apache.org/download/] and individual releases (e.g.
> [https://camel.apache.org/releases/release-3.4.5/#camel])
> # Remove binary releases from ASF distribution (e.g. {{*.tar.gz*}} and non
> {{-src}} {{*.zip}}
> [https://dist.apache.org/repos/dist/release/camel/apache-camel/3.7.0/])
> # Remove binary assembly
> We will continue to have binary releases for tools that can be downloaded and
> used directly as such, for example {{kamel}} CLI, or future {{karamel}} CLI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-16038) Remove binary releases
Zoran Regvart created CAMEL-16038:
-
Summary: Remove binary releases
Key: CAMEL-16038
URL: https://issues.apache.org/jira/browse/CAMEL-16038
Project: Camel
Issue Type: Task
Components: website
Reporter: Zoran Regvart
Assignee: Zoran Regvart
As
[discussed|https://lists.apache.org/thread.html/r2b9a9a4d2946608832f68b6144ed35fb7896ed83d7e3b0213202acf4%40%3Cdev.camel.apache.org%3E]
on user/dev mailing list, there is little use of the Camel binary release. For
this we'll do:
# Remove "Binary zip" and "Binary tar.gz" rows from the table in
[https://camel.apache.org/download/] and individual releases (e.g.
[https://camel.apache.org/releases/release-3.4.5/#camel])
# Remove binary releases from ASF distribution (e.g. {{*.tar.gz*}} and non
{{-src}} {{*.zip}}
[https://dist.apache.org/repos/dist/release/camel/apache-camel/3.7.0/])
# Remove binary assembly
We will continue to have binary releases for tools that can be downloaded and
used directly as such, for example {{kamel}} CLI, or future {{karamel}} CLI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14138) Salesforce: a synchronous call that follow an asynchronous call will always result in a TimeoutException
[
https://issues.apache.org/jira/browse/CAMEL-14138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261192#comment-17261192
]
Zoran Regvart commented on CAMEL-14138:
---
I don't think it's worth the effort to resolve this without having good use
cases behind it. I'd rather deprecate this and remove it in the next LTS. I'm
not sure if there are use cases that folk rely on this, if they do, I think
deprecating it should bring about the use cases.
> Salesforce: a synchronous call that follow an asynchronous call will always
> result in a TimeoutException
>
>
> Key: CAMEL-14138
> URL: https://issues.apache.org/jira/browse/CAMEL-14138
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.0.0.RC3
>Reporter: Jeremy Ross
>Priority: Major
> Fix For: 3.x
>
> Attachments: Call stack.png, thread-dump.txt
>
>
> Using the {{synchronous}} URL option, a synchronous operation following an
> asynchronous operation will result in a
> {{java.util.concurrent.TimeoutException}}. Subsequent synchronous operations
> will succeed. Despite the {{TimeoutException}}, the operation can still be
> successful on the salesforce side. I've yet to determine why Camel thinks the
> operation is timing out.
> Test case: [https://github.com/jeremyross/CAMEL-14138]
> stack trace:
> {noformat}
> org.apache.camel.component.salesforce.api.SalesforceException: Unexpected
> error {0:null} executing
> {POST:https://cs44.salesforce.com/services/data/v45.0/sobjects/Contact}
> at
> org.apache.camel.component.salesforce.internal.client.AbstractClientBase$1.onComplete(AbstractClientBase.java:206)
> ~[camel-salesforce-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT]
> at
> org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:196)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:188)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:441)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at org.eclipse.jetty.client.HttpReceiver.abort(HttpReceiver.java:523)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.HttpChannel.abortResponse(HttpChannel.java:156)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at org.eclipse.jetty.client.HttpChannel.abort(HttpChannel.java:149)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at org.eclipse.jetty.client.HttpExchange.abort(HttpExchange.java:257)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.HttpConversation.abort(HttpConversation.java:149)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at org.eclipse.jetty.client.HttpRequest.abort(HttpRequest.java:766)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.http.HttpConnectionOverHTTP.abort(HttpConnectionOverHTTP.java:204)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.http.HttpConnectionOverHTTP.close(HttpConnectionOverHTTP.java:190)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onIdleExpired(HttpConnectionOverHTTP.java:145)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.io.ssl.SslConnection.onIdleExpired(SslConnection.java:302)
> ~[jetty-io-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.io.AbstractEndPoint.onIdleExpired(AbstractEndPoint.java:401)
> ~[jetty-io-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171)
> ~[jetty-io-9.4.19.v20190610.jar:9.4.19.v20190610]
> at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113)
> ~[jetty-io-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> ~[na:na]
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> ~[na:na]
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> ~[na:na]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> ~[na:na]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ~[na:na]
> at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]
> Caused by:
[jira] [Commented] (CAMEL-14138) Salesforce: a synchronous call that follow an asynchronous call will always result in a TimeoutException
[
https://issues.apache.org/jira/browse/CAMEL-14138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260302#comment-17260302
]
Zoran Regvart commented on CAMEL-14138:
---
Perhaps for my better understanding what would be the use case for using
{{synchronous=true}}, from git blame I can see that it was added in the initial
component contribution without much explanation as to why. I can't think of an
use case for it, can we remove it and not try to fix it?
> Salesforce: a synchronous call that follow an asynchronous call will always
> result in a TimeoutException
>
>
> Key: CAMEL-14138
> URL: https://issues.apache.org/jira/browse/CAMEL-14138
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.0.0.RC3
>Reporter: Jeremy Ross
>Priority: Major
> Fix For: 3.x
>
> Attachments: Call stack.png, thread-dump.txt
>
>
> Using the {{synchronous}} URL option, a synchronous operation following an
> asynchronous operation will result in a
> {{java.util.concurrent.TimeoutException}}. Subsequent synchronous operations
> will succeed. Despite the {{TimeoutException}}, the operation can still be
> successful on the salesforce side. I've yet to determine why Camel thinks the
> operation is timing out.
> Test case: [https://github.com/jeremyross/CAMEL-14138]
> stack trace:
> {noformat}
> org.apache.camel.component.salesforce.api.SalesforceException: Unexpected
> error {0:null} executing
> {POST:https://cs44.salesforce.com/services/data/v45.0/sobjects/Contact}
> at
> org.apache.camel.component.salesforce.internal.client.AbstractClientBase$1.onComplete(AbstractClientBase.java:206)
> ~[camel-salesforce-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT]
> at
> org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:196)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:188)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:441)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at org.eclipse.jetty.client.HttpReceiver.abort(HttpReceiver.java:523)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.HttpChannel.abortResponse(HttpChannel.java:156)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at org.eclipse.jetty.client.HttpChannel.abort(HttpChannel.java:149)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at org.eclipse.jetty.client.HttpExchange.abort(HttpExchange.java:257)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.HttpConversation.abort(HttpConversation.java:149)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at org.eclipse.jetty.client.HttpRequest.abort(HttpRequest.java:766)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.http.HttpConnectionOverHTTP.abort(HttpConnectionOverHTTP.java:204)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.http.HttpConnectionOverHTTP.close(HttpConnectionOverHTTP.java:190)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onIdleExpired(HttpConnectionOverHTTP.java:145)
> ~[jetty-client-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.io.ssl.SslConnection.onIdleExpired(SslConnection.java:302)
> ~[jetty-io-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.io.AbstractEndPoint.onIdleExpired(AbstractEndPoint.java:401)
> ~[jetty-io-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171)
> ~[jetty-io-9.4.19.v20190610.jar:9.4.19.v20190610]
> at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113)
> ~[jetty-io-9.4.19.v20190610.jar:9.4.19.v20190610]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> ~[na:na]
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> ~[na:na]
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> ~[na:na]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> ~[na:na]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ~[na:na]
> at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]
> Caused by:
[jira] [Resolved] (CAMEL-15948) camel-website - Quarkus examples are empty
[ https://issues.apache.org/jira/browse/CAMEL-15948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-15948. --- Fix Version/s: (was: 3.8.0) Assignee: Zoran Regvart (was: Peter Palaga) Resolution: Fixed Looks okay now > camel-website - Quarkus examples are empty > -- > > Key: CAMEL-15948 > URL: https://issues.apache.org/jira/browse/CAMEL-15948 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > > The table is empty at > https://camel.apache.org/camel-quarkus/latest/user-guide/examples.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-12812) Salesforce component tries to reconnect when unsubscribing from topic in case of "403::Handshake denied" error
[
https://issues.apache.org/jira/browse/CAMEL-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251736#comment-17251736
]
Zoran Regvart commented on CAMEL-12812:
---
I'm not certain that it would. The credentials we provide to the Salesforce API
remain unchanged, and the request to not restart the client goes against the
resiliency we're trying to have in the Salesforce consumer. We simply can't
recover in some cases without restarting the client. Whatever made the
credentials to expire would make them invalid if the application hosting the
Camel/Salesforce component would restart, so I'm not sure if this would provide
a long term benefit. Perhaps [~atyurin] you could elaborate a bit or create a
test reproducer for the issue you're having.
> Salesforce component tries to reconnect when unsubscribing from topic in case
> of "403::Handshake denied" error
> --
>
> Key: CAMEL-12812
> URL: https://issues.apache.org/jira/browse/CAMEL-12812
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 2.21.2, 2.22.1
>Reporter: Andrey Tyurin
>Priority: Minor
>
> Hi.
> We've faced some strange behavior when salesforce component is shutting down.
> When SF component is unsubscribing from channel and it gets some error, e.g.
> "403::Handshake denied" it tries then reconnect to SF. But why? if it is
> shutting down.
> This causes long process of logout from SF: about 4 minutes.
> We do not have specific scenario, but only exceptions for this case.
>
> 2018-08-31 05:40:51.454 [SalesforceHttpClient@b9f06a7-293] INFO
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Restarting on unexpected disconnect from Salesforce... 2018-08-31
> 05:40:51.454 [SalesforceHttpClient@b9f06a7-293] DEBUG
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Waiting to disconnect... 2018-08-31 05:40:51.455
> [SalesforceHttpClient@b9f06a7-288] DEBUG
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> [CHANNEL:META_CONNECT]: \{clientId=kteskpq4fgf192z1zpdm0ml1ebe,
> advice={reconnect=none, interval=0}, channel=/meta/connect, id=29,
> error=401::Authentication invalid, successful=false} 2018-08-31 05:40:51.455
> [SalesforceHttpClient@b9f06a7-288] WARN
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Connect failure: \{clientId=kteskpq4fgf192z1zpdm0ml1ebe,
> advice={reconnect=none, interval=0}, channel=/meta/connect, id=29,
> error=401::Authentication invalid, successful=false} 2018-08-31 05:40:56.516
> [SalesforceHttpClient@b9f06a7-292] INFO
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Cleaning session (logout) from SalesforceSession before restarting client
> 2018-08-31 05:41:39.156 [Camel (camel-1) thread #105 - ShutdownTask] INFO
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Unsubscribing from channel /topic/myCompanyExtRoutPsr... ... 2018-08-31
> 05:42:19.156 [Camel (camel-1) thread #105 - ShutdownTask] WARN
> org.apache.camel.impl.DefaultShutdownStrategy - Error occurred while shutting
> down route:
> Consumer[salesforce-102-STREAMING://myCompanyExtRoutPsr?sObjectClass=com.myCompany.sfgateway.api.dto.PendingServiceRouting=SELECT+Id%2C+QueueId%2C+WorkItemId%2C+IsPushed%2C+ServiceChannelId%2C+LastDeclinedAgentSession%2C+CreatedDate%2C+IsDeleted%2C+IsPushAttempted%2C+IsTransfer+from+PendingServiceRouting+WHERE+RoutingModel+%3D+%27ExternalRouting%27=true].
> This exception will be ignored. org.apache.camel.CamelException: Timeout
> error unsubscribing from topic myCompanyExtRoutPsr after 40 seconds at
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper.unsubscribe(SubscriptionHelper.java:519)
> ~[camel-salesforce-2.21.2.jar!/:2.21.2] at
> org.apache.camel.component.salesforce.SalesforceConsumer.doStop(SalesforceConsumer.java:139)
> ~[camel-salesforce-2.21.2.jar!/:2.21.2] at
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> ~[camel-core-2.21.2.jar!/:2.21.2] at
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:142)
> ~[camel-core-2.21.2.jar!/:2.21.2] at
> org.apache.camel.impl.DefaultShutdownStrategy.shutdownNow(DefaultShutdownStrategy.java:381)
> [camel-core-2.21.2.jar!/:2.21.2] at
> org.apache.camel.impl.DefaultShutdownStrategy$ShutdownTask.run(DefaultShutdownStrategy.java:577)
> [camel-core-2.21.2.jar!/:2.21.2] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [?:1.8.0_102] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [?:1.8.0_102] at
>
[jira] [Resolved] (CAMEL-12871) Camel-salesforce component drops the streaming topic
[
https://issues.apache.org/jira/browse/CAMEL-12871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-12871.
---
Resolution: Fixed
Fix is targeted to be released in 3.7.1 and 3.8.0, in the interim I would
appreciate anyone trying this out in their environment and reporting any issues
so we get them fixed.
> Camel-salesforce component drops the streaming topic
>
>
> Key: CAMEL-12871
> URL: https://issues.apache.org/jira/browse/CAMEL-12871
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 2.21.1, 3.7.0
>Reporter: Hemang Ajmera
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.7.1, 3.8.0
>
>
> h1. Summary
> Salesforce component tries to reconnect to salesforce, if it gets disconnect.
> Most of the time it is succeeded. However, there is case when re-connect does
> not work. At that time salesforce component drops the topic which is
> subscribe and reconnects back. Everything looks normal again, however, no new
> streaming messages are received, as the component has dropped the topic.
> h1. Observation
> Here is the logs which show good reconnect. We can see that camel attempts to
> subscribe to topic /topic/AccountOwner
> {quote}
> 2018-09-12 02:54:23.530 DEBUG 1 --- [ent@2362f559-20]
> o.a.c.c.s.i.s.SubscriptionHelper$5 : Received messages
> [{advice={reconnect=handshake, interval=0}, channel=/meta/connect, id=410,
> error=403::Unknown client, successful=false}]
> 2018-09-12 02:54:23.531 DEBUG 1 --- [ent@2362f559-20]
> o.a.c.c.s.i.s.SubscriptionHelper : [CHANNEL:META_CONNECT]:
> {advice={reconnect=handshake, interval=0}, channel=/meta/connect, id=410,
> error=403::Unknown client, successful=false}
> 2018-09-12 02:54:23.531 WARN 1 --- [ent@2362f559-20]
> o.a.c.c.s.i.s.SubscriptionHelper : Connect failure:
> {advice={reconnect=handshake, interval=0}, channel=/meta/connect, id=410,
> error=403::Unknown client, successful=false}
> 2018-09-12 02:54:23.588 DEBUG 1 --- [ent@2362f559-21]
> o.a.c.c.s.i.s.SubscriptionHelper$5 : Received messages
> [{ext={replay=true, payload.format=true}, minimumVersion=1.0,
> clientId=p1t17l7111gqk4p6eff60893qeev,
> supportedConnectionTypes=[Ljava.lang.Object;@471ebac8,
> channel=/meta/handshake, id=411, version=1.0, successful=true}]
> 2018-09-12 02:54:23.589 DEBUG 1 --- [ent@2362f559-21]
> o.a.c.c.s.i.s.SubscriptionHelper : [CHANNEL:META_HANDSHAKE]:
> {ext={replay=true, payload.format=true}, minimumVersion=1.0,
> clientId=p1t17l7111gqk4p6eff60893qeev,
> supportedConnectionTypes=[Ljava.lang.Object;@471ebac8,
> channel=/meta/handshake, id=411, version=1.0, successful=true}
> 2018-09-12 02:54:23.625 DEBUG 1 --- [ent@2362f559-20]
> o.a.c.c.s.i.s.SubscriptionHelper$5 : Received messages
> [{clientId=p1t17l7111gqk4p6eff60893qeev, advice={reconnect=retry, interval=0,
> timeout=11}, channel=/meta/connect, id=412, successful=true}]
> 2018-09-12 02:54:23.625 DEBUG 1 --- [ent@2362f559-20]
> o.a.c.c.s.i.s.SubscriptionHelper : [CHANNEL:META_CONNECT]:
> {clientId=p1t17l7111gqk4p6eff60893qeev, advice={reconnect=retry, interval=0,
> timeout=11}, channel=/meta/connect, id=412, successful=true}
> 2018-09-12 02:54:23.625 DEBUG 1 --- [ent@2362f559-20]
> o.a.c.c.s.i.s.SubscriptionHelper : Refreshing subscriptions to 1
> channels on reconnect
> 2018-09-12 02:54:23.626 INFO 1 --- [ent@2362f559-20]
> o.a.c.c.s.i.s.SubscriptionHelper : Set Replay extension to replay
> from `-2` for channel `/topic/AccountOwners`
> 2018-09-12 02:54:23.626 INFO 1 --- [ent@2362f559-20]
> o.a.c.c.s.i.s.SubscriptionHelper : Subscribing to channel
> /topic/AccountOwners...
> 2018-09-12 02:54:23.693 DEBUG 1 --- [ent@2362f559-21]
> o.a.c.c.s.i.s.SubscriptionHelper$5 : Received messages
> [{clientId=p1t17l7111gqk4p6eff60893qeev, channel=/meta/subscribe, id=413,
> subscription=/topic/AccountOwners, successful=true}]
> 2018-09-12 02:54:23.693 DEBUG 1 --- [ent@2362f559-21]
> o.a.c.c.s.i.s.SubscriptionHelper : [CHANNEL:META_SUBSCRIBE]:
> {clientId=p1t17l7111gqk4p6eff60893qeev, channel=/meta/subscribe, id=413,
> subscription=/topic/AccountOwners, successful=true}
> 2018-09-12 02:54:23.693 INFO 1 --- [ent@2362f559-21]
> o.a.c.c.s.i.s.SubscriptionHelper : Subscribed to channel
> /topic/AccountOwners
> 2018-09-12 02:54:25.453 DEBUG 1 --- [ent@2362f559-20]
> o.a.c.c.s.i.s.SubscriptionHelper$5 : Received messages
> {quote}
> Here is the logs which shows connection fails. Camel tries to reconnect, but
> fails. Then camel reconnects after dropping the topic. After this incident,
> no new messages are received.
> {quote}
> 2018-09-22 05:26:17.121 WARN 1 --- [ent@2362f559-23]
>
[jira] [Commented] (CAMEL-15948) camel-website - Quarkus examples are empty
[
https://issues.apache.org/jira/browse/CAMEL-15948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251725#comment-17251725
]
Zoran Regvart commented on CAMEL-15948:
---
I _think_ we could replace the {{indexTable}} with {{jsonpathTable}} from
[asciidoctor-jsonpath|https://gitlab.com/djencks/asciidoctor-jsonpath] and keep
the {{examples.json}} as an attachment in the camel-quarkus-examples/doc. Let
me prototype this.
> camel-website - Quarkus examples are empty
> --
>
> Key: CAMEL-15948
> URL: https://issues.apache.org/jira/browse/CAMEL-15948
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: Claus Ibsen
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 3.8.0
>
>
> The table is empty at
> https://camel.apache.org/camel-quarkus/latest/user-guide/examples.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15948) camel-website - Quarkus examples are empty
[
https://issues.apache.org/jira/browse/CAMEL-15948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251721#comment-17251721
]
Zoran Regvart commented on CAMEL-15948:
---
[~ppalaga] I think a Antora/Asciidoctor.js extension could do the trick.
Perhaps the easiest way would be to grab a JSON file via raw view of the file
from GitHub, something like
https://raw.githubusercontent.com/apache/camel-quarkus-examples/master/docs/examples.json
so we can replace the {{master}} with the version if we publish non-latest
versions of docs.
> camel-website - Quarkus examples are empty
> --
>
> Key: CAMEL-15948
> URL: https://issues.apache.org/jira/browse/CAMEL-15948
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: Claus Ibsen
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 3.8.0
>
>
> The table is empty at
> https://camel.apache.org/camel-quarkus/latest/user-guide/examples.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-15970) Create a check to make sure URLs remain backward compatible
Zoran Regvart created CAMEL-15970: - Summary: Create a check to make sure URLs remain backward compatible Key: CAMEL-15970 URL: https://issues.apache.org/jira/browse/CAMEL-15970 Project: Camel Issue Type: Bug Components: website Reporter: Zoran Regvart Assignee: Zoran Regvart When we re-organize content on the website we might accidentally shuffle the URLs around. We do check if within the website links are not broken, but we could also check if we changed any of the URLs so we know we broke links from other websites pointing to Camel and that we might need to add a redirect from old to the new content. Perhaps looking up the current sitemap and the built sitemap on the pull request might be a way to check for any changes in the URL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15948) camel-website - Quarkus examples are empty
[ https://issues.apache.org/jira/browse/CAMEL-15948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251681#comment-17251681 ] Zoran Regvart commented on CAMEL-15948: --- How about we revert 6d7935f81ca45b0a46a478ebcc657ed530a6a24e and work on getting the data for the table outside of Asciidoc, perhaps pull in a JSON file generated in the examples repository? > camel-website - Quarkus examples are empty > -- > > Key: CAMEL-15948 > URL: https://issues.apache.org/jira/browse/CAMEL-15948 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Assignee: Peter Palaga >Priority: Major > Fix For: 3.8.0 > > > The table is empty at > https://camel.apache.org/camel-quarkus/latest/user-guide/examples.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15948) camel-website - Quarkus examples are empty
[ https://issues.apache.org/jira/browse/CAMEL-15948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251683#comment-17251683 ] Zoran Regvart commented on CAMEL-15948: --- Oh, and to answer the question, I don't think there would be any way of content being in the catalog and not build. We could remove it from the menu by changing the template, we do custom sort now for example, but I'd rather not build what we don't publish as HTML on the website. I'm worried that we'll end up with long build times otherwise, they are pretty long as it is. > camel-website - Quarkus examples are empty > -- > > Key: CAMEL-15948 > URL: https://issues.apache.org/jira/browse/CAMEL-15948 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Assignee: Peter Palaga >Priority: Major > Fix For: 3.8.0 > > > The table is empty at > https://camel.apache.org/camel-quarkus/latest/user-guide/examples.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15948) camel-website - Quarkus examples are empty
[
https://issues.apache.org/jira/browse/CAMEL-15948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17249581#comment-17249581
]
Zoran Regvart commented on CAMEL-15948:
---
With CAMEL-15929
(https://github.com/apache/camel-website/commit/6d7935f81ca45b0a46a478ebcc657ed530a6a24e)
we no longer build quarkus examples Antora component for the website, not sure
how
[this|https://github.com/apache/camel-quarkus/blob/99e8b13efa8cb5908e22028e5ba572833aa65228/docs/modules/ROOT/pages/user-guide/examples.adoc#L17]
{{indexTable}} extension works, but I think it needs those Asciidoc pages to
be part of the site's content catalog to work. Not sure if there is a way not
to build the examples but also have the pages present in the site's content
catalog.
> camel-website - Quarkus examples are empty
> --
>
> Key: CAMEL-15948
> URL: https://issues.apache.org/jira/browse/CAMEL-15948
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: Claus Ibsen
>Assignee: Peter Palaga
>Priority: Major
> Fix For: 3.8.0
>
>
> The table is empty at
> https://camel.apache.org/camel-quarkus/latest/user-guide/examples.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (CAMEL-15945) Don't require sObjectName or sObjectClass when streaming with raw payload
[
https://issues.apache.org/jira/browse/CAMEL-15945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-15945 started by Zoran Regvart.
-
> Don't require sObjectName or sObjectClass when streaming with raw payload
> -
>
> Key: CAMEL-15945
> URL: https://issues.apache.org/jira/browse/CAMEL-15945
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Fix For: 3.7.1
>
>
> We should not require {{sObjectName}} and {{sObjectClass}} parameters if
> {{rawPayload}} is set to {{true}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-15945) Don't require sObjectName or sObjectClass when streaming with raw payload
Zoran Regvart created CAMEL-15945:
-
Summary: Don't require sObjectName or sObjectClass when streaming
with raw payload
Key: CAMEL-15945
URL: https://issues.apache.org/jira/browse/CAMEL-15945
Project: Camel
Issue Type: Bug
Components: camel-salesforce
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Fix For: 3.7.1
We should not require {{sObjectName}} and {{sObjectClass}} parameters if
{{rawPayload}} is set to {{true}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-15944) Edit this page link no longer takes page-source attribute to account
[
https://issues.apache.org/jira/browse/CAMEL-15944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-15944.
---
Resolution: Fixed
Should be fixed in couple of mins.
> Edit this page link no longer takes page-source attribute to account
>
>
> Key: CAMEL-15944
> URL: https://issues.apache.org/jira/browse/CAMEL-15944
> Project: Camel
> Issue Type: Bug
> Components: website
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>
> Seems that we no longer look at {{page-source}} attribute to point to the
> correct document to edit from the "Edit this page" link on the website.
> For example if I click on "Edit this page" on
> https://camel.apache.org/components/latest/telegram-component.html I'm taken
> to
> https://github.com/apache/camel/edit/master/docs/components/modules/ROOT/pages/telegram-component.adoc,
> I should have been taken to
> https://github.com/apache/camel/edit/master/components/camel-telegram/src/main/docs/telegram-component.adoc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (CAMEL-15944) Edit this page link no longer takes page-source attribute to account
[
https://issues.apache.org/jira/browse/CAMEL-15944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-15944 started by Zoran Regvart.
-
> Edit this page link no longer takes page-source attribute to account
>
>
> Key: CAMEL-15944
> URL: https://issues.apache.org/jira/browse/CAMEL-15944
> Project: Camel
> Issue Type: Bug
> Components: website
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>
> Seems that we no longer look at {{page-source}} attribute to point to the
> correct document to edit from the "Edit this page" link on the website.
> For example if I click on "Edit this page" on
> https://camel.apache.org/components/latest/telegram-component.html I'm taken
> to
> https://github.com/apache/camel/edit/master/docs/components/modules/ROOT/pages/telegram-component.adoc,
> I should have been taken to
> https://github.com/apache/camel/edit/master/components/camel-telegram/src/main/docs/telegram-component.adoc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-15944) Edit this page link no longer takes page-source attribute to account
Zoran Regvart created CAMEL-15944:
-
Summary: Edit this page link no longer takes page-source attribute
to account
Key: CAMEL-15944
URL: https://issues.apache.org/jira/browse/CAMEL-15944
Project: Camel
Issue Type: Bug
Components: website
Reporter: Zoran Regvart
Assignee: Zoran Regvart
Seems that we no longer look at {{page-source}} attribute to point to the
correct document to edit from the "Edit this page" link on the website.
For example if I click on "Edit this page" on
https://camel.apache.org/components/latest/telegram-component.html I'm taken to
https://github.com/apache/camel/edit/master/docs/components/modules/ROOT/pages/telegram-component.adoc,
I should have been taken to
https://github.com/apache/camel/edit/master/components/camel-telegram/src/main/docs/telegram-component.adoc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-15929) camel-website - Project names in bottom left menu
[ https://issues.apache.org/jira/browse/CAMEL-15929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-15929. --- Resolution: Done Last of the changes should be visible on the website in 15mins or so, when the build completes. > camel-website - Project names in bottom left menu > - > > Key: CAMEL-15929 > URL: https://issues.apache.org/jira/browse/CAMEL-15929 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot 2020-12-09 at 11.23.04.png > > > Apache Camel K -> Camel K > Apache Camel Karaf -> Camel Karaf > Camel Quarkus Examples -> SHOULD BE REMOVED > Camel Spring Boot Starters -> Camel Spring Boot > And can we order them so Camel Components are in the top? > Camel Components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15364) Duplicate pages title within Components 2.x
[ https://issues.apache.org/jira/browse/CAMEL-15364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-15364. --- Resolution: Fixed > Duplicate pages title within Components 2.x > > > Key: CAMEL-15364 > URL: https://issues.apache.org/jira/browse/CAMEL-15364 > Project: Camel > Issue Type: Task > Components: website >Reporter: Aemie >Priority: Minor > > Within the Components section version 2.x, there are 2 pages pertaining to > MongoDB. The links are - > * [https://camel.apache.org/components/2.x/mongodb3-component.html] > * [https://camel.apache.org/components/2.x/mongodb-component.html] > These 2 differentiate in a sub-top however having the same title doesn't seem > appropriate. > Other thing I have noticed is that bundling of similar components has taken > place with the latest and 3.4.x version but not with the 2.x version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15419) camel-website build instructions: yarn format not found
[
https://issues.apache.org/jira/browse/CAMEL-15419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart resolved CAMEL-15419.
---
Resolution: Fixed
We improved the build process and the documentation in the README.
> camel-website build instructions: yarn format not found
> ---
>
> Key: CAMEL-15419
> URL: https://issues.apache.org/jira/browse/CAMEL-15419
> Project: Camel
> Issue Type: Bug
> Components: website
>Reporter: Ahmed M
>Priority: Minor
>
> In camel-website README.md (under Build the website content) we are told to
> use *yarn format* command to format the code, but this command is not defined
> :
> {{$ yarn format}}
> {{yarn run v1.22.0}}
> {{error Command "format" not found.}}
> {{info Visit [https://yarnpkg.com/en/docs/cli/run] for documentation about
> this command.}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (CAMEL-15929) camel-website - Project names in bottom left menu
[ https://issues.apache.org/jira/browse/CAMEL-15929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15929 started by Zoran Regvart. - > camel-website - Project names in bottom left menu > - > > Key: CAMEL-15929 > URL: https://issues.apache.org/jira/browse/CAMEL-15929 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot 2020-12-09 at 11.23.04.png > > > Apache Camel K -> Camel K > Apache Camel Karaf -> Camel Karaf > Camel Quarkus Examples -> SHOULD BE REMOVED > Camel Spring Boot Starters -> Camel Spring Boot > And can we order them so Camel Components are in the top? > Camel Components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15929) camel-website - Project names in bottom left menu
[ https://issues.apache.org/jira/browse/CAMEL-15929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246711#comment-17246711 ] Zoran Regvart commented on CAMEL-15929: --- The only thing is the removal of Camel Quarkus Examples component, waiting on feedback from [~ppalaga] on that. > camel-website - Project names in bottom left menu > - > > Key: CAMEL-15929 > URL: https://issues.apache.org/jira/browse/CAMEL-15929 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot 2020-12-09 at 11.23.04.png > > > Apache Camel K -> Camel K > Apache Camel Karaf -> Camel Karaf > Camel Quarkus Examples -> SHOULD BE REMOVED > Camel Spring Boot Starters -> Camel Spring Boot > And can we order them so Camel Components are in the top? > Camel Components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15929) camel-website - Project names in bottom left menu
[ https://issues.apache.org/jira/browse/CAMEL-15929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246520#comment-17246520 ] Zoran Regvart commented on CAMEL-15929: --- The order of components is determined by title, they're sorted by it alphabetically (https://gitlab.com/antora/antora/-/blob/1c4089164b11f5a7ed70960188ed9dcd52d52d07/packages/page-composer/lib/build-ui-model.js#L51). We can add our own ordering in the partial used in the theme. I'd set the manual first, component reference second, and the rest of the documentation components in alphabetical order. Does that make sense [~davsclaus]? > camel-website - Project names in bottom left menu > - > > Key: CAMEL-15929 > URL: https://issues.apache.org/jira/browse/CAMEL-15929 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot 2020-12-09 at 11.23.04.png > > > Apache Camel K -> Camel K > Apache Camel Karaf -> Camel Karaf > Camel Quarkus Examples -> SHOULD BE REMOVED > Camel Spring Boot Starters -> Camel Spring Boot > And can we order them so Camel Components are in the top? > Camel Components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15929) camel-website - Project names in bottom left menu
[
https://issues.apache.org/jira/browse/CAMEL-15929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246493#comment-17246493
]
Zoran Regvart commented on CAMEL-15929:
---
Just found out that I can also add LTS via {{display_version}}, so I'll do that
as well, for example for Camel Components, Camel Spring Boot and Camel Karaf,
we can have "3.4.x (LTS)" as version.
> camel-website - Project names in bottom left menu
> -
>
> Key: CAMEL-15929
> URL: https://issues.apache.org/jira/browse/CAMEL-15929
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: Claus Ibsen
>Assignee: Zoran Regvart
>Priority: Major
> Attachments: Screenshot 2020-12-09 at 11.23.04.png
>
>
> Apache Camel K -> Camel K
> Apache Camel Karaf -> Camel Karaf
> Camel Quarkus Examples -> SHOULD BE REMOVED
> Camel Spring Boot Starters -> Camel Spring Boot
> And can we order them so Camel Components are in the top?
> Camel Components
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15929) camel-website - Project names in bottom left menu
[ https://issues.apache.org/jira/browse/CAMEL-15929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246461#comment-17246461 ] Zoran Regvart commented on CAMEL-15929: --- [~ppalaga] are you okay with the removal of Camel Quarkus examples? > camel-website - Project names in bottom left menu > - > > Key: CAMEL-15929 > URL: https://issues.apache.org/jira/browse/CAMEL-15929 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot 2020-12-09 at 11.23.04.png > > > Apache Camel K -> Camel K > Apache Camel Karaf -> Camel Karaf > Camel Quarkus Examples -> SHOULD BE REMOVED > Camel Spring Boot Starters -> Camel Spring Boot > And can we order them so Camel Components are in the top? > Camel Components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15929) camel-website - Project names in bottom left menu
[ https://issues.apache.org/jira/browse/CAMEL-15929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246459#comment-17246459 ] Zoran Regvart commented on CAMEL-15929: --- Sure thing, I'll look into this. > camel-website - Project names in bottom left menu > - > > Key: CAMEL-15929 > URL: https://issues.apache.org/jira/browse/CAMEL-15929 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot 2020-12-09 at 11.23.04.png > > > Apache Camel K -> Camel K > Apache Camel Karaf -> Camel Karaf > Camel Quarkus Examples -> SHOULD BE REMOVED > Camel Spring Boot Starters -> Camel Spring Boot > And can we order them so Camel Components are in the top? > Camel Components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15898) Camel Website search is broken
[ https://issues.apache.org/jira/browse/CAMEL-15898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-15898. --- Resolution: Fixed Algolia folk merged the PR, the search index now contains lvl0-lvl3 data as can be seen on the live website. Thanks for reporting! > Camel Website search is broken > -- > > Key: CAMEL-15898 > URL: https://issues.apache.org/jira/browse/CAMEL-15898 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Aashna Jena >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot from 2020-11-27 14-21-45.png > > > I can see NULLs in place of headings, although the content seems to be fine. > Blogs, Articles, Books (all Hugo content) etc are rendering fine, but > Components and sub project headings are not appearing. Has there been a > change is the organization of Antora content? Else this may be a problem from > the Algolia side. > !Screenshot from 2020-11-27 14-21-45.png|width=267,height=444! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15913) spurious content in /releases/ pages
[ https://issues.apache.org/jira/browse/CAMEL-15913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-15913. --- Resolution: Fixed Thanks for reporting! > spurious content in /releases/ pages > > > Key: CAMEL-15913 > URL: https://issues.apache.org/jira/browse/CAMEL-15913 > Project: Camel > Issue Type: Task > Components: website >Reporter: Sebb >Assignee: Zoran Regvart >Priority: Trivial > > The prior releases pages contain some spurious text: > '3.4.4 3.6.0 2.25.2' > This appears just after the 'camel-spring-boot-dependencies' section above > the 'APACHE CAMEL' heading > See for example: > https://deploy-preview-500--camel.netlify.app/releases/release-2.22.0/ > and > https://deploy-preview-500--camel.netlify.app/releases/release-3.6.0/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15921) Add related posts to the end of the blog post
[ https://issues.apache.org/jira/browse/CAMEL-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-15921. --- Resolution: Implemented > Add related posts to the end of the blog post > - > > Key: CAMEL-15921 > URL: https://issues.apache.org/jira/browse/CAMEL-15921 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Minor > > Would be nice to offer a selection of related blog posts at the bottom of a > blog post. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-15921) Add related posts to the end of the blog post
[ https://issues.apache.org/jira/browse/CAMEL-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15921 started by Zoran Regvart. - > Add related posts to the end of the blog post > - > > Key: CAMEL-15921 > URL: https://issues.apache.org/jira/browse/CAMEL-15921 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Minor > > Would be nice to offer a selection of related blog posts at the bottom of a > blog post. -- This message was sent by Atlassian Jira (v8.3.4#803005)
