[jira] [Created] (CAMEL-14766) Rearrange 3.0.x components component similar to latest
David Jencks created CAMEL-14766: Summary: Rearrange 3.0.x components component similar to latest Key: CAMEL-14766 URL: https://issues.apache.org/jira/browse/CAMEL-14766 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.1.0 Reporter: David Jencks Assignee: David Jencks Rearrange website source in the 3.0.x branch for the components component to imitate 'latest' (master) branch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14765) Rearrange 2.x components component similar to latest
David Jencks created CAMEL-14765: Summary: Rearrange 2.x components component similar to latest Key: CAMEL-14765 URL: https://issues.apache.org/jira/browse/CAMEL-14765 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.1.0 Reporter: David Jencks Assignee: David Jencks Rearrange the website sources in the 2.x branch to imitate the components component in the 'latest' (master) branch per CAMEL-14698Consider rearranging site source to Antora norms -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14747) Put all the EIP documentation in one place, and possibly version it.
[
https://issues.apache.org/jira/browse/CAMEL-14747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks resolved CAMEL-14747.
--
Fix Version/s: 3.2.0
Resolution: Fixed
I picked \{14754, 14758} so the EIP docs are in the components component. At
this point it would be very easy to switch to the other configuration.
> Put all the EIP documentation in one place, and possibly version it.
>
>
> Key: CAMEL-14747
> URL: https://issues.apache.org/jira/browse/CAMEL-14747
> Project: Camel
> Issue Type: Improvement
> Components: website
>Affects Versions: 3.1.0
>Reporter: David Jencks
>Assignee: David Jencks
>Priority: Major
> Fix For: 3.2.0
>
>
> * move all the EIP documentation to core/camel-core-engine to be with the
> partially generated documentation. I plan to move pages referencing an EIP
> in
> [http://www.enterpriseintegrationpatterns.com|http://www.enterpriseintegrationpatterns.com/]
> and, if I can find them, other closely related pages.
> * Consider where this module would best live as part of a versioned
> component. It could be added to the components component or made a
> standalone component.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14758) aggregate eip content - camel-website - eip in components component
[ https://issues.apache.org/jira/browse/CAMEL-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14758. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > aggregate eip content - camel-website - eip in components component > --- > > Key: CAMEL-14758 > URL: https://issues.apache.org/jira/browse/CAMEL-14758 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > playbook changes for aggregated eip content as module in components component -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14755) aggregate eip content - 3.0.x branch
[ https://issues.apache.org/jira/browse/CAMEL-14755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14755. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > aggregate eip content - 3.0.x branch > > > Key: CAMEL-14755 > URL: https://issues.apache.org/jira/browse/CAMEL-14755 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > changes for 3.0.x branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14756) aggregate eip content - 2.x branch
[ https://issues.apache.org/jira/browse/CAMEL-14756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14756. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > aggregate eip content - 2.x branch > -- > > Key: CAMEL-14756 > URL: https://issues.apache.org/jira/browse/CAMEL-14756 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > changes for 2.x branch -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14754) aggregate eip content - master branch - part of components component
[ https://issues.apache.org/jira/browse/CAMEL-14754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14754. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > aggregate eip content - master branch - part of components component > > > Key: CAMEL-14754 > URL: https://issues.apache.org/jira/browse/CAMEL-14754 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > This is the same as previous sub-task but with the eip docs as a module in > the components component. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14730) 2.x website source rearrangement
[ https://issues.apache.org/jira/browse/CAMEL-14730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14730. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > 2.x website source rearrangement > > > Key: CAMEL-14730 > URL: https://issues.apache.org/jira/browse/CAMEL-14730 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > task for 2.x branch components website source rearrangement -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14731) camel-website playbook rearrangement
[ https://issues.apache.org/jira/browse/CAMEL-14731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14731. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > camel-website playbook rearrangement > > > Key: CAMEL-14731 > URL: https://issues.apache.org/jira/browse/CAMEL-14731 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > task for playbook changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14729) 3.0.x branch website source rearrangement
[ https://issues.apache.org/jira/browse/CAMEL-14729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14729. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > 3.0.x branch website source rearrangement > - > > Key: CAMEL-14729 > URL: https://issues.apache.org/jira/browse/CAMEL-14729 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > task for 3.0.x website components. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14728) master branch website source rearrangement
[ https://issues.apache.org/jira/browse/CAMEL-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14728. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > master branch website source rearrangement > -- > > Key: CAMEL-14728 > URL: https://issues.apache.org/jira/browse/CAMEL-14728 > Project: Camel > Issue Type: Sub-task > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > sub task for master branch PR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14698) Consider rearranging site source to Antora norms
[ https://issues.apache.org/jira/browse/CAMEL-14698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14698. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > Consider rearranging site source to Antora norms > > > Key: CAMEL-14698 > URL: https://issues.apache.org/jira/browse/CAMEL-14698 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > Consider rearranging the website source .adocs to conform to expected Antora > structure and avoid copying. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14764) header menus missing from antora site
[ https://issues.apache.org/jira/browse/CAMEL-14764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14764. -- Fix Version/s: 3.2.0 Resolution: Fixed Merged PR after approval. > header menus missing from antora site > - > > Key: CAMEL-14764 > URL: https://issues.apache.org/jira/browse/CAMEL-14764 > Project: Camel > Issue Type: Bug > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > menu.js registered on the Antora command line seems to have stopped working > at some point. > It's pretty easy to make this functionality into a helper in the ui bundle, > and it can be simplified quite a bit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14764) header menus missing from antora site
David Jencks created CAMEL-14764: Summary: header menus missing from antora site Key: CAMEL-14764 URL: https://issues.apache.org/jira/browse/CAMEL-14764 Project: Camel Issue Type: Bug Components: website Affects Versions: 3.1.0 Reporter: David Jencks Assignee: David Jencks menu.js registered on the Antora command line seems to have stopped working at some point. It's pretty easy to make this functionality into a helper in the ui bundle, and it can be simplified quite a bit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14763) Allow S3 Consumer to be configured to not return/delete "directories"
Darius Cooper created CAMEL-14763: - Summary: Allow S3 Consumer to be configured to not return/delete "directories" Key: CAMEL-14763 URL: https://issues.apache.org/jira/browse/CAMEL-14763 Project: Camel Issue Type: Improvement Components: camel-aws-s3 Reporter: Darius Cooper Allow S3 Consumer to be configured to not return/delete "empty files" which S3 uses as a way to simulate a folder structure. Since S3 object Content-Type meta-data tells whether the object is a "directory", this can be used to identify and skip such objects. It does mean that the number of objects returned could be less than the maxMessagesPerPoll. As long as this is not the default and the docs explain what to expect, I believe this would be okay. Wanted to create a JIRA to see if there was an architectural objection to adding such a feature. If not, Ill try submitting a PR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14762) camel-core - Configurer to include API for method name and type
Claus Ibsen created CAMEL-14762: --- Summary: camel-core - Configurer to include API for method name and type Key: CAMEL-14762 URL: https://issues.apache.org/jira/browse/CAMEL-14762 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.2.0 This allows some more reflection free configuration if we can know by name/type the options a given component, configuration etc may have. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14747) Put all the EIP documentation in one place, and possibly version it.
[
https://issues.apache.org/jira/browse/CAMEL-14747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063994#comment-17063994
]
David Jencks commented on CAMEL-14747:
--
We need to pick one of \{14753, 14757} and \{14754, 14758}.
> Put all the EIP documentation in one place, and possibly version it.
>
>
> Key: CAMEL-14747
> URL: https://issues.apache.org/jira/browse/CAMEL-14747
> Project: Camel
> Issue Type: Improvement
> Components: website
>Affects Versions: 3.1.0
>Reporter: David Jencks
>Assignee: David Jencks
>Priority: Major
>
> * move all the EIP documentation to core/camel-core-engine to be with the
> partially generated documentation. I plan to move pages referencing an EIP
> in
> [http://www.enterpriseintegrationpatterns.com|http://www.enterpriseintegrationpatterns.com/]
> and, if I can find them, other closely related pages.
> * Consider where this module would best live as part of a versioned
> component. It could be added to the components component or made a
> standalone component.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14760) camel-main - Generate configurer for its own options
[ https://issues.apache.org/jira/browse/CAMEL-14760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14760. - Resolution: Fixed > camel-main - Generate configurer for its own options > > > Key: CAMEL-14760 > URL: https://issues.apache.org/jira/browse/CAMEL-14760 > Project: Camel > Issue Type: Improvement > Components: camel-main >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.2.0 > > > As an experiment, then lets look at generating a reflection free configurer > for the camel-main own options. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14760) camel-main - Generate configurer for its own options
[ https://issues.apache.org/jira/browse/CAMEL-14760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063968#comment-17063968 ] Claus Ibsen commented on CAMEL-14760: - Also for camelcontext itself, eg camel.context.xxx now has a configurer class via camel-main > camel-main - Generate configurer for its own options > > > Key: CAMEL-14760 > URL: https://issues.apache.org/jira/browse/CAMEL-14760 > Project: Camel > Issue Type: Improvement > Components: camel-main >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.2.0 > > > As an experiment, then lets look at generating a reflection free configurer > for the camel-main own options. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14761) JPAMessageIdRepository Not Releasing Connections for contains() method
[ https://issues.apache.org/jira/browse/CAMEL-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14761. - Fix Version/s: 3.2.0 Resolution: Fixed > JPAMessageIdRepository Not Releasing Connections for contains() method > -- > > Key: CAMEL-14761 > URL: https://issues.apache.org/jira/browse/CAMEL-14761 > Project: Camel > Issue Type: Bug > Components: camel-jpa >Affects Versions: 3.1.0 >Reporter: Michal Zabielski >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > When using the JpaMessageIdRepository for an idempotent repo (or > inProgressRepo) for file processing it holds onto connections on contains() > method. Other methods add(), remove(), etc. were fixed in CAMEL-11630. > > Proposed fix: adjust contains() method in the same manner as other methods -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14761) JPAMessageIdRepository Not Releasing Connections for contains() method
[ https://issues.apache.org/jira/browse/CAMEL-14761?focusedWorklogId=407415=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-407415 ] ASF GitHub Bot logged work on CAMEL-14761: -- Author: ASF GitHub Bot Created on: 21/Mar/20 12:34 Start Date: 21/Mar/20 12:34 Worklog Time Spent: 10m Work Description: davsclaus commented on pull request #3662: CAMEL-14761 JPAMessageIdRepository.contains() release db connection fix URL: https://github.com/apache/camel/pull/3662 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 407415) Time Spent: 20m (was: 10m) > JPAMessageIdRepository Not Releasing Connections for contains() method > -- > > Key: CAMEL-14761 > URL: https://issues.apache.org/jira/browse/CAMEL-14761 > Project: Camel > Issue Type: Bug > Components: camel-jpa >Affects Versions: 3.1.0 >Reporter: Michal Zabielski >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > When using the JpaMessageIdRepository for an idempotent repo (or > inProgressRepo) for file processing it holds onto connections on contains() > method. Other methods add(), remove(), etc. were fixed in CAMEL-11630. > > Proposed fix: adjust contains() method in the same manner as other methods -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063879#comment-17063879 ] Aemie commented on CAMEL-13812: --- I really think the proposal of the entire layout is pretty good. I would love to help you people out in this. > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, > getting-started-with-apache-camel.docx > > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14761) JPAMessageIdRepository Not Releasing Connections for contains() method
[ https://issues.apache.org/jira/browse/CAMEL-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063872#comment-17063872 ] Michal Zabielski commented on CAMEL-14761: -- PR: [https://github.com/apache/camel/pull/3662] > JPAMessageIdRepository Not Releasing Connections for contains() method > -- > > Key: CAMEL-14761 > URL: https://issues.apache.org/jira/browse/CAMEL-14761 > Project: Camel > Issue Type: Bug > Components: camel-jpa >Affects Versions: 3.1.0 >Reporter: Michal Zabielski >Assignee: Claus Ibsen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When using the JpaMessageIdRepository for an idempotent repo (or > inProgressRepo) for file processing it holds onto connections on contains() > method. Other methods add(), remove(), etc. were fixed in CAMEL-11630. > > Proposed fix: adjust contains() method in the same manner as other methods -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14761) JPAMessageIdRepository Not Releasing Connections for contains() method
[ https://issues.apache.org/jira/browse/CAMEL-14761?focusedWorklogId=407411=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-407411 ] ASF GitHub Bot logged work on CAMEL-14761: -- Author: ASF GitHub Bot Created on: 21/Mar/20 12:00 Start Date: 21/Mar/20 12:00 Worklog Time Spent: 10m Work Description: kosciej commented on pull request #3662: CAMEL-14761 JPAMessageIdRepository.contains() release db connection fix URL: https://github.com/apache/camel/pull/3662 Fix for: [CAMEL-14761](https://issues.apache.org/jira/browse/CAMEL-14761) Issue: When using the JpaMessageIdRepository for an idempotent repo (or inProgressRepo) for file processing it holds onto connections on contains() method. Other methods add(), remove(), etc. were fixed in CAMEL-11630. PR: code fixed in the same way as it was fixed for methods add(), remove(), etc. in: [CAMEL-11630](https://issues.apache.org/jira/browse/CAMEL-11630), [PR](https://github.com/apache/camel/pull/1883) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 407411) Remaining Estimate: 0h Time Spent: 10m > JPAMessageIdRepository Not Releasing Connections for contains() method > -- > > Key: CAMEL-14761 > URL: https://issues.apache.org/jira/browse/CAMEL-14761 > Project: Camel > Issue Type: Bug > Components: camel-jpa >Affects Versions: 3.1.0 >Reporter: Michal Zabielski >Assignee: Claus Ibsen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When using the JpaMessageIdRepository for an idempotent repo (or > inProgressRepo) for file processing it holds onto connections on contains() > method. Other methods add(), remove(), etc. were fixed in CAMEL-11630. > > Proposed fix: adjust contains() method in the same manner as other methods -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14761) JPAMessageIdRepository Not Releasing Connections for contains() method
[ https://issues.apache.org/jira/browse/CAMEL-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Zabielski updated CAMEL-14761: - Description: When using the JpaMessageIdRepository for an idempotent repo (or inProgressRepo) for file processing it holds onto connections on contains() method. Other methods add(), remove(), etc. were fixed in CAMEL-11630. Proposed fix: adjust contains() method in the same manner as other methods was:When using the JpaMessageIdRepository for an idempotent repo for file processing it holds onto connections on contains() method. Other methods add(), remove(), etc. were fixed in > JPAMessageIdRepository Not Releasing Connections for contains() method > -- > > Key: CAMEL-14761 > URL: https://issues.apache.org/jira/browse/CAMEL-14761 > Project: Camel > Issue Type: Bug > Components: camel-jpa >Affects Versions: 3.1.0 >Reporter: Michal Zabielski >Assignee: Claus Ibsen >Priority: Major > > When using the JpaMessageIdRepository for an idempotent repo (or > inProgressRepo) for file processing it holds onto connections on contains() > method. Other methods add(), remove(), etc. were fixed in CAMEL-11630. > > Proposed fix: adjust contains() method in the same manner as other methods -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14761) JPAMessageIdRepository Not Releasing Connections for contains() method
[ https://issues.apache.org/jira/browse/CAMEL-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Zabielski updated CAMEL-14761: - Description: When using the JpaMessageIdRepository for an idempotent repo for file processing it holds onto connections on contains() method. Other methods add(), remove(), etc. were fixed in (was: When using the JpaMessageIdRepository for an idempotent repo for file processing it holds onto connections on contains method. ) > JPAMessageIdRepository Not Releasing Connections for contains() method > -- > > Key: CAMEL-14761 > URL: https://issues.apache.org/jira/browse/CAMEL-14761 > Project: Camel > Issue Type: Bug > Components: camel-jpa >Affects Versions: 3.1.0 >Reporter: Michal Zabielski >Assignee: Claus Ibsen >Priority: Major > > When using the JpaMessageIdRepository for an idempotent repo for file > processing it holds onto connections on contains() method. Other methods > add(), remove(), etc. were fixed in -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14761) JPAMessageIdRepository Not Releasing Connections for contains() method
[ https://issues.apache.org/jira/browse/CAMEL-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Zabielski updated CAMEL-14761: - Fix Version/s: (was: 2.19.3) (was: 2.18.5) (was: 2.20.0) > JPAMessageIdRepository Not Releasing Connections for contains() method > -- > > Key: CAMEL-14761 > URL: https://issues.apache.org/jira/browse/CAMEL-14761 > Project: Camel > Issue Type: Bug > Components: camel-jpa >Affects Versions: 2.19.1 >Reporter: Michal Zabielski >Assignee: Claus Ibsen >Priority: Major > > When using the JpaMessageIdRepository for an idempotent repo for file > processing it holds onto connections and does not release them unless you > manually flush the connection pool. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14761) JPAMessageIdRepository Not Releasing Connections for contains() method
Michal Zabielski created CAMEL-14761: Summary: JPAMessageIdRepository Not Releasing Connections for contains() method Key: CAMEL-14761 URL: https://issues.apache.org/jira/browse/CAMEL-14761 Project: Camel Issue Type: Bug Components: camel-jpa Affects Versions: 2.19.1 Reporter: Michal Zabielski Assignee: Claus Ibsen Fix For: 2.18.5, 2.19.3, 2.20.0 When using the JpaMessageIdRepository for an idempotent repo for file processing it holds onto connections and does not release them unless you manually flush the connection pool. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14761) JPAMessageIdRepository Not Releasing Connections for contains() method
[ https://issues.apache.org/jira/browse/CAMEL-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Zabielski updated CAMEL-14761: - Affects Version/s: (was: 2.19.1) 3.1.0 > JPAMessageIdRepository Not Releasing Connections for contains() method > -- > > Key: CAMEL-14761 > URL: https://issues.apache.org/jira/browse/CAMEL-14761 > Project: Camel > Issue Type: Bug > Components: camel-jpa >Affects Versions: 3.1.0 >Reporter: Michal Zabielski >Assignee: Claus Ibsen >Priority: Major > > When using the JpaMessageIdRepository for an idempotent repo for file > processing it holds onto connections and does not release them unless you > manually flush the connection pool. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14761) JPAMessageIdRepository Not Releasing Connections for contains() method
[ https://issues.apache.org/jira/browse/CAMEL-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Zabielski updated CAMEL-14761: - Description: When using the JpaMessageIdRepository for an idempotent repo for file processing it holds onto connections on contains method. (was: When using the JpaMessageIdRepository for an idempotent repo for file processing it holds onto connections and does not release them unless you manually flush the connection pool.) > JPAMessageIdRepository Not Releasing Connections for contains() method > -- > > Key: CAMEL-14761 > URL: https://issues.apache.org/jira/browse/CAMEL-14761 > Project: Camel > Issue Type: Bug > Components: camel-jpa >Affects Versions: 3.1.0 >Reporter: Michal Zabielski >Assignee: Claus Ibsen >Priority: Major > > When using the JpaMessageIdRepository for an idempotent repo for file > processing it holds onto connections on contains method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063836#comment-17063836 ] Aashna Jena commented on CAMEL-13812: - I like the idea. Shall we start working on this? > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, > getting-started-with-apache-camel.docx > > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14760) camel-main - Generate configurer for its own options
Claus Ibsen created CAMEL-14760: --- Summary: camel-main - Generate configurer for its own options Key: CAMEL-14760 URL: https://issues.apache.org/jira/browse/CAMEL-14760 Project: Camel Issue Type: Improvement Components: camel-main Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.2.0 As an experiment, then lets look at generating a reflection free configurer for the camel-main own options. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14759) Some pages dont have navbar menu items
Prerna Singh created CAMEL-14759: Summary: Some pages dont have navbar menu items Key: CAMEL-14759 URL: https://issues.apache.org/jira/browse/CAMEL-14759 Project: Camel Issue Type: Bug Components: website Reporter: Prerna Singh Attachments: image-2020-03-21-14-11-49-451.png As I was skimming through the website, I found that some pages under "documentation" ,don't have menu-items in the navbar and hence the navbar-burger does not yield anything on being clicked on smaller resolutions. !image-2020-03-21-14-11-49-451.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
