Re: Camel, m2Eclipse, Eclipse Ganymede
Hi, I use Eclipse 3.4 (Ganymede) with Sonatype Maven plugin. Personaly I do the build outside of Eclipse. I will check but I'm pretty sure that I can do the build inside Eclipse. BTW, the file to be used for the build is the pom.xml parent file which is not of a module regards, Charles Moulliard Senior Enterprise Architect Apache Camel Committer * blog : http://cmoulliard.blogspot.com On Wed, May 6, 2009 at 7:03 AM, huntc hu...@mac.com wrote: Hi there, Does anyone use Eclipse Ganymede and the m2eclipse tooling? I've been trying to build the 1.6 with these and I can get things to build outside of the IDE using Maven from the command line. However I am unable to build Came with Eclipse and m2eclipse. Recipes anyone? Kind regards, Christopher -- View this message in context: http://www.nabble.com/Camel%2C-m2Eclipse%2C-Eclipse-Ganymede-tp23400074p23400074.html Sent from the Camel Development mailing list archive at Nabble.com.
[jira] Commented: (CAMEL-1585) SFTP GenericFileProducer.createFileName produces OS normalized file name, that doesn't work with SFTP
[ https://issues.apache.org/activemq/browse/CAMEL-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51529#action_51529 ] Claus Ibsen commented on CAMEL-1585: Willem, great work. Yeah looking at the patch it was just the producer side not using the getFileSeparator. SFTP GenericFileProducer.createFileName produces OS normalized file name, that doesn't work with SFTP - Key: CAMEL-1585 URL: https://issues.apache.org/activemq/browse/CAMEL-1585 Project: Apache Camel Issue Type: Bug Components: camel-ftp Affects Versions: 2.0-M1 Environment: Windows XP Reporter: Darryl Smith Assignee: Willem Jiang Fix For: 2.0-M2 The use of File.separator and FileUtil.normalizePath in GenericFileProducer.createFileName produce a OS normalized file name, that doesn't work with SFTP e.g. outbound\\out_20090501_091940_ACC.txt which will not work produce a file called outboundout_20090501_091940_ACC.txt The proper name should be outbound/out_20090501_091940_ACC.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Camel 2.0 Async Findings - Roadmap to a solution
Hi I have committed first cut of the new Async API to Camel trunk. See ticket CAMEL-1572 for svn revision and details. The remaining work: - Migrate MulticastProcessor - Remove last piece of old API classes (2 interfaces) - Introduce Async DSL to replace Thread DSL and with clear intention of turning route into async mode and support thread pools using JDK executor service. - Support Jetty continuation with async Should we mark the old API in Camel 1.x as @deprecated? On Tue, May 5, 2009 at 4:48 PM, Claus Ibsen claus.ib...@gmail.com wrote: Hi Just wanted to keep you posted. Had some more work done to replace the old async API with the new API in camel-core. I basically got it all done except the MuticastProcessor as it would take a bit more time to get done correctly. I am thinking it should leverage the JDK CompletionService or the like for keeping track on completed tasks. But for now I wanted to get the other parts working, and it looks good. The Thread DSL is to be replaced with a new Async DSL, so that is why I am deleting it from the code base. And I am going to merge the async producer template into the regular producer template so we have a single combined template for all producer sync and async. Its about 10 more methods. On Tue, May 5, 2009 at 11:05 AM, Claus Ibsen claus.ib...@gmail.com wrote: Hi I had some more time to work on this. I have attached a 2nd patch on the JIRA ticket 1572. This time the patch is only focusing on the AsyncProducerTemplate. I have added more methods to cover the most common methods use in producer template. With this an end user can initiate and async routing in Camel. If the user wants to use the regular Camel API (lookup endpoint, create exchange, create producer, process etc.) there is a helper method on AsyncProcessorHelper to initiate an async route as well. Any thoughts? On Fri, May 1, 2009 at 11:53 AM, Claus Ibsen claus.ib...@gmail.com wrote: I have committed a patch to trunk: that resolves #1 (partly), #2 and #4 In #1 there are still two classes that needs a cleanup as well. However they are core pieces in Camel, the Pipeline and MulticastProcessor so they are left as is. When we have a new Async API in place these classes can be fixed as well. I have also attached a prototype for a patch for the new async API experiment I have done. See CAMEL-1572. -- 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 -- 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 Interview with me: http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress -- 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 Interview with me: http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress -- 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 Interview with me: http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
[jira] Commented: (CAMEL-1572) Internal API - Cleanup in the AsyncCallback
[ https://issues.apache.org/activemq/browse/CAMEL-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51531#action_51531 ] Claus Ibsen commented on CAMEL-1572: See the nabble link as I keep posting there also with updates. Internal API - Cleanup in the AsyncCallback --- Key: CAMEL-1572 URL: https://issues.apache.org/activemq/browse/CAMEL-1572 Project: Apache Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.0-M1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0 Attachments: CAMEL-1572.patch, CAMEL-1572b.patch, new_async_api.patch, new_async_api2.patch See nabble http://www.nabble.com/Camel-2.0-Async-Findings---Roadmap-to-a-solution-td23310165.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Fwd: [Question] About Camel Spring and registration of new endpoint (camel-quickfix)
Hi, I will first check the code in order to be able to run it in Camel with quickfix/j (it seems that there is a classloading issue inside quickfix/j, ...) and deploy it in OSGI server. After, I will check why there is an issue with the XML file, Regards Charles Moulliard Senior Enterprise Architect Apache Camel Committer * blog : http://cmoulliard.blogspot.com On Wed, May 6, 2009 at 6:51 AM, Willem Jiang willem.ji...@gmail.com wrote: Yes, declare the component in the spring configuration file just a walk around solution. I can dig the code of quickfix resource loading later today. Willem Claus Ibsen wrote: On Tue, May 5, 2009 at 5:15 PM, Charles Moulliard cmoulli...@gmail.com wrote: With the following config, it works : bean id=quickfix-server class=org.apache.camel.quickfix.QuickfixAcceptor/ bean id=quickfix-client class=org.apache.camel.quickfix.QuickfixInitiator/ camel:camelContext trace=true xmlns= http://camel.apache.org/schema/osgi; camel:route camel:from uri=quickfix-server:META-INF/examples/server.cfg/ camel:to uri=quickfix-client:META-INF/examples/client.cfg/ /camel:route /camel:camelContext Any idea why we have to declare the beans ? No but its your job to dig into the code base :) I assume the code that reads the resources from the URI has a flaw. I can help with this later. The important part is to make sure the camel-quickfix component works, has the features we want and is properly tested etc. Then later we can fix the minor issues with resource loading. It should support loading in classpath, file, and OSGi :) Charles Moulliard Senior Enterprise Architect Apache Camel Committer * blog : http://cmoulliard.blogspot.com On Tue, May 5, 2009 at 5:12 PM, Charles Moulliard cmoulli...@gmail.com wrote: I have modified the spring xml file like you propose : camel:camelContext trace=true xmlns= http://camel.apache.org/schema/osgi; camel:route camel:from uri=quickfix-server:examples/server.cfg/ camel:to uri=quickfix-client:examples/client.cfg/ /camel:route /camel:camelContext and now we have the error : s...@root:osgi Exception in thread SpringOsgiExtenderThread-63 org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: quickfix-server:examples/ser ver.cfg due to: java.io.FileNotFoundException: class path resource [examples/server.cfg] cannot be opened because it does not exist at org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:378) at org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:52) at org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:133) at org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:103) at org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:109) at org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72) at org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:78) at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:302) at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:121) at org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:481) at org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:777) at org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:759) at org.apache.camel.spring.SpringCamelContext.maybeDoStart(SpringCamelContext.java:165) at org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:160) at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:50) at org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:95) at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:114) 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
Jetty unit https test messages
Hi there, I've made some local changes to the jetty unit tests so they are able to support a key/trust store path that has spaces in it (such as on my machine). The change is pretty simple - instead of passing the result of a URL's getPath to the system property we convert to a URI and then use getPath. Anyhow I noticed the following output from HttpsRouteTest and wondered if it was normal: Running org.apache.camel.component.jetty.HttpsRouteTest 2009-05-06 18:10:17.264::INFO: jetty-6.1.14 2009-05-06 18:10:17.530::INFO: Started sslsocketconnec...@localhost:9080 2009-05-06 18:10:17.869::INFO: jetty-6.1.14 2009-05-06 18:10:17.871::INFO: Started sslsocketconnec...@localhost:9080 2009-05-06 18:10:18.06::WARN: EXCEPTION javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:523) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041) at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:631) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522) 2009-05-06 18:10:18.132::INFO: jetty-6.1.14 2009-05-06 18:10:18.134::INFO: Started sslsocketconnec...@localhost:9080 2009-05-06 18:10:18.523::INFO: jetty-6.1.14 2009-05-06 18:10:18.525::INFO: Started sslsocketconnec...@localhost:9080 2009-05-06 18:10:18.544::WARN: EXCEPTION javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:523) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041) at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:631) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522) Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.415 sec Kind regards, Christopher -- View this message in context: http://www.nabble.com/Jetty-unit-https-test-messages-tp23402063p23402063.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: Camel, m2Eclipse, Eclipse Ganymede
Hi Claude, Thanks for your replies. I'm thinking that you shouldn't have to do this with m2eclipse though - in a perfect world that is. You should be able to check out the project from svn, enable m2eclipse on the project, and the rest should sort itself out. It mostly does though there's something I'm not doing... I'll study your advice further though. Kind regards, Christopher -- View this message in context: http://www.nabble.com/Camel%2C-m2Eclipse%2C-Eclipse-Ganymede-tp23400074p23402716.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: Jetty unit https test messages
Hi I think these exceptions has always been in the unit test of camel-jetty. On Wed, May 6, 2009 at 10:17 AM, huntc hu...@mac.com wrote: Hi there, I've made some local changes to the jetty unit tests so they are able to support a key/trust store path that has spaces in it (such as on my machine). The change is pretty simple - instead of passing the result of a URL's getPath to the system property we convert to a URI and then use getPath. Anyhow I noticed the following output from HttpsRouteTest and wondered if it was normal: Running org.apache.camel.component.jetty.HttpsRouteTest 2009-05-06 18:10:17.264::INFO: jetty-6.1.14 2009-05-06 18:10:17.530::INFO: Started sslsocketconnec...@localhost:9080 2009-05-06 18:10:17.869::INFO: jetty-6.1.14 2009-05-06 18:10:17.871::INFO: Started sslsocketconnec...@localhost:9080 2009-05-06 18:10:18.06::WARN: EXCEPTION javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:523) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041) at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:631) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522) 2009-05-06 18:10:18.132::INFO: jetty-6.1.14 2009-05-06 18:10:18.134::INFO: Started sslsocketconnec...@localhost:9080 2009-05-06 18:10:18.523::INFO: jetty-6.1.14 2009-05-06 18:10:18.525::INFO: Started sslsocketconnec...@localhost:9080 2009-05-06 18:10:18.544::WARN: EXCEPTION javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:523) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1057) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1041) at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:631) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522) Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.415 sec Kind regards, Christopher -- View this message in context: http://www.nabble.com/Jetty-unit-https-test-messages-tp23402063p23402063.html Sent from the Camel Development mailing list archive at Nabble.com. -- 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 Interview with me: http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
[jira] Created: (CAMEL-1587) Processors supporting thread pool should have option aligned to be a executorService / executorServiceRef
Processors supporting thread pool should have option aligned to be a executorService / executorServiceRef - Key: CAMEL-1587 URL: https://issues.apache.org/activemq/browse/CAMEL-1587 Project: Apache Camel Issue Type: Improvement Components: camel-spring Affects Versions: 2.0-M1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0 Having a consistent configuration to configure thread pools / management in Camel is a goal of Camel 2.x. There is a ticket to allow easier setup of this to be used in managed environments such as WebSphere with its ThreadWorker API (cant remember the exact name) This applied among others for: - mutlicast - splitter and others -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1587) Processors supporting thread pool should have option aligned to be a executorService / executorServiceRef
[ https://issues.apache.org/activemq/browse/CAMEL-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-1587: --- Description: Having a consistent configuration to configure thread pools / management in Camel is a goal of Camel 2.x. There is a ticket to allow easier setup of this to be used in managed environments such as WebSphere with its ThreadWorker API (cant remember the exact name) This applied among others for: - mutlicast *DONE* - splitter *DONE* and others (need to look) was: Having a consistent configuration to configure thread pools / management in Camel is a goal of Camel 2.x. There is a ticket to allow easier setup of this to be used in managed environments such as WebSphere with its ThreadWorker API (cant remember the exact name) This applied among others for: - mutlicast - splitter and others part of commit patch for CAMEL-1572 also: 772172. Processors supporting thread pool should have option aligned to be a executorService / executorServiceRef - Key: CAMEL-1587 URL: https://issues.apache.org/activemq/browse/CAMEL-1587 Project: Apache Camel Issue Type: Improvement Components: camel-spring Affects Versions: 2.0-M1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0 Having a consistent configuration to configure thread pools / management in Camel is a goal of Camel 2.x. There is a ticket to allow easier setup of this to be used in managed environments such as WebSphere with its ThreadWorker API (cant remember the exact name) This applied among others for: - mutlicast *DONE* - splitter *DONE* and others (need to look) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Camel 2.0 Async Findings - Roadmap to a solution
Hi Status update On Wed, May 6, 2009 at 9:17 AM, Claus Ibsen claus.ib...@gmail.com wrote: Hi I have committed first cut of the new Async API to Camel trunk. See ticket CAMEL-1572 for svn revision and details. The remaining work: - Migrate MulticastProcessor DONE - Remove last piece of old API classes (2 interfaces) DONE - Introduce Async DSL to replace Thread DSL and with clear intention of turning route into async mode and support thread pools using JDK executor service. - Support Jetty continuation with async
[jira] Assigned: (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 ] Willem Jiang reassigned CAMEL-1350: --- Assignee: Willem Jiang 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 Assignee: Willem Jiang 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 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:383) at
Re: Camel 2.0 Async Findings - Roadmap to a solution
On Wed, May 6, 2009 at 3:41 PM, Gert Vanthienen gert.vanthie...@gmail.com wrote: Hi Claus, Nice work on cleaning up the async API for Camel! Using well-known java.util.concurrency classes to build the API is a good idea, makes it a lot more comprehensible for people. Just a few questions that come to mind... - How does this work relate to introducing the Channel API? Will we have a means for using async channels in the route transparently or are the two unrelated? Per see the two are unrelated as such. But in the future we can much more easily introduce async channels. If you want for instance each processing step to be done async step by step :) But currently the Channel we have is not so flexible but the ground work has been done for the future work. - What happens with the original thread after the async()? I'm guessing it will wait for the async work to be done before continuing, right? Note the async DSL I did in the patch was an experiment but will bring it back in to replace the old Thread DSL. Well the original thread gets the FutureExchange handle as a result. So it basically returns this back to the original caller. Then the original caller can do other work, and then retrieve the async thread result when he/she likes with the future handle get method. - Do all the threads come from a single thread pool? Do we have a means to configure that pool? I guess my main question is, how likely are we to deadlock the entire Route by having all the threads either waiting on some Future or waiting to get another thread from the pool? Good question. I am also aligning the configuration of thread pools in Camel 2.0. So its based on ExecutorService and have the same API / Spring attribute. This allows end users to define thread pools as they like more easily and configure it. And at the same time we should provide some default pools and pool sizes. Some uses 5 and others 10 in the current code base. But basically each processor creates its own thread pool if none configured, and they default to a size of either 5 or 10. When I get a bit more work done lets re asset and find a good solution for thread pool management in Camel 2.0 For instance some users with J2EE servers would like to define that Camel should use threads provided from this server. Just wondering if we could somehow put an Erlang-style message-passing concurrency mechanism underneath our Route afterwards -- in a transparent way so people wouldn't have to worry about this. I guess we have enough work just to keep the Scala DSL up to date. But yeah concurrency and parallel work is challeging the way we program today in Java. Bug be careful James might read this and ask you to do some prototyping :) Regards, Gert Vanthienen Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/5/6 Claus Ibsen claus.ib...@gmail.com: Hi Status update On Wed, May 6, 2009 at 9:17 AM, Claus Ibsen claus.ib...@gmail.com wrote: Hi I have committed first cut of the new Async API to Camel trunk. See ticket CAMEL-1572 for svn revision and details. The remaining work: - Migrate MulticastProcessor DONE - Remove last piece of old API classes (2 interfaces) DONE - Introduce Async DSL to replace Thread DSL and with clear intention of turning route into async mode and support thread pools using JDK executor service. - Support Jetty continuation with async -- 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 Interview with me: http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
[jira] Commented: (CAMEL-1350) camel-quickfix component in apache camel distribution
[ https://issues.apache.org/activemq/browse/CAMEL-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51539#action_51539 ] Charles Moulliard commented on CAMEL-1350: -- @Willem, I have already done some modifications in the code provided by Anton. Do you want it ? 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 Assignee: Willem Jiang 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] Commented: (CAMEL-1350) camel-quickfix component in apache camel distribution
[ https://issues.apache.org/activemq/browse/CAMEL-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51540#action_51540 ] Willem Jiang commented on CAMEL-1350: - @Anton, I just went through the patch , I didn't find any unit tests. Did you miss them when you zip the files ? 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 Assignee: Willem Jiang 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] Commented: (CAMEL-1350) camel-quickfix component in apache camel distribution
[ https://issues.apache.org/activemq/browse/CAMEL-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51541#action_51541 ] Charles Moulliard commented on CAMEL-1350: -- @Willem, there is no unit test except an example class packaged under src/main/java/org.apache.camel.quickfix.example 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 Assignee: Willem Jiang 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] Resolved: (CAMEL-1587) Processors supporting thread pool should have option aligned to be a executorService / executorServiceRef
[ https://issues.apache.org/activemq/browse/CAMEL-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1587. Resolution: Fixed Have done the rest, wireTap had also one. trunk: 772297. Processors supporting thread pool should have option aligned to be a executorService / executorServiceRef - Key: CAMEL-1587 URL: https://issues.apache.org/activemq/browse/CAMEL-1587 Project: Apache Camel Issue Type: Improvement Components: camel-spring Affects Versions: 2.0-M1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0 Having a consistent configuration to configure thread pools / management in Camel is a goal of Camel 2.x. There is a ticket to allow easier setup of this to be used in managed environments such as WebSphere with its ThreadWorker API (cant remember the exact name) This applied among others for: - mutlicast *DONE* - splitter *DONE* and others (need to look) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1588) ExecutorService configuration
ExecutorService configuration - Key: CAMEL-1588 URL: https://issues.apache.org/activemq/browse/CAMEL-1588 Project: Apache Camel Issue Type: New Feature Components: camel-core Affects Versions: 2.0-M1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0 Camel uses some thread pools, for component, endpoint and processor. We should have some default configuration that is easy to configure with Camel to adjust pool sizes for individual/groups/type etc. By not they use 5 as the default pool size. And have their own executor unless configured otherwise. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1350) camel-quickfix component in apache camel distribution
[ https://issues.apache.org/activemq/browse/CAMEL-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51543#action_51543 ] Willem Jiang commented on CAMEL-1350: - @ Charles, Can you show me your change ? I'm trying to load the camel-quickfix bundle in my osgi-integration test. 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 Assignee: Willem Jiang 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-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 ] Charles Moulliard updated CAMEL-1350: - Attachment: camel-quickfix.zip Here is a zip file containing : A) camel-quickfix modified : 1) pom.xml, 2) packages renamed from org.apache.camel.quickfix to org.apache.camel.component.quickfix 3) Thread.currentThread().setContextClassLoader added in quickFixAcceptor and Initiator B) reportincident.quickfix Small camel bundle using quickfix Remark : You have to deploy the following bundle too : install -s wrap:mvn:org.quickfixj/quickfixj-all/1.4.0 the jar is available from repo of iona : http://repo.fusesource.com/maven2-all 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 Assignee: Willem Jiang Fix For: 2.1.0 Attachments: camel-quickfix.zip, 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
[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 ] Charles Moulliard updated CAMEL-1350: - Attachment: (was: camel-quickfix.zip) 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 Assignee: Willem Jiang Fix For: 2.1.0 Attachments: camel-quickfix.zip, camel-quickfix.zip, reportincident.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 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:383) at
[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 ] Charles Moulliard updated CAMEL-1350: - Attachment: reportincident.quickfix.zip camel-quickfix.zip 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 Assignee: Willem Jiang Fix For: 2.1.0 Attachments: camel-quickfix.zip, camel-quickfix.zip, reportincident.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
Re: Fwd: [Question] About Camel Spring and registration of new endpoint (camel-quickfix)
Hi Charles After changed the pom.xml to make camel-quickfix component as bundle, I managed to load it in Pax-Exam. BTW, you need to wrap the quickfix and mina-core jars. wrappedBundle(mavenBundle().groupId(org.quickfixj).artifactId(quickfixj-all).version(1.4.0)), wrappedBundle(mavenBundle().groupId(org.apache.mina).artifactId(mina-core).version(1.1.7)), Willem Charles Moulliard wrote: Hi, I will first check the code in order to be able to run it in Camel with quickfix/j (it seems that there is a classloading issue inside quickfix/j, ...) and deploy it in OSGI server. After, I will check why there is an issue with the XML file, Regards Charles Moulliard Senior Enterprise Architect Apache Camel Committer * blog : http://cmoulliard.blogspot.com On Wed, May 6, 2009 at 6:51 AM, Willem Jiang willem.ji...@gmail.com wrote: Yes, declare the component in the spring configuration file just a walk around solution. I can dig the code of quickfix resource loading later today. Willem Claus Ibsen wrote: On Tue, May 5, 2009 at 5:15 PM, Charles Moulliard cmoulli...@gmail.com wrote: With the following config, it works : bean id=quickfix-server class=org.apache.camel.quickfix.QuickfixAcceptor/ bean id=quickfix-client class=org.apache.camel.quickfix.QuickfixInitiator/ camel:camelContext trace=true xmlns= http://camel.apache.org/schema/osgi; camel:route camel:from uri=quickfix-server:META-INF/examples/server.cfg/ camel:to uri=quickfix-client:META-INF/examples/client.cfg/ /camel:route /camel:camelContext Any idea why we have to declare the beans ? No but its your job to dig into the code base :) I assume the code that reads the resources from the URI has a flaw. I can help with this later. The important part is to make sure the camel-quickfix component works, has the features we want and is properly tested etc. Then later we can fix the minor issues with resource loading. It should support loading in classpath, file, and OSGi :) Charles Moulliard Senior Enterprise Architect Apache Camel Committer * blog : http://cmoulliard.blogspot.com On Tue, May 5, 2009 at 5:12 PM, Charles Moulliard cmoulli...@gmail.com wrote: I have modified the spring xml file like you propose : camel:camelContext trace=true xmlns= http://camel.apache.org/schema/osgi; camel:route camel:from uri=quickfix-server:examples/server.cfg/ camel:to uri=quickfix-client:examples/client.cfg/ /camel:route /camel:camelContext and now we have the error : s...@root:osgi Exception in thread SpringOsgiExtenderThread-63 org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: quickfix-server:examples/ser ver.cfg due to: java.io.FileNotFoundException: class path resource [examples/server.cfg] cannot be opened because it does not exist at org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:378) at org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:52) at org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:133) at org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:103) at org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:109) at org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72) at org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:78) at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:302) at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:121) at org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:481) at org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:777) at org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:759) at org.apache.camel.spring.SpringCamelContext.maybeDoStart(SpringCamelContext.java:165) at org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:160) at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:50) at org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:95) at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:114) 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
Re: svn commit: r772054 - in /camel/trunk/components/camel-cxf/src: main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java test/java/org/apache/camel/component/cxf/CxfRawMessageRouter
Hi Willem,
I don't think adding content-type to the filters is necessary.
1. The header is Content-Type not content-type, so the change
does not really affect anything.
2. Putting that aside. If we add filters for Content-Type, it stops
the propagating from Camel header to/from CXF header, which we don't
want.
We probably should clean up the use of
CamelTransportContants.CONTENT_TYPE (value = content.type) and just
use Message.CONTENT_TYPE (value = Content-Type).
In DefaultCxfBinding.java, I don't see why we need to invent a header
constant (CamelTransportContants.CONTENT_TYPE) only used by camel-cxf
and have to map it back and forth.
That is, we can eliminate CamelTransportContants.CONTENT_TYPE and use
Message.CONTENT_TYPE consistently in:
// propagate content type
String key = Message.CONTENT_TYPE;
Object value = cxfMessage.get(key);
if (value != null
!headerFilterStrategy.applyFilterToExternalHeaders(key, value,
exchange)) {
camelHeaders.put(CamelTransportConstants.CONTENT_TYPE, value);
if (LOG.isTraceEnabled()) {
LOG.trace(Populate header from CXF header= + key +
value= + value);
}
}
...
// put content type in exchange
if (CamelTransportConstants.CONTENT_TYPE.equals(entry.getKey())) {
cxfExchange.put(Message.CONTENT_TYPE, entry.getValue());
continue;
}
Thoughts?
==
---
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
(original)
+++
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
Wed May 6 04:56:14 2009
@@ -63,6 +63,11 @@
getOutFilter().add(Message.PROTOCOL_HEADERS);
getInFilter().add(Message.PROTOCOL_HEADERS);
+ // Since the DefaultCxfBinding deal with the content-type separately.
+ // We need to filter this header
+ getOutFilter().add(content-type);
+ getInFilter().add(content-type);
+
// initialize message header filter map with default SOAP filter
messageHeaderFiltersMap = new HashMapString, MessageHeaderFilter();
addToMessageHeaderFilterMap(new SoapMessageHeaderFilter());
Re: svn commit: r772054 - in /camel/trunk/components/camel-cxf/src: main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java test/java/org/apache/camel/component/cxf/CxfRawMessageRouter
Hi William,
Since the JMS can't accept the header which's name has the '-'
character, we introduce the CamelTransportContants.CONTENT_TYPE for it.
After checking the on wire message between the client and CXF consumer,
I found there are two lines of content-type in the http header.
One is content-type, the other is Content-Type.
So I added the filter of content-type, and keep using content.type
in the Camel message.
Willem
William Tam wrote:
Hi Willem,
I don't think adding content-type to the filters is necessary.
1. The header is Content-Type not content-type, so the change
does not really affect anything.
2. Putting that aside. If we add filters for Content-Type, it stops
the propagating from Camel header to/from CXF header, which we don't
want.
We probably should clean up the use of
CamelTransportContants.CONTENT_TYPE (value = content.type) and just
use Message.CONTENT_TYPE (value = Content-Type).
In DefaultCxfBinding.java, I don't see why we need to invent a header
constant (CamelTransportContants.CONTENT_TYPE) only used by camel-cxf
and have to map it back and forth.
That is, we can eliminate CamelTransportContants.CONTENT_TYPE and use
Message.CONTENT_TYPE consistently in:
// propagate content type
String key = Message.CONTENT_TYPE;
Object value = cxfMessage.get(key);
if (value != null
!headerFilterStrategy.applyFilterToExternalHeaders(key, value,
exchange)) {
camelHeaders.put(CamelTransportConstants.CONTENT_TYPE, value);
if (LOG.isTraceEnabled()) {
LOG.trace(Populate header from CXF header= + key +
value= + value);
}
}
...
// put content type in exchange
if (CamelTransportConstants.CONTENT_TYPE.equals(entry.getKey())) {
cxfExchange.put(Message.CONTENT_TYPE, entry.getValue());
continue;
}
Thoughts?
==
---
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
(original)
+++
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
Wed May 6 04:56:14 2009
@@ -63,6 +63,11 @@
getOutFilter().add(Message.PROTOCOL_HEADERS);
getInFilter().add(Message.PROTOCOL_HEADERS);
+// Since the DefaultCxfBinding deal with the content-type
separately.
+// We need to filter this header
+getOutFilter().add(content-type);
+getInFilter().add(content-type);
+
// initialize message header filter map with default SOAP filter
messageHeaderFiltersMap = new HashMapString, MessageHeaderFilter();
addToMessageHeaderFilterMap(new SoapMessageHeaderFilter());
Re: svn commit: r772054 - in /camel/trunk/components/camel-cxf/src: main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java test/java/org/apache/camel/component/cxf/CxfRawMessageRouter
On Thu, May 7, 2009 at 5:02 AM, William Tam email.w...@gmail.com wrote:
On Wed, May 6, 2009 at 9:57 PM, Willem Jiang willem.ji...@gmail.com wrote:
Hi William,
Since the JMS can't accept the header which's name has the '-'
character, we introduce the CamelTransportContants.CONTENT_TYPE for it.
I thought JMS could not handle dots in header names (that's why we
went from org.apache.camel convention to CamelHeaderName case
convention). My memory may be wrong.
Hi
In Camel 2.0 we have added to the JMS component so it will be able to
transfer Content-Type with the hyphen, as its a common header.
If you use Camel on both sides then it will automatic revert it back
to normal again. It replaces - with a _HYPHEN_ constant. So its
transfered as Content_HYPHEN_Type.
After checking the on wire message between the client and CXF consumer,
I found there are two lines of content-type in the http header.
One is content-type, the other is Content-Type.
The comment in code is kinda off.
So I added the filter of content-type, and keep using content.type
in the Camel message.
Willem
William Tam wrote:
Hi Willem,
I don't think adding content-type to the filters is necessary.
1. The header is Content-Type not content-type, so the change
does not really affect anything.
2. Putting that aside. If we add filters for Content-Type, it stops
the propagating from Camel header to/from CXF header, which we don't
want.
We probably should clean up the use of
CamelTransportContants.CONTENT_TYPE (value = content.type) and just
use Message.CONTENT_TYPE (value = Content-Type).
In DefaultCxfBinding.java, I don't see why we need to invent a header
constant (CamelTransportContants.CONTENT_TYPE) only used by camel-cxf
and have to map it back and forth.
That is, we can eliminate CamelTransportContants.CONTENT_TYPE and use
Message.CONTENT_TYPE consistently in:
// propagate content type
String key = Message.CONTENT_TYPE;
Object value = cxfMessage.get(key);
if (value != null
!headerFilterStrategy.applyFilterToExternalHeaders(key, value,
exchange)) {
camelHeaders.put(CamelTransportConstants.CONTENT_TYPE, value);
if (LOG.isTraceEnabled()) {
LOG.trace(Populate header from CXF header= + key +
value= + value);
}
}
...
// put content type in exchange
if
(CamelTransportConstants.CONTENT_TYPE.equals(entry.getKey())) {
cxfExchange.put(Message.CONTENT_TYPE, entry.getValue());
continue;
}
Thoughts?
==
---
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
(original)
+++
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
Wed May 6 04:56:14 2009
@@ -63,6 +63,11 @@
getOutFilter().add(Message.PROTOCOL_HEADERS);
getInFilter().add(Message.PROTOCOL_HEADERS);
+ // Since the DefaultCxfBinding deal with the content-type
separately.
+ // We need to filter this header
+ getOutFilter().add(content-type);
+ getInFilter().add(content-type);
+
// initialize message header filter map with default SOAP filter
messageHeaderFiltersMap = new HashMapString,
MessageHeaderFilter();
addToMessageHeaderFilterMap(new SoapMessageHeaderFilter());
--
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
Interview with me:
http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
[jira] Resolved: (CAMEL-656) Component documentation - needs overhaul, check for missing options, add more samples java/spring, etc
[ https://issues.apache.org/activemq/browse/CAMEL-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-656. --- Resolution: Fixed The most important components is documented. Component documentation - needs overhaul, check for missing options, add more samples java/spring, etc -- Key: CAMEL-656 URL: https://issues.apache.org/activemq/browse/CAMEL-656 Project: Apache Camel Issue Type: Improvement Components: documentation Affects Versions: 1.3.0, 1.4.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0 Our extensive list of components needs to be checked for its state of current documentation standard in the wiki. The should be checked for - options - headers they use/set - pitfalls - samples both java and spring XML - see also - etc And whats the difference / relation to similar component (the http ones, the sql ones etc.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-797) camel-example-reportincident tutorial - ideas for new parts to add
[ https://issues.apache.org/activemq/browse/CAMEL-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-797. --- Resolution: Fixed The tutorial is finished. No time to write more on it. camel-example-reportincident tutorial - ideas for new parts to add -- Key: CAMEL-797 URL: https://issues.apache.org/activemq/browse/CAMEL-797 Project: Apache Camel Issue Type: Improvement Components: documentation, examples Affects Versions: 1.4.0 Reporter: Charles Moulliard Assignee: Claus Ibsen Fix For: 2.0.0 Attachments: part-four.zip Hi, First of all, I would like to thanks Claus for the quality of its tutorial. This is a great job for the camel community to have now a second tutorial showing the magic of Camel. What I would like to propose is to add a fourth part to this tutorial to show : - How to turn on the code to DSL language and/or spring xml configuration file ? - How the architecture can be adapted to use Camel as the entry point of the web service instead of the CxFServlet ? Task to do 1) Adapt the architecture to allow Camel to become the entry point of the web services 2) Transpose the code to routes the messages between the endpoints using DSL language through a java class 3) Idem bu using a spring configuration file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1310) DelegateProcessor should support async message handling
[ https://issues.apache.org/activemq/browse/CAMEL-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1310. Resolution: Won't Fix Fix Version/s: 2.0.0 The AsyncProcessor Is replaced by the new Async API. So this ticket is not needed. DelegateProcessor should support async message handling --- Key: CAMEL-1310 URL: https://issues.apache.org/activemq/browse/CAMEL-1310 Project: Apache Camel Issue Type: Improvement Components: camel-core Affects Versions: 1.5.0, 1.6.0 Reporter: Gert Vanthienen Assignee: Claus Ibsen Fix For: 2.0.0 We should improve the default DelegateProcessor to support async Message handling as well. Right now, adding a Tracer, Delayer, StreamCaching, ... to a Route breaks the ability to use asynchronous processing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r772054 - in /camel/trunk/components/camel-cxf/src: main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java test/java/org/apache/camel/component/cxf/CxfRawMessageRouter
On Wed, May 6, 2009 at 11:55 PM, Claus Ibsen claus.ib...@gmail.com wrote:
On Thu, May 7, 2009 at 5:02 AM, William Tam email.w...@gmail.com wrote:
On Wed, May 6, 2009 at 9:57 PM, Willem Jiang willem.ji...@gmail.com wrote:
Hi William,
Since the JMS can't accept the header which's name has the '-'
character, we introduce the CamelTransportContants.CONTENT_TYPE for it.
I thought JMS could not handle dots in header names (that's why we
went from org.apache.camel convention to CamelHeaderName case
convention). My memory may be wrong.
Hi
In Camel 2.0 we have added to the JMS component so it will be able to
transfer Content-Type with the hyphen, as its a common header.
If you use Camel on both sides then it will automatic revert it back
to normal again. It replaces - with a _HYPHEN_ constant. So its
transfered as Content_HYPHEN_Type.
In 2.0, does that mean it is OK to have hyphen in header? If so, we
could clean up CamelTransportContants.CONTENT_TYPE?
After checking the on wire message between the client and CXF consumer,
I found there are two lines of content-type in the http header.
One is content-type, the other is Content-Type.
The comment in code is kinda off.
So I added the filter of content-type, and keep using content.type
in the Camel message.
Willem
William Tam wrote:
Hi Willem,
I don't think adding content-type to the filters is necessary.
1. The header is Content-Type not content-type, so the change
does not really affect anything.
2. Putting that aside. If we add filters for Content-Type, it stops
the propagating from Camel header to/from CXF header, which we don't
want.
We probably should clean up the use of
CamelTransportContants.CONTENT_TYPE (value = content.type) and just
use Message.CONTENT_TYPE (value = Content-Type).
In DefaultCxfBinding.java, I don't see why we need to invent a header
constant (CamelTransportContants.CONTENT_TYPE) only used by camel-cxf
and have to map it back and forth.
That is, we can eliminate CamelTransportContants.CONTENT_TYPE and use
Message.CONTENT_TYPE consistently in:
// propagate content type
String key = Message.CONTENT_TYPE;
Object value = cxfMessage.get(key);
if (value != null
!headerFilterStrategy.applyFilterToExternalHeaders(key, value,
exchange)) {
camelHeaders.put(CamelTransportConstants.CONTENT_TYPE, value);
if (LOG.isTraceEnabled()) {
LOG.trace(Populate header from CXF header= + key +
value= + value);
}
}
...
// put content type in exchange
if
(CamelTransportConstants.CONTENT_TYPE.equals(entry.getKey())) {
cxfExchange.put(Message.CONTENT_TYPE, entry.getValue());
continue;
}
Thoughts?
==
---
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
(original)
+++
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
Wed May 6 04:56:14 2009
@@ -63,6 +63,11 @@
getOutFilter().add(Message.PROTOCOL_HEADERS);
getInFilter().add(Message.PROTOCOL_HEADERS);
+ // Since the DefaultCxfBinding deal with the content-type
separately.
+ // We need to filter this header
+ getOutFilter().add(content-type);
+ getInFilter().add(content-type);
+
// initialize message header filter map with default SOAP filter
messageHeaderFiltersMap = new HashMapString,
MessageHeaderFilter();
addToMessageHeaderFilterMap(new SoapMessageHeaderFilter());
--
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
Interview with me:
http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
Re: svn commit: r772054 - in /camel/trunk/components/camel-cxf/src: main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java test/java/org/apache/camel/component/cxf/CxfRawMessageRouter
On Thu, May 7, 2009 at 6:29 AM, William Tam email.w...@gmail.com wrote:
On Wed, May 6, 2009 at 11:55 PM, Claus Ibsen claus.ib...@gmail.com wrote:
On Thu, May 7, 2009 at 5:02 AM, William Tam email.w...@gmail.com wrote:
On Wed, May 6, 2009 at 9:57 PM, Willem Jiang willem.ji...@gmail.com wrote:
Hi William,
Since the JMS can't accept the header which's name has the '-'
character, we introduce the CamelTransportContants.CONTENT_TYPE for it.
I thought JMS could not handle dots in header names (that's why we
went from org.apache.camel convention to CamelHeaderName case
convention). My memory may be wrong.
Hi
In Camel 2.0 we have added to the JMS component so it will be able to
transfer Content-Type with the hyphen, as its a common header.
If you use Camel on both sides then it will automatic revert it back
to normal again. It replaces - with a _HYPHEN_ constant. So its
transfered as Content_HYPHEN_Type.
In 2.0, does that mean it is OK to have hyphen in header? If so, we
could clean up CamelTransportContants.CONTENT_TYPE?
Yes the default JmsKeyFormatStrategy in Camel 2.0 is for the JMS component:
public class DefaultJmsKeyFormatStrategy implements JmsKeyFormatStrategy {
public String encodeKey(String key) {
String answer = key.replace(., _);
answer = answer.replaceAll(-, _HYPHEN_);
return answer;
}
public String decodeKey(String key) {
String answer = key.replaceAll(_HYPHEN_, -);
answer = answer.replace(_, .);
return answer;
}
}
After checking the on wire message between the client and CXF consumer,
I found there are two lines of content-type in the http header.
One is content-type, the other is Content-Type.
The comment in code is kinda off.
So I added the filter of content-type, and keep using content.type
in the Camel message.
Willem
William Tam wrote:
Hi Willem,
I don't think adding content-type to the filters is necessary.
1. The header is Content-Type not content-type, so the change
does not really affect anything.
2. Putting that aside. If we add filters for Content-Type, it stops
the propagating from Camel header to/from CXF header, which we don't
want.
We probably should clean up the use of
CamelTransportContants.CONTENT_TYPE (value = content.type) and just
use Message.CONTENT_TYPE (value = Content-Type).
In DefaultCxfBinding.java, I don't see why we need to invent a header
constant (CamelTransportContants.CONTENT_TYPE) only used by camel-cxf
and have to map it back and forth.
That is, we can eliminate CamelTransportContants.CONTENT_TYPE and use
Message.CONTENT_TYPE consistently in:
// propagate content type
String key = Message.CONTENT_TYPE;
Object value = cxfMessage.get(key);
if (value != null
!headerFilterStrategy.applyFilterToExternalHeaders(key, value,
exchange)) {
camelHeaders.put(CamelTransportConstants.CONTENT_TYPE, value);
if (LOG.isTraceEnabled()) {
LOG.trace(Populate header from CXF header= + key +
value= + value);
}
}
...
// put content type in exchange
if
(CamelTransportConstants.CONTENT_TYPE.equals(entry.getKey())) {
cxfExchange.put(Message.CONTENT_TYPE, entry.getValue());
continue;
}
Thoughts?
==
---
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
(original)
+++
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
Wed May 6 04:56:14 2009
@@ -63,6 +63,11 @@
getOutFilter().add(Message.PROTOCOL_HEADERS);
getInFilter().add(Message.PROTOCOL_HEADERS);
+ // Since the DefaultCxfBinding deal with the content-type
separately.
+ // We need to filter this header
+ getOutFilter().add(content-type);
+ getInFilter().add(content-type);
+
// initialize message header filter map with default SOAP filter
messageHeaderFiltersMap = new HashMapString,
MessageHeaderFilter();
addToMessageHeaderFilterMap(new SoapMessageHeaderFilter());
--
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
Interview with me:
http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
--
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
Interview with me:
Re: svn commit: r772054 - in /camel/trunk/components/camel-cxf/src: main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java test/java/org/apache/camel/component/cxf/CxfRawMessageRouter
Hi,
It's much clearer after the discussion, I will head to clean up the
CamelTransportContants.CONTENT_TYPE later today.
Thanks,
Willem
Claus Ibsen wrote:
On Thu, May 7, 2009 at 6:29 AM, William Tam email.w...@gmail.com wrote:
On Wed, May 6, 2009 at 11:55 PM, Claus Ibsen claus.ib...@gmail.com wrote:
On Thu, May 7, 2009 at 5:02 AM, William Tam email.w...@gmail.com wrote:
On Wed, May 6, 2009 at 9:57 PM, Willem Jiang willem.ji...@gmail.com
wrote:
Hi William,
Since the JMS can't accept the header which's name has the '-'
character, we introduce the CamelTransportContants.CONTENT_TYPE for it.
I thought JMS could not handle dots in header names (that's why we
went from org.apache.camel convention to CamelHeaderName case
convention). My memory may be wrong.
Hi
In Camel 2.0 we have added to the JMS component so it will be able to
transfer Content-Type with the hyphen, as its a common header.
If you use Camel on both sides then it will automatic revert it back
to normal again. It replaces - with a _HYPHEN_ constant. So its
transfered as Content_HYPHEN_Type.
In 2.0, does that mean it is OK to have hyphen in header? If so, we
could clean up CamelTransportContants.CONTENT_TYPE?
Yes the default JmsKeyFormatStrategy in Camel 2.0 is for the JMS component:
public class DefaultJmsKeyFormatStrategy implements JmsKeyFormatStrategy {
public String encodeKey(String key) {
String answer = key.replace(., _);
answer = answer.replaceAll(-, _HYPHEN_);
return answer;
}
public String decodeKey(String key) {
String answer = key.replaceAll(_HYPHEN_, -);
answer = answer.replace(_, .);
return answer;
}
}
After checking the on wire message between the client and CXF consumer,
I found there are two lines of content-type in the http header.
One is content-type, the other is Content-Type.
The comment in code is kinda off.
So I added the filter of content-type, and keep using content.type
in the Camel message.
Willem
William Tam wrote:
Hi Willem,
I don't think adding content-type to the filters is necessary.
1. The header is Content-Type not content-type, so the change
does not really affect anything.
2. Putting that aside. If we add filters for Content-Type, it stops
the propagating from Camel header to/from CXF header, which we don't
want.
We probably should clean up the use of
CamelTransportContants.CONTENT_TYPE (value = content.type) and just
use Message.CONTENT_TYPE (value = Content-Type).
In DefaultCxfBinding.java, I don't see why we need to invent a header
constant (CamelTransportContants.CONTENT_TYPE) only used by camel-cxf
and have to map it back and forth.
That is, we can eliminate CamelTransportContants.CONTENT_TYPE and use
Message.CONTENT_TYPE consistently in:
// propagate content type
String key = Message.CONTENT_TYPE;
Object value = cxfMessage.get(key);
if (value != null
!headerFilterStrategy.applyFilterToExternalHeaders(key, value,
exchange)) {
camelHeaders.put(CamelTransportConstants.CONTENT_TYPE,
value);
if (LOG.isTraceEnabled()) {
LOG.trace(Populate header from CXF header= + key +
value= + value);
}
}
...
// put content type in exchange
if
(CamelTransportConstants.CONTENT_TYPE.equals(entry.getKey())) {
cxfExchange.put(Message.CONTENT_TYPE, entry.getValue());
continue;
}
Thoughts?
==
---
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
(original)
+++
camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
Wed May 6 04:56:14 2009
@@ -63,6 +63,11 @@
getOutFilter().add(Message.PROTOCOL_HEADERS);
getInFilter().add(Message.PROTOCOL_HEADERS);
+// Since the DefaultCxfBinding deal with the content-type
separately.
+// We need to filter this header
+getOutFilter().add(content-type);
+getInFilter().add(content-type);
+
// initialize message header filter map with default SOAP filter
messageHeaderFiltersMap = new HashMapString,
MessageHeaderFilter();
addToMessageHeaderFilterMap(new SoapMessageHeaderFilter());
--
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
Interview with me:
http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
[jira] Commented: (CAMEL-1350) camel-quickfix component in apache camel distribution
[ https://issues.apache.org/activemq/browse/CAMEL-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51550#action_51550 ] Willem Jiang commented on CAMEL-1350: - Applied the patch with thanks to Anton and Charles http://svn.apache.org/viewvc?rev=772503view=rev The patch also includes these changes 1) pom.xml, created the osig friendly bundle 2) packages renamed from org.apache.camel.quickfix to org.apache.camel.component.quickfix also updated the META-INF/services/org/apache/camel/component files and example/fix-gateway.xml for the change 3) Thread.currentThread().setContextClassLoader added in quickFixAcceptor and Initiator 4) Fix the CS errors 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 Assignee: Willem Jiang Fix For: 2.1.0 Attachments: camel-quickfix.zip, camel-quickfix.zip, reportincident.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
[jira] Commented: (CAMEL-1350) camel-quickfix component in apache camel distribution
[
https://issues.apache.org/activemq/browse/CAMEL-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=51551#action_51551
]
Claus Ibsen commented on CAMEL-1350:
Willem a few comments to the commit
1) dependency on log4j should be optional, eg remove log4j in the code and
*only* uses commons-logging
2) please add code comments why you mess with the context classloader
3) QuickFixEndpoint please do proper error handling and not do
e.printStackTrace. There should be some getExceptionHandler on the super you
can delegate to.
4) Remove the shutdown hook, it should be stopped in doStop() in the endpoint.
Eg use doStart and doStop for init/dispose tasks.
5) Dont catch, log and rethrow in QuickFixEndpoint, but set the exception on
exchange, then Camel error handler can handle it afterwards, eg
try {
process
} catch (Exception e)
exchange.setException(e);
}
6) createException looks odd, as it sets the same object in IN/OUT, and why
force an InOut pattern? Is it mandatory for FIX to always do InOut?
7) In createConsumer do not set the this.processor = processor. The processor
is for the consumer only.
8) It depends on camel-spring for resource loading, so we can load resource
files in the classpath. See camel-velocity that also does this, and do like it,
eg extend some camel-spring XXX endpoint class for doing it properly.
9) Maybe add some DEBUG logging in doStart / doStop so you can see it starts /
stops
10) throw IllegalArgumentException if not configured properly instead of
RuntimeException
11) Why does Exchange2Message extends MessageCracker is that needed? And it
should be renamed to QuickFixConverter.
12) Do not hardcode iso-8859-1 as encoding, but use the existing type
converters in camel-core. And add Exchange as the 2nd parameter to get hold of
the other type converters to convert the InputStream to String.
13) And move the sample code into src/test/java
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
Assignee: Willem Jiang
Fix For: 2.1.0
Attachments: camel-quickfix.zip, camel-quickfix.zip,
reportincident.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
[jira] Updated: (CAMEL-1570) Jetty component is unable to be configured for security
[
https://issues.apache.org/activemq/browse/CAMEL-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Hunt updated CAMEL-1570:
Attachment: (was: JettyHttpEndpoint.java.diff)
Jetty component is unable to be configured for security
---
Key: CAMEL-1570
URL: https://issues.apache.org/activemq/browse/CAMEL-1570
Project: Apache Camel
Issue Type: Improvement
Components: camel-jetty
Affects Versions: 1.6.0, 2.0-M1
Environment: NA
Reporter: Christopher Hunt
The Jetty component is presently unable to be configured for security. A
general purpose mechanism so that the Jetty component can be configured would
be useful. The following URI based option is proposed:
||Name||Default Value||Description||
|handlers|null| Specifies a comma delimited set of instances in your Registry
(such as your Spring ApplicationContext). These instances are added to the
Jetty servlet context|
Here is an example URI:
{code}
jetty:http://0.0.0.0:9080/MyService?handlers=securityHandler
{code}
This could refer to something like the following Spring configuration:
{code}
!-- Jetty Security handling --
bean id=userRealm class=org.mortbay.jetty.plus.jaas.JAASUserRealm
property name=name value=tracker-users /
property name=loginModuleName value=ldaploginmodule /
/bean
bean id=constraint class=org.mortbay.jetty.security.Constraint
property name=name value=BASIC /
property name=roles value=tracker-users /
property name=authenticate value=true /
/bean
bean id=constraintMapping
class=org.mortbay.jetty.security.ConstraintMapping
property name=constraint ref=constraint /
property name=pathSpec value=/* /
/bean
bean id=securityHandler
class=org.mortbay.jetty.security.SecurityHandler
property name=userRealm ref=userRealm /
property name=constraintMappings ref=constraintMapping /
/bean
{code}
I have attached proposed changes to the 1.6 branch. I imagine that 2.0 should
be quite similar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1570) Jetty component is unable to be configured for security
[
https://issues.apache.org/activemq/browse/CAMEL-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Hunt updated CAMEL-1570:
Attachment: (was: JettyHttpComponent.java.diff)
Jetty component is unable to be configured for security
---
Key: CAMEL-1570
URL: https://issues.apache.org/activemq/browse/CAMEL-1570
Project: Apache Camel
Issue Type: Improvement
Components: camel-jetty
Affects Versions: 1.6.0, 2.0-M1
Environment: NA
Reporter: Christopher Hunt
The Jetty component is presently unable to be configured for security. A
general purpose mechanism so that the Jetty component can be configured would
be useful. The following URI based option is proposed:
||Name||Default Value||Description||
|handlers|null| Specifies a comma delimited set of instances in your Registry
(such as your Spring ApplicationContext). These instances are added to the
Jetty servlet context|
Here is an example URI:
{code}
jetty:http://0.0.0.0:9080/MyService?handlers=securityHandler
{code}
This could refer to something like the following Spring configuration:
{code}
!-- Jetty Security handling --
bean id=userRealm class=org.mortbay.jetty.plus.jaas.JAASUserRealm
property name=name value=tracker-users /
property name=loginModuleName value=ldaploginmodule /
/bean
bean id=constraint class=org.mortbay.jetty.security.Constraint
property name=name value=BASIC /
property name=roles value=tracker-users /
property name=authenticate value=true /
/bean
bean id=constraintMapping
class=org.mortbay.jetty.security.ConstraintMapping
property name=constraint ref=constraint /
property name=pathSpec value=/* /
/bean
bean id=securityHandler
class=org.mortbay.jetty.security.SecurityHandler
property name=userRealm ref=userRealm /
property name=constraintMappings ref=constraintMapping /
/bean
{code}
I have attached proposed changes to the 1.6 branch. I imagine that 2.0 should
be quite similar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
