[jira] [Commented] (CAMEL-6794) XSLT Aggregation Strategies?
[ https://issues.apache.org/jira/browse/CAMEL-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979460#comment-13979460 ] Oliver Jelinski commented on CAMEL-6794: That looks great! Thanx. I will have a closer look at your provided code and test it, during the next week. XSLT Aggregation Strategies? Key: CAMEL-6794 URL: https://issues.apache.org/jira/browse/CAMEL-6794 Project: Camel Issue Type: New Feature Components: camel-core Affects Versions: 2.12.1 Reporter: Oliver Jelinski Hi Camel team, my wish for a new feature already came up a long time ago, in CAMEL-2820, but this was closed, because the requester didn't give enough information on this. So I try it again, with a bit more info... I am processing xml via camel a lot and I'm working a lot with the xslt component for transformations. This works fine and I think it is solved by you in a very elegant way. But very often I also need to split my xml for processing of the maxOccurs=unbounded-Elements one-by-one. This also works fine, but when it comes to aggregating the elements again, I need to write a java-AggregationStrategy for that. Basically, what the java AggregationStrategy does, would be also achievable with XSLT: having an old exchange (that is null for the first aggregation) and a new exchange that are however aggregated to a new object that has the same type as the body of the old exchange. In XSLT you can transform two (or more) files into one new file, So it would be totally possible to process one xml-file of namespace x with root element x:a and another xml-file with namespace y with root element y:b to a target file which also has the root-element x:a. This could be repeated n times and would result in an element x:a. -- basically the same behaviour as the java AggregationStrategies. So my wish would be to have something like split strategyRef=xslt:MyTransformation.xslt ... /split If I had that, I would save a lot of marshal/unmarshal operations. I would be glad, if you took this into consideration. Best regards, Oliver -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7269) camel-jpa - joinTransaction called for RESOURCE_LOCAL datasource
[ https://issues.apache.org/jira/browse/CAMEL-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-7269: --- Fix Version/s: (was: 2.12.4) (was: 2.14.0) (was: 2.13.1) (was: 2.13.0) (was: 3.0.0) Future camel-jpa - joinTransaction called for RESOURCE_LOCAL datasource Key: CAMEL-7269 URL: https://issues.apache.org/jira/browse/CAMEL-7269 Project: Camel Issue Type: Bug Components: camel-jpa Affects Versions: 2.12.0 Environment: tomcat+eclipselink+camel 2.12.2 Reporter: Hristo Sabev Assignee: Claus Ibsen Fix For: Future At line 82, JpaConsumer calls entityManager.joinTransaction(). This call cannot really work in environmnent without JTA. This is a change since 2.11.x and earlier versions where non JTA environments were supported -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7391) camel-netty - NettyProduce should use timer from component instead of creating new timer per producer
Claus Ibsen created CAMEL-7391: -- Summary: camel-netty - NettyProduce should use timer from component instead of creating new timer per producer Key: CAMEL-7391 URL: https://issues.apache.org/jira/browse/CAMEL-7391 Project: Camel Issue Type: Bug Components: camel-netty Affects Versions: 2.12.3 Reporter: Claus Ibsen Fix For: 2.12.4, 2.13.1, 2.14.0 We should use the shared timer, instead of creating a new timer per producer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7391) camel-netty - NettyProduce should use timer from component instead of creating new timer per producer
[ https://issues.apache.org/jira/browse/CAMEL-7391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7391. Resolution: Fixed Assignee: Claus Ibsen camel-netty - NettyProduce should use timer from component instead of creating new timer per producer - Key: CAMEL-7391 URL: https://issues.apache.org/jira/browse/CAMEL-7391 Project: Camel Issue Type: Bug Components: camel-netty Affects Versions: 2.12.3 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.12.4, 2.13.1, 2.14.0 We should use the shared timer, instead of creating a new timer per producer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7392) Unable to resolve bundle revision org.apache.camel.camel-servlet
Martin Lichtin created CAMEL-7392: - Summary: Unable to resolve bundle revision org.apache.camel.camel-servlet Key: CAMEL-7392 URL: https://issues.apache.org/jira/browse/CAMEL-7392 Project: Camel Issue Type: Bug Affects Versions: 2.13.0 Environment: Karaf 2.3.4 Reporter: Martin Lichtin When loading features featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature featurecamel-http/feature featurecamel-http4/feature featurecamel-servlet/feature the following issue occurs: Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [243.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] Chain 2: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [239.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7391) camel-netty - NettyProduce should use timer from component instead of creating new timer per producer
[ https://issues.apache.org/jira/browse/CAMEL-7391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979764#comment-13979764 ] Claus Ibsen commented on CAMEL-7391: So we had to use a private timer per producer as using a shared is not possible. camel-netty - NettyProduce should use timer from component instead of creating new timer per producer - Key: CAMEL-7391 URL: https://issues.apache.org/jira/browse/CAMEL-7391 Project: Camel Issue Type: Bug Components: camel-netty Affects Versions: 2.12.3 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.12.4, 2.13.1, 2.14.0 We should use the shared timer, instead of creating a new timer per producer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7392) Unable to resolve bundle revision org.apache.camel.camel-servlet
[ https://issues.apache.org/jira/browse/CAMEL-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Lichtin updated CAMEL-7392: -- Description: When loading features repositorymvn:org.apache.activemq/activemq-karaf/5.7.0/xml/features/repository repositorymvn:org.apache.camel.karaf/apache-camel/2.13.0/xml/features/repository repositorymvn:io.hawt/hawtio-karaf/1.2.3/xml/features/repository featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature featurecamel-http/feature featurecamel-http4/feature featurecamel-servlet/feature the following issue occurs: Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [243.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] Chain 2: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [239.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] was: When loading features featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature featurecamel-http/feature featurecamel-http4/feature featurecamel-servlet/feature the following issue occurs: Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [243.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] Chain 2: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [239.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] Unable to resolve bundle revision org.apache.camel.camel-servlet - Key: CAMEL-7392 URL: https://issues.apache.org/jira/browse/CAMEL-7392 Project: Camel Issue Type: Bug Affects Versions: 2.13.0 Environment: Karaf 2.3.4 Reporter: Martin Lichtin When loading features repositorymvn:org.apache.activemq/activemq-karaf/5.7.0/xml/features/repository repositorymvn:org.apache.camel.karaf/apache-camel/2.13.0/xml/features/repository repositorymvn:io.hawt/hawtio-karaf/1.2.3/xml/features/repository featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature
[jira] [Commented] (CAMEL-7392) Unable to resolve bundle revision org.apache.camel.camel-servlet
[ https://issues.apache.org/jira/browse/CAMEL-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979780#comment-13979780 ] Claus Ibsen commented on CAMEL-7392: ActiveMQ 5.7 does not support Camel 2.13.0 Unable to resolve bundle revision org.apache.camel.camel-servlet - Key: CAMEL-7392 URL: https://issues.apache.org/jira/browse/CAMEL-7392 Project: Camel Issue Type: Bug Affects Versions: 2.13.0 Environment: Karaf 2.3.4 Reporter: Martin Lichtin When loading features repositorymvn:org.apache.activemq/activemq-karaf/5.7.0/xml/features/repository repositorymvn:org.apache.camel.karaf/apache-camel/2.13.0/xml/features/repository repositorymvn:io.hawt/hawtio-karaf/1.2.3/xml/features/repository featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature featurecamel-http/feature featurecamel-http4/feature featurecamel-servlet/feature the following issue occurs: Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [243.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] Chain 2: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [239.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7393) Recipient List - Allow to define cache size, so you can tweak that or turn it off
Claus Ibsen created CAMEL-7393: -- Summary: Recipient List - Allow to define cache size, so you can tweak that or turn it off Key: CAMEL-7393 URL: https://issues.apache.org/jira/browse/CAMEL-7393 Project: Camel Issue Type: Improvement Components: camel-core, eip Affects Versions: 2.12.3 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.12.4, 2.13.1, 2.14.0 When using recipient list we use a default producer cache with a default size. We should allow end user to configure the size, so they can control that, or even turn it off, in case they use one-time only uris in the recipinent list (so they are not reuse later). Then it does not make sense to cache them anyway. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7383) camel-script-* features should depend on scripting-api bundle
[
https://issues.apache.org/jira/browse/CAMEL-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-7383.
-
Resolution: Fixed
Fix Version/s: 2.14.0
2.13.1
2.12.4
Applied the patch into camel master, camel-2.13.x and camel-2.12.x with thanks
to Grzegorz.
camel-script-* features should depend on scripting-api bundle
-
Key: CAMEL-7383
URL: https://issues.apache.org/jira/browse/CAMEL-7383
Project: Camel
Issue Type: Bug
Affects Versions: 2.13.0
Reporter: Grzegorz Grzybek
Assignee: Grzegorz Grzybek
Priority: Minor
Fix For: 2.12.4, 2.13.1, 2.14.0
{{camel-script-*}} features use package {{javax.script}} which may be not
exported by system bundle.
{{camel-script-*}} feature should depend on ServiceMix's scripting bundle
just like camel-groovy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7392) Unable to resolve bundle revision org.apache.camel.camel-servlet
[ https://issues.apache.org/jira/browse/CAMEL-7392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979820#comment-13979820 ] Martin Lichtin commented on CAMEL-7392: --- Thanks for the info. Actually we happily run with ActiveMQ 5.7 (client-side only) and Camel 2.13.0. What seems to be causing the problem here is hawtio. Camel and the camel-servlet feature come up fine when I do not load the hawtio-core feature. Unable to resolve bundle revision org.apache.camel.camel-servlet - Key: CAMEL-7392 URL: https://issues.apache.org/jira/browse/CAMEL-7392 Project: Camel Issue Type: Bug Affects Versions: 2.13.0 Environment: Karaf 2.3.4 Reporter: Martin Lichtin When loading features repositorymvn:org.apache.activemq/activemq-karaf/5.7.0/xml/features/repository repositorymvn:org.apache.camel.karaf/apache-camel/2.13.0/xml/features/repository repositorymvn:io.hawt/hawtio-karaf/1.2.3/xml/features/repository featureactivemq/feature featurecamel/feature featurecamel-jms/feature featurecamel-mvel/feature featurecamel-groovy/feature featurehawtio-core/feature featurecamel-cache/feature featurecxf/feature featurecamel-cxf/feature featurecamel-http/feature featurecamel-http4/feature featurecamel-servlet/feature the following issue occurs: Error executing command: Could not start bundle mvn:org.apache.camel/camel-servlet/2.13.0 in feature(s) camel-servlet-2.13.0: Uses constraint violation. Unable to resolve bundle revision org.apache.camel.camel-servlet [243.0] because it is exposed to package 'javax.servlet' from bundle revisions org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] and org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] via two dependency chains. Chain 1: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_2.5_spec [110.0] Chain 2: org.apache.camel.camel-servlet [243.0] import: ((osgi.wiring.package=org.apache.camel.component.http)(version=2.13.0)(!(version=2.14.0))) | export: osgi.wiring.package=org.apache.camel.component.http; uses:=javax.servlet org.apache.camel.camel-http [239.0] import: ((osgi.wiring.package=javax.servlet)(version=2.5.0)(!(version=4.0.0))) | export: osgi.wiring.package=javax.servlet org.apache.geronimo.specs.geronimo-servlet_3.0_spec [238.0] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7393) Recipient List - Allow to define cache size, so you can tweak that or turn it off
[ https://issues.apache.org/jira/browse/CAMEL-7393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7393. Resolution: Fixed There is now a new cacheSize option on recipinent list and routing slip you can use. Recipient List - Allow to define cache size, so you can tweak that or turn it off - Key: CAMEL-7393 URL: https://issues.apache.org/jira/browse/CAMEL-7393 Project: Camel Issue Type: Improvement Components: camel-core, eip Affects Versions: 2.12.3 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.12.4, 2.13.1, 2.14.0 When using recipient list we use a default producer cache with a default size. We should allow end user to configure the size, so they can control that, or even turn it off, in case they use one-time only uris in the recipinent list (so they are not reuse later). Then it does not make sense to cache them anyway. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7384) camel-rabbitmq: Allow connection factory tuning
[
https://issues.apache.org/jira/browse/CAMEL-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13980296#comment-13980296
]
ASF GitHub Bot commented on CAMEL-7384:
---
GitHub user gquintana opened a pull request:
https://github.com/apache/camel/pull/140
CAMEL-7384 Allow connection factory tuning
Add all available RabbitMQ ConnectionFactory settings
Upgrade to latest RabbitMQ AMQP Client 3.3.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gquintana/camel camel-7384-rabbitmq
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/140.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #140
commit fb6ab3de5b0248675ed5e95474d71c082e6fc3c6
Author: Gerald Quintana gerald.quint...@zenika.com
Date: 2014-04-24T20:38:24Z
Add all available ConnectionFactory settings
commit 99985218a362d7333b90c2cb3e431096a1887e6f
Author: Gerald Quintana gerald.quint...@zenika.com
Date: 2014-04-24T20:56:57Z
Upgrade RabbitMQ AMQP Client 3.3.0 and new connection factory settings
camel-rabbitmq: Allow connection factory tuning
---
Key: CAMEL-7384
URL: https://issues.apache.org/jira/browse/CAMEL-7384
Project: Camel
Issue Type: New Feature
Components: camel-rabbitmq
Affects Versions: 2.13.0
Reporter: Gérald Quintana
Assignee: Willem Jiang
Several settings of the {{com.rabbitmq.client.ConnectionFactory}} are not
exposed in RabbitMQEndpoint, namely:
- automaticRecoveryEnabled
- networkRecoveryInterval
- topologyRecoveryEnabled
- connectionTimeout
- requestedHeartbeat
- clientProperties
- requestedChannelMax
- requestedFrameMax
- sslProtocol
It would be great if we could plug any ConnectionFactory implementation in
the endpoint (caching connection factory for instance)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7377) mark openjpa as dependency in Camel JPA feature
[ https://issues.apache.org/jira/browse/CAMEL-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13980727#comment-13980727 ] Claus Ibsen commented on CAMEL-7377: Hmm openjpa should really not be there, as people should install their JPA implementation of choice. So if they want to use something else such as EclipseLink or Hibernate then OpenJPA should not be installed out of the box. mark openjpa as dependency in Camel JPA feature Key: CAMEL-7377 URL: https://issues.apache.org/jira/browse/CAMEL-7377 Project: Camel Issue Type: Bug Components: camel-jpa Affects Versions: 2.12.3, 2.13.0 Reporter: Ioan Eugen Stan I believe Camel-JPA feature should mark openjpa bundle as a dependency becasue it conflicts with open-jpa 2.3.0. Currently camel-jpa feature.xml defines: ``` bundlemvn:org.apache.openjpa/openjpa/2.2.2/bundle ``` and should be bundle dependency=truemvn:org.apache.openjpa/openjpa/2.2.2/bundle This problem apears when you have openjpa 2.3.0 installed and with to install camel-jpa 2.12.3 feature. Not marking the bundle as a dependency results in camel-jpa pulling the OpenJPA 2.2.2 bundle even if karaf has OpenJpa 2.3.0. Since both bundles try to register a PersistenceProvider in OSgi, the second one fails and the bundle fails to start - so camel-jpa feature is not installed. -- This message was sent by Atlassian JIRA (v6.2#6252)
