[jira] Commented: (CAMEL-1548) ErrorHandler to be wrapped at every node incl children
[ https://issues.apache.org/activemq/browse/CAMEL-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51314#action_51314 ] Claus Ibsen commented on CAMEL-1548: It should work now. trunk: 767064 ErrorHandler to be wrapped at every node incl children -- Key: CAMEL-1548 URL: https://issues.apache.org/activemq/browse/CAMEL-1548 Project: Apache Camel Issue Type: Bug Components: camel-core Affects Versions: 2.0-M1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1548) ErrorHandler to be wrapped at every node incl children
[ https://issues.apache.org/activemq/browse/CAMEL-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1548. Resolution: Fixed ErrorHandler to be wrapped at every node incl children -- Key: CAMEL-1548 URL: https://issues.apache.org/activemq/browse/CAMEL-1548 Project: Apache Camel Issue Type: Bug Components: camel-core Affects Versions: 2.0-M1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1552) Provide declarative transaction handling for the JPA component
Provide declarative transaction handling for the JPA component -- Key: CAMEL-1552 URL: https://issues.apache.org/activemq/browse/CAMEL-1552 Project: Apache Camel Issue Type: Improvement Components: camel-jpa Affects Versions: 2.0-M1 Reporter: Frank Schwarz The JPA component uses currently a hard coded reference to org.springframework.orm.jpa.JpaTransactionManager. A more flexible (i.e. declarative) handling would be desirable. See also: http://www.nabble.com/Re%3A-JPA-component-in-a-JEE5-environment-p23154746s22882.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1536) add an integration test for Camel in OSGi containers like Felix and Equinox
[ https://issues.apache.org/activemq/browse/CAMEL-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51321#action_51321 ] Gert Vanthienen commented on CAMEL-1536: These tests were failing on Hudson/TeamCity because they override the Maven local repository location using -Dmaven.repo.local=/some/dir. Unfortunately, Pax Exam doesn't support this yet (cfr. [PAXEXAM-62|http://issues.ops4j.org/browse/PAXEXAM-62] and [PAXEXAM-64|http://issues.ops4j.org/browse/PAXEXAM-64]), so using a workaround using the Pax Exam Maven plugin to generate a config file to point to the right local Maven repo in http://svn.apache.org/viewvc?view=revrevision=767141 add an integration test for Camel in OSGi containers like Felix and Equinox --- Key: CAMEL-1536 URL: https://issues.apache.org/activemq/browse/CAMEL-1536 Project: Apache Camel Issue Type: Improvement Reporter: James Strachan Assignee: James Strachan Fix For: 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1555) JMX Instrumentation - rework code to avoid changing the route model, so the model is the same when JMX is disabled
JMX Instrumentation - rework code to avoid changing the route model, so the model is the same when JMX is disabled -- Key: CAMEL-1555 URL: https://issues.apache.org/activemq/browse/CAMEL-1555 Project: Apache Camel Issue Type: Task Components: camel-core Affects Versions: 2.0-M1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0 It bites us if we have different model depending whether JMX is enabled or not. JMX should only instrument some processors with performance counters and register endpoints, consumer, producers and the likes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[DISCUSS] Release Camel 2.0-M2 and 1.6.1
Hi, I think quite a bit of progress has been made in the trunk and more patches applied on the 1.x branch. There is still some more work to be done on 2.0, but I think what we have is a great candidate for a M2 release. The time is also right for a Camel 1.6.1 maintenance release. Thoughts? Hadrian
Re: [DISCUSS] Release Camel 2.0-M2 and 1.6.1
+1 to both On Tue, Apr 21, 2009 at 6:55 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: Hi, I think quite a bit of progress has been made in the trunk and more patches applied on the 1.x branch. There is still some more work to be done on 2.0, but I think what we have is a great candidate for a M2 release. The time is also right for a Camel 1.6.1 maintenance release. Thoughts? Hadrian -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus Apache Camel Reference Card: http://refcardz.dzone.com/refcardz/enterprise-integration
Re: [DISCUSS] Release Camel 2.0-M2 and 1.6.1
+1 2009/4/21 Hadrian Zbarcea hzbar...@gmail.com: Hi, I think quite a bit of progress has been made in the trunk and more patches applied on the 1.x branch. There is still some more work to be done on 2.0, but I think what we have is a great candidate for a M2 release. The time is also right for a Camel 1.6.1 maintenance release. Thoughts? Hadrian -- James --- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
Re: [DISCUSS] Release Camel 2.0-M2 and 1.6.1
+1 On Tue, Apr 21, 2009 at 2:35 PM, James Strachan james.strac...@gmail.comwrote: +1 2009/4/21 Hadrian Zbarcea hzbar...@gmail.com: Hi, I think quite a bit of progress has been made in the trunk and more patches applied on the 1.x branch. There is still some more work to be done on 2.0, but I think what we have is a great candidate for a M2 release. The time is also right for a Camel 1.6.1 maintenance release. Thoughts? Hadrian -- James --- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/ -- Cheers, Jon http://janstey.blogspot.com/
[jira] Created: (CAMEL-1556) Controlling initiatation order of routes
Controlling initiatation order of routes Key: CAMEL-1556 URL: https://issues.apache.org/activemq/browse/CAMEL-1556 Project: Apache Camel Issue Type: Wish Components: camel-core Reporter: Henric Hedin Priority: Minor Would be nice if it was possible to control the order of how routes are initiated. If the following code is implemented within the same RouteBuilder.configure: // initiated from queue from(jms:queue:SOURCE_QUEUE). to(direct:processMsg); // initiated from file from(file://inbox). to(direct:processMsg); // Main flow from(direct:processMsg) .process(...) .to(validator:foo.xsd) .to(jms:queue:DEST_QUEUE); ... and there already is a message waiting on the JMS-source when camel is started, it could/will lead to the following error: WARN DirectProducer - No consumers available on endpoint: Endpoint[direct:processMsg] to process Exchange[JmsMessage: Today the are workarounds (by splitting in multiple files, and re-order route definitions), but maybe this could solved in some other better way (which also could affect a graceful shutdown). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1350) camel-quickfix component in apache camel distribution
[ https://issues.apache.org/activemq/browse/CAMEL-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Arhipov updated CAMEL-1350: - Attachment: camel-quickfix.zip Attached a version of the component that doesn't have the dependency on ArtixDS, including the fixes suggested by Bengt camel-quickfix component in apache camel distribution - Key: CAMEL-1350 URL: https://issues.apache.org/activemq/browse/CAMEL-1350 Project: Apache Camel Issue Type: Bug Environment: properties camel-version2.0-SNAPSHOT/camel-version fuse-version2.x-fuse-SNAPSHOT/fuse-version activemq-version5.2.0/activemq-version quickfix-version1.3.3/quickfix-version mina-version1.1.0/mina-version slf4j-version1.5.6/slf4j-version /properties Reporter: Charles Moulliard Fix For: 2.1.0 Attachments: camel-quickfix.zip Hi, ATTENTION: Ignoring converter type: org.apache.camel.fix.FixConverter as a dependent class could not be found: java.lang.NoClassDefFoundError: biz/c24/io/api/data/DataType java.lang.NoClassDefFoundError: biz/c24/io/api/data/DataType at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.getDeclaredMethods(Class.java:1791) at org.apache.camel.impl.converter.AnnotationTypeConverterLoader.loadConverterMethods(AnnotationTypeConverterLoader.java:147) at org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:78) at org.apache.camel.impl.converter.DefaultTypeConverter.checkLoaded(DefaultTypeConverter.java:260) at org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(DefaultTypeConverter.java:95) at org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(DefaultTypeConverter.java:71) at org.apache.camel.util.IntrospectionSupport.convert(IntrospectionSupport.java:263) at org.apache.camel.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:221) at org.apache.camel.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:188) at org.apache.camel.impl.DefaultComponent.setProperties(DefaultComponent.java:213) at org.apache.camel.component.file.GenericFileComponent.createEndpoint(GenericFileComponent.java:63) at org.apache.camel.component.file.GenericFileComponent.createEndpoint(GenericFileComponent.java:33) at org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:81) at org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:330) at org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:54) at org.apache.camel.model.RouteType.resolveEndpoint(RouteType.java:96) at org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:106) at org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:112) at org.apache.camel.model.FromType.resolveEndpoint(FromType.java:72) at org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:81) at org.apache.camel.model.RouteType.addRoutes(RouteType.java:239) at org.apache.camel.model.RouteType.addRoutes(RouteType.java:86) at org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:661) at org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:651) at org.apache.camel.spring.SpringCamelContext.maybeDoStart(SpringCamelContext.java:166) at org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:161) at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:49) at org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:96) at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:115) at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78) at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76) at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736) at
[jira] Updated: (CAMEL-1556) Controlling initiatation order of routes
[ https://issues.apache.org/activemq/browse/CAMEL-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henric Hedin updated CAMEL-1556: Issue Type: New Feature (was: Wish) Controlling initiatation order of routes Key: CAMEL-1556 URL: https://issues.apache.org/activemq/browse/CAMEL-1556 Project: Apache Camel Issue Type: New Feature Components: camel-core Reporter: Henric Hedin Priority: Minor Would be nice if it was possible to control the order of how routes are initiated. If the following code is implemented within the same RouteBuilder.configure: // initiated from queue from(jms:queue:SOURCE_QUEUE). to(direct:processMsg); // initiated from file from(file://inbox). to(direct:processMsg); // Main flow from(direct:processMsg) .process(...) .to(validator:foo.xsd) .to(jms:queue:DEST_QUEUE); ... and there already is a message waiting on the JMS-source when camel is started, it could/will lead to the following error: WARN DirectProducer - No consumers available on endpoint: Endpoint[direct:processMsg] to process Exchange[JmsMessage: Today the are workarounds (by splitting in multiple files, and re-order route definitions), but maybe this could solved in some other better way (which also could affect a graceful shutdown). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] Release Camel 2.0-M2 and 1.6.1
+1 On Tue, Apr 21, 2009 at 1:13 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: just realized that these would be the first releases using nexus. On Apr 21, 2009, at 1:08 PM, Jon Anstey wrote: +1 On Tue, Apr 21, 2009 at 2:35 PM, James Strachan james.strac...@gmail.comwrote: +1 2009/4/21 Hadrian Zbarcea hzbar...@gmail.com: Hi, I think quite a bit of progress has been made in the trunk and more patches applied on the 1.x branch. There is still some more work to be done on 2.0, but I think what we have is a great candidate for a M2 release. The time is also right for a Camel 1.6.1 maintenance release. Thoughts? Hadrian -- James --- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/ -- Cheers, Jon http://janstey.blogspot.com/
Re: [DISCUSS] Release Camel 2.0-M2 and 1.6.1
+1 2009/4/21 Hadrian Zbarcea hzbar...@gmail.com: Hi, I think quite a bit of progress has been made in the trunk and more patches applied on the 1.x branch. There is still some more work to be done on 2.0, but I think what we have is a great candidate for a M2 release. The time is also right for a Camel 1.6.1 maintenance release. Thoughts? Hadrian
Re: [DISCUSS] Release Camel 2.0-M2 and 1.6.1
+1. Willem On Wed, Apr 22, 2009 at 12:55 AM, Hadrian Zbarcea hzbar...@gmail.comwrote: Hi, I think quite a bit of progress has been made in the trunk and more patches applied on the 1.x branch. There is still some more work to be done on 2.0, but I think what we have is a great candidate for a M2 release. The time is also right for a Camel 1.6.1 maintenance release. Thoughts? Hadrian
Re: [DISCUSS] Release Camel 2.0-M2 and 1.6.1
+1 Freeman Willem Jiang wrote: +1. Willem On Wed, Apr 22, 2009 at 12:55 AM, Hadrian Zbarcea hzbar...@gmail.comwrote: Hi, I think quite a bit of progress has been made in the trunk and more patches applied on the 1.x branch. There is still some more work to be done on 2.0, but I think what we have is a great candidate for a M2 release. The time is also right for a Camel 1.6.1 maintenance release. Thoughts? Hadrian -- Freeman Fang Open Source SOA: http://fusesource.com
