[jira] [Updated] (CAMEL-6555) camel-netty - Upgrade to Netty 4
[ https://issues.apache.org/jira/browse/CAMEL-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-6555: --- Fix Version/s: (was: 2.13.0) Future Yeah its not being developed right now. Moving to a future release as we might as well jump straight to Netty 5, since they are already working on that with a new revised API. The effort of upgrading camel-netty to Netty 4/5 API is big, and hence not something you can easily do in a short time. camel-netty - Upgrade to Netty 4 Key: CAMEL-6555 URL: https://issues.apache.org/jira/browse/CAMEL-6555 Project: Camel Issue Type: Task Components: camel-netty Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: Future Netty 4.0 has been released. We should upgrade, though it has new package names. So end users with custom codec need to migrate as well. So we could indicate that after Camel 2.12 we upgrade to give ppl amble time to adjust. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CAMEL-6555) camel-netty - Upgrade to Netty 4 or 5
[ https://issues.apache.org/jira/browse/CAMEL-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-6555: --- Summary: camel-netty - Upgrade to Netty 4 or 5 (was: camel-netty - Upgrade to Netty 4) camel-netty - Upgrade to Netty 4 or 5 - Key: CAMEL-6555 URL: https://issues.apache.org/jira/browse/CAMEL-6555 Project: Camel Issue Type: Task Components: camel-netty Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: Future Netty 4.0 has been released. We should upgrade, though it has new package names. So end users with custom codec need to migrate as well. So we could indicate that after Camel 2.12 we upgrade to give ppl amble time to adjust. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CAMEL-6004) Tokenize XML does not support self-closing XML tokens
[ https://issues.apache.org/jira/browse/CAMEL-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13861407#comment-13861407 ] subrata commented on CAMEL-6004: Thanks Aki. The current service mix is using Version 2.10.7 of Camel. So I guess we need to wait for the next service mix release. Tokenize XML does not support self-closing XML tokens - Key: CAMEL-6004 URL: https://issues.apache.org/jira/browse/CAMEL-6004 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.2 Reporter: Greg Heidorn Assignee: Willem Jiang Priority: Minor Fix For: 2.10.6, 2.11.1, 2.12.0 Attachments: GenericTokenizeTest.java, camel-6004.patch Tokenize creates non-well-formed XML when handling self-closing XML tokens. Tokenize should support parsing tokens that are either have a closing tag or are self-closing. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CAMEL-7067) JcrProducer should not store all exchange properties in the target JCR node
[ https://issues.apache.org/jira/browse/CAMEL-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregor Zurowski updated CAMEL-7067: --- Assignee: Gregor Zurowski (was: Claus Ibsen) JcrProducer should not store all exchange properties in the target JCR node --- Key: CAMEL-7067 URL: https://issues.apache.org/jira/browse/CAMEL-7067 Project: Camel Issue Type: Improvement Components: camel-jcr Affects Versions: 2.12.2 Reporter: Gregor Zurowski Assignee: Gregor Zurowski Fix For: 2.12.3, 2.13.0 Attachments: CAMEL-7067-headers.patch, CAMEL-7067.patch The CamelJcrInsert operation in JcrProducer stores all exchange properties in the target JCR node including all Camel properties that are found in the incoming exchange. This means that non-relevant data is persisted in JCR nodes including sensitive information such as username and password that is part of the URI in the CamelToEndpoint exchange property. Other examples of such properties include CamelJcrNodeName and CamelExternalRedelivered. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CAMEL-7103) camel-quartz - Store trigger information in job map
[ https://issues.apache.org/jira/browse/CAMEL-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7103. Resolution: Fixed camel-quartz - Store trigger information in job map --- Key: CAMEL-7103 URL: https://issues.apache.org/jira/browse/CAMEL-7103 Project: Camel Issue Type: Improvement Components: camel-quartz, camel-quartz2 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.12.3, 2.13.0 At runtime quartz scheduler does not have any information about the triggers which is easily available to know if its a simple or cron trigger, and how they are configured. Having those details in the job map allows end users to access this information in the Camel routes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CAMEL-7104) Add support for all permissions for authorization in camel-shiro
[ https://issues.apache.org/jira/browse/CAMEL-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-7104: --- Attachment: camel-7104.patch A patch for this issue. Colm. Add support for all permissions for authorization in camel-shiro -- Key: CAMEL-7104 URL: https://issues.apache.org/jira/browse/CAMEL-7104 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Priority: Minor Fix For: 2.13.0 Attachments: camel-7104.patch Currently, the ShiroSecurityPolicy takes a List of Shiro Permission objects for authorization. Authorization succeeds if any of the permissions match that of the current user. However, it's not possible to support requiring all of the permissions, expect via the permission wildcard syntax, which may not be convenient for every circumstance. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CAMEL-7104) Add support for all permissions for authorization in camel-shiro
Colm O hEigeartaigh created CAMEL-7104: -- Summary: Add support for all permissions for authorization in camel-shiro Key: CAMEL-7104 URL: https://issues.apache.org/jira/browse/CAMEL-7104 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Priority: Minor Fix For: 2.13.0 Attachments: camel-7104.patch Currently, the ShiroSecurityPolicy takes a List of Shiro Permission objects for authorization. Authorization succeeds if any of the permissions match that of the current user. However, it's not possible to support requiring all of the permissions, expect via the permission wildcard syntax, which may not be convenient for every circumstance. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CAMEL-7105) Add ability to send html emails and auto reconnect for sqs queues
adrian jagnanan created CAMEL-7105: -- Summary: Add ability to send html emails and auto reconnect for sqs queues Key: CAMEL-7105 URL: https://issues.apache.org/jira/browse/CAMEL-7105 Project: Camel Issue Type: New Feature Components: camel-aws Affects Versions: 2.13.0 Reporter: adrian jagnanan Fix For: 2.13.0 Hello, I am putting a ticket in for 2 features we found missing in the aws component. I have these in a pull request already, located here https://github.com/apache/camel/pull/60. Thanks. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
