Re: Two different transactionmanagers on same route
Hi David,
You can configure the Camel JMS consumer component as a transactional
client (see camel 2.0 - jms /
http://camel.apache.org/transactional-client.html)
and Camel route with transacted option (Camel 2.0 - Database Sample
/ http://camel.apache.org/transactional-client.html). In this
scenario, 2 Tx managers will be used (JMS / JPA) but not at all
synchronized. This means that an error could occur after the exchange
completed by the camel route, record committed in the DB but JMS
rollbacked.
Regards,
Charles Moulliard
Apache Committer
Blog : http://cmoulliard.blogspot.com
Twitter : http://twitter.com/cmoulliard
Linkedin : http://www.linkedin.com/in/charlesmoulliard
Skype: cmoulliard
On Sun, Oct 30, 2011 at 7:59 PM, David Karlsen davidkarl...@gmail.com wrote:
Hi.
I have a route with two transactional resources, stripped down it is:
camel:route
camel:from uri={{incoming.filedir}} /
camel:from ref=myQueueEndpoint /
camel:transacted /
camel:to
uri=jpa:?persistenceUnit=myPersistenceUnitamp;usePersist=true /
/camel:route
How do I apply transactionality for the jpa endpoint in addition to the JMS
one?
I do not want to use XA (which would have only one common transactionmanager).
Do I have to split the route in two and pass on the message over a
direct channel and stick in a JPA transactionmanager in the second
one?
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
Re: pollEnrich consumer with selector
On Mon, Oct 31, 2011 at 4:58 AM, rspeter rspe...@yahoo.com wrote: Good day Claus, I did get this dynamic URI working by following the consumer template java bean example. Thank you very much for your prompt replies. Glad you got it working. I created a ticket so we can support this in the future. But targeted it for 3.0 as it would be an API breaker https://issues.apache.org/jira/browse/CAMEL-4596 Camel components are really powerful and you are a genius indeed. Regards Peter -- View this message in context: http://camel.465427.n5.nabble.com/pollEnrich-consumer-with-selector-tp4939908p4951412.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
Re: Basic from fp to file route: Need clarification. 1M Thanks.
Hi You can provide the name of the file to download as a parameter to the ftp uri. ftp://localhost/testfolder/?username=MYUSERNAMEpassword=MYPASSWORDlocalWorkDirectory=/tmpbinary=true?fileName=soap.xml; Then you do not need to use the choice. The Camel FTP consumer (eg when you do from(ftp:...) will keep checking the FTP server for new files to download. You can configure how often it checks by setting an option named: delay and its in milliseconds delay=5000 = 5 seconds But you can also use a more human readable format by specifying delay=5m = 5 minutes delay=10s = 10 seconds delay=1h = 1 hour And so forth. Also check this FAQ about running Camel standalone https://cwiki.apache.org/confluence/display/CAMEL/Running+Camel+standalone+and+have+it+keep+running On Sun, Oct 30, 2011 at 8:20 PM, H Paul passmea...@gmail.com wrote: The journey of 1000 miles begin with 1 step. This is my first small step with Camel. 1. Basically, I want to selectively download only 1 file soap.xml by ftp. Is below code is correct way of doing it? Please see code + log 2. From log, I saw a lot of repeative things. Is it because of 5 min? What is the correct value? 5 to 60 mins? int min=5; int second=60; context.start(); Thread.sleep(min*second*1000); context.stop(); 3. How can we stop the process once the file soap.xml is downloaded? there is no need to wait for 5 mins. -- View this message in context: http://camel.465427.n5.nabble.com/Basic-from-fp-to-file-route-Need-clarification-1M-Thanks-tp4950632p4950632.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
Contract first approach (using WSDL) to create a WS using cxf and route using camel
Hi, I want to create a WS using contract first approach. I have WSDL with me. I want a WS which when invokes send some data to an XML file using Camel. I want to deploy it in Tomcat Server. I am new to Camel. Please help out. Regards, Sachin Mehta -- View this message in context: http://camel.465427.n5.nabble.com/Contract-first-approach-using-WSDL-to-create-a-WS-using-cxf-and-route-using-camel-tp4951686p4951686.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Contract first approach (using WSDL) to create a WS using cxf and route using camel
Hi Check the CXF Tomcat example http://camel.apache.org/cxf-tomcat-example.html On Mon, Oct 31, 2011 at 8:26 AM, smehta34 sachin.me...@wipro.com wrote: Hi, I want to create a WS using contract first approach. I have WSDL with me. I want a WS which when invokes send some data to an XML file using Camel. I want to deploy it in Tomcat Server. I am new to Camel. Please help out. Regards, Sachin Mehta -- View this message in context: http://camel.465427.n5.nabble.com/Contract-first-approach-using-WSDL-to-create-a-WS-using-cxf-and-route-using-camel-tp4951686p4951686.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
Camel WS example
Hi Is there any simple camel example which can read from web service. I will be more comfortable if it was through camel-blueprint. If i am using blueprint, Then how i will be directing soap request. ? SAMPLE iDEA-- Can anyone suggest modifications to it cxf:cxfEndpoint id=cxfEndpoint address=http://0.0.0.0:8080/there; wsdlUrl=file://path/to/your/wsdl serviceClass=the_service_class_generated_by_cxf_codegen/ ... from uri=file endpoint: message.xml/ ( message.xml has soap request ? ) to uri=cxfEndpoint/ from uri=cxf Endpoint/ ( message.xml has soap request ? ) to uri=file response.xml/ ( response.xml which will receive soap response ) Regards Guru. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-WS-example-tp4951882p4951882.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Contract first approach (using WSDL) to create a WS using cxf and route using camel
Hi, Thanks for reply. I tried that example before and it was build successfully but when I put that zip file in the Webapp folder of Tomcat and deployed it and after giving address in the browser http://localhost:8080/camel-example-cxf-tomcat-2.5.0/webservices/incident?wsdl; it was showing this message The requested resource (/camel-example-cxf-tomcat-2.5.0/webservices/incident) is not available. When I tried CamelinAction book's example War of chapter 13 then it got successfully deployed. But same thing happened to War-servlet example, it was not successfully deployed in Tomcat. I am not able to resolve the problem. Please help me out. Regards, Sachin -- View this message in context: http://camel.465427.n5.nabble.com/Contract-first-approach-using-WSDL-to-create-a-WS-using-cxf-and-route-using-camel-tp4951686p4952013.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel WS example
If you want to put the response to file, you should define the route like this from uri=file endpoint: message.xml/ ( message.xml has soap request ? ) to uri=cxfEndpoint/ to uri=file response.xml/ On Mon Oct 31 17:01:18 2011, Gnanaguru S wrote: Hi Is there any simple camel example which can read from web service. I will be more comfortable if it was through camel-blueprint. If i am using blueprint, Then how i will be directing soap request. ? SAMPLE iDEA-- Can anyone suggest modifications to it cxf:cxfEndpoint id=cxfEndpoint address=http://0.0.0.0:8080/there; wsdlUrl=file://path/to/your/wsdl serviceClass=the_service_class_generated_by_cxf_codegen/ ... from uri=file endpoint: message.xml/ ( message.xml has soap request ? ) to uri=cxfEndpoint/ from uri=cxf Endpoint/ ( message.xml has soap request ? ) to uri=file response.xml/ ( response.xml which will receive soap response ) Regards Guru. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-WS-example-tp4951882p4951882.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Willem -- FuseSource Web: http://www.fusesource.com Blog:http://willemjiang.blogspot.com (English) http://jnn.javaeye.com (Chinese) Twitter: willemjiang Weibo: willemjiang
Camel ftp read next file after close connection
Hi. There is an error with ftp server. Many files on the server. All files have no time to be processed. When the processing of the next file, the process stops. Error - The request is a file after closing the connection. Camel version 2.8.1 Camel config route: Open FTP connection: Close FTP connection: After closed FTP connection: -- View this message in context: http://camel.465427.n5.nabble.com/Camel-ftp-read-next-file-after-close-connection-tp4952369p4952369.html Sent from the Camel - Users mailing list archive at Nabble.com.
Apache Camel 2.9.0-RC1
Hi, as a Apache Camel user I intend to upgrade to the 2.9.0 Release as soon as availabe @ the Maven-Repo, so that I wonder if is there any plan for a second try of the 2.9.0-RC1 in the near future: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-9-0-RC1-td4942935.html Regards, Babak -- View this message in context: http://camel.465427.n5.nabble.com/Apache-Camel-2-9-0-RC1-tp4952378p4952378.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Apache Camel 2.9.0-RC1
Yes, I am rebuilding it today. Thanks, Hadrian On 10/31/2011 09:08 AM, bvahdat wrote: Hi, as a Apache Camel user I intend to upgrade to the 2.9.0 Release as soon as availabe @ the Maven-Repo, so that I wonder if is there any plan for a second try of the 2.9.0-RC1 in the near future: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-9-0-RC1-td4942935.html Regards, Babak -- View this message in context: http://camel.465427.n5.nabble.com/Apache-Camel-2-9-0-RC1-tp4952378p4952378.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Validation supporting schemas with includes?
On Sunday, October 30, 2011 11:21:41 PM Christian Müller wrote: I wanted to add the missing unit test for handling multiple schema file, but it doesn't work. :-( I made a test where a root schema file imports a nested schema file. Bot schema file was valid. But I got an exception by starting the route. I think to support multiple schemas, we have to use schemaFactory.newSchema(Source[] sources); instead of schemaFactory.newSchema(Source source); but I'm not sure. We have to figure it out... Feel free to open a JIRA to track this issue as improvement. This is one of those things that's really hard to get working. And it also tends to break. Includes are a bit different than imports and just doing Source[] doesn't really work either as it still calls the Resolver if the [] doesn't have them in perfect order (the leafs first). If you want a starting point for some code, look into the CXF EndpointReferenceUtils class. There is a SchemaLSResourceResolver class right at the top that makes some attempts at this.It's gone through many iterations trying to get something to work and it seems to work OK now. Dan Best, Christian On Sat, Oct 29, 2011 at 10:04 AM, Claus Ibsen claus.ib...@gmail.com wrote: On Fri, Oct 28, 2011 at 1:13 PM, Lars lars.stuev...@ergogroup.no wrote: I'm using Camel 2.8.2 and I try to use the Validator with a schema which includes other schemas? Is this functionality supported? If yes, how do I specify the schemas? Have you tried to include the other schemas from a schema file? I assume you can use some sort of xsd:include or xsd:import or whatever you do. Lars Stuevold -- View this message in context: http://camel.465427.n5.nabble.com/Validation-supporting-schemas-with-inc ludes-tp4945655p4945655.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/ -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com
Re: Spliter in Camel
Thanks a lot all of you. As you may see the code in above in this thread, I am splitting based on the new line token and sending it to a bean. I noticed som gap in the processing times. I 5 messages beeing processed in a single millisecond and there is a gap of 15 milliseconds before the next 5 message's are sent to the bean .. this pattern repeats itself. Any reason for this time delay. I went through the Splitter and streaming and do not see any specific property i could set for continous streaming. 2011-10-31 13:42:43,874 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,874 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,*874* DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,*890* DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,*890* DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,*905* DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,905 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message 2011-10-31 13:42:43,905 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting bean invocation result on the IN message: Some message -- View this message in context: http://camel.465427.n5.nabble.com/Spliter-in-Camel-tp4940967p4953111.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem running camel-example-cxf-osgi
Thanks--that worked--sort of. Making your recommended changes now reports the following error when I do features:install camel-cxf: karaf@root features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.8.2/xml/fe atures karaf@root features:install war karaf@root features:install camel-spring karaf@root features:install camel-jaxb karaf@root features:install camel-cxf Refreshing bundles org.springframework.context (84), org.springframework.context.support (85), org.apache.camel.camel-core (97), org.apache.servicemix.bundles.jaxb-impl (95) ERROR: Bundle org.springframework.osgi.extender [89] Error stopping bundle. (java.lang.NoClassDefFoundError: org/osgi/framework/ServiceRegistration) java.lang.NoClassDefFoundError: org/osgi/framework/ServiceRegistration at org.springframework.osgi.util.OsgiServiceUtils.unregisterService(OsgiServiceUtils.java:41) at org.springframework.osgi.extender.internal.support.NamespaceManager.unregisterResolverService(NamespaceManager.java:195) at org.springframework.osgi.extender.internal.support.NamespaceManager.destroy(NamespaceManager.java:223) at org.springframework.osgi.extender.internal.activator.ContextLoaderListener.shutdown(ContextLoaderListener.java:547) at org.springframework.osgi.extender.internal.activator.ContextLoaderListener.stop(ContextLoaderListener.java:431) at org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:651) at org.apache.felix.framework.Felix.stopBundle(Felix.java:2216) at org.apache.felix.framework.Felix$RefreshHelper.stop(Felix.java:4489) at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3581) at org.apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:363) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: org.osgi.framework.ServiceRegistration not found by org.springframework.osgi.core [88] at org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:787) at org.apache.felix.framework.ModuleImpl.access$400(ModuleImpl.java:71) at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1768) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 11 more Any more ideas? Glen On 10/30/2011 09:53 PM, Daniel Kulp wrote: The README.txt needs updating. You need to edit the jre.properties and comment out a bunch of the javax.* things that are provided by the bundles. That would include javax.xml.bind*, javax.jws*, javax.xml.soap*, javax.xml.ws*, I think javax.mail, javax.activation. Dan On Sunday, October 30, 2011 7:10:21 PM Glen Mazza wrote: Hello, I'm trying to run the Camel 2.8.2 sample camel-example-cxf-osgi on Apache Karaf 2.2.4. Following these instructions: https://svn.apache.org/repos/asf/camel/trunk/examples/camel-example-cxf-osgi /README.txt, I'm able to run the first four of these five commands with no problem: features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.8.2/xml/features features:install war features:install camel-spring features:install camel-jaxb features:install camel-cxf The last command above, however, reports this error: karaf@root features:install camel-cxf Error executing command: Could not start bundle mvn:org.apache.camel/camel-cxf-transport/2.8.2 in feature(s) camel-cxf-2.8.2: Unable to resolve module org.apache.cxf.bundle [137.0] because it is exposed to package 'javax.xml.bind.attachment' from org.apache.felix.framework [0] and org.apache.servicemix.specs.jaxb-api-2.2 [53.0] via two dependency chains. Chain 1: org.apache.cxf.bundle [137.0] import: (package=javax.xml.bind.attachment) export: package=javax.xml.bind.attachment org.apache.felix.framework [0] Chain 2: org.apache.cxf.bundle [137.0] import: (package=com.sun.tools.xjc.reader.xmlschema.parser) export: package=com.sun.tools.xjc.reader.xmlschema.parser; uses:=javax.xml.bind org.apache.servicemix.bundles.jaxb-xjc [58.0] import: ((package=javax.xml.bind)(version=2.2.0)(!(version=3.0.0))) export: package=javax.xml.bind; uses:=javax.xml.bind.attachment export: package=javax.xml.bind.attachment org.apache.servicemix.specs.jaxb-api-2.2 [53.0] Any idea what the solution would be? Thanks, Glen -- Glen Mazza Talend - http://www.talend.com/apache Blog - http://www.jroller.com/gmazza/ Twitter - glenmazza
route pulling message by query
Hi I am using ActiveMQ 5.4.2 and Camel 2.4.0. *Short description:* I am wondering how, using some headers from messages in a route I can pull another related message from a tap queue at the same time. *Long description:* I have a message that comes into a request queue, and is copied into a request.tap queue. From there I manipulate the message, putting it in other queues as it goes through various processing steps and eventually into a result queue. I want to listen to the result queue, and when a message arrives on it, I want to use the JMSCorrelationID from this message to select the original message from the request.tap queue, and save both the result queue message and the request.tap message into a database. I need this to be transactional. I am using Spring xml for my routes and I can't get two from elements into a route. I am having a hard time understanding how I might do this in Spring xml. Even if I add some beans to do the processing, it seems like I will have to make the second call from my bean (directly to the message broker using JMS) to get the second message. Perhaps I need to write this route directly in Java DSL; or maybe even need to write a JMS listener totally outside of Camel. My preference is to keep it in Camel and in Spring xml, using beans if necessary. Any suggestions are appreciated. -- View this message in context: http://camel.465427.n5.nabble.com/route-pulling-message-by-query-tp4953301p4953301.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem running camel-example-cxf-osgi
You likely need to install the various featuers in a different order.I would try doing: features:install war features:install cxf features:install camel-spring features:install camel-jaxb features:install camel-cxf The cxf feature should pull in the full JAXB-API jars and such and POSSIBLY avoid some of the Refreshing bundles things. Going in that order you can also use CXF 2.5.x instead of 2.4.3. Dan On Monday, October 31, 2011 2:10:58 PM Glen Mazza wrote: Thanks--that worked--sort of. Making your recommended changes now reports the following error when I do features:install camel-cxf: karaf@root features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.8.2/xml/fe atures karaf@root features:install war karaf@root features:install camel-spring karaf@root features:install camel-jaxb karaf@root features:install camel-cxf Refreshing bundles org.springframework.context (84), org.springframework.context.support (85), org.apache.camel.camel-core (97), org.apache.servicemix.bundles.jaxb-impl (95) ERROR: Bundle org.springframework.osgi.extender [89] Error stopping bundle. (java.lang.NoClassDefFoundError: org/osgi/framework/ServiceRegistration) java.lang.NoClassDefFoundError: org/osgi/framework/ServiceRegistration at org.springframework.osgi.util.OsgiServiceUtils.unregisterService(OsgiService Utils.java:41) at org.springframework.osgi.extender.internal.support.NamespaceManager.unregist erResolverService(NamespaceManager.java:195) at org.springframework.osgi.extender.internal.support.NamespaceManager.destroy( NamespaceManager.java:223) at org.springframework.osgi.extender.internal.activator.ContextLoaderListener.s hutdown(ContextLoaderListener.java:547) at org.springframework.osgi.extender.internal.activator.ContextLoaderListener.s top(ContextLoaderListener.java:431) at org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java :651) at org.apache.felix.framework.Felix.stopBundle(Felix.java:2216) at org.apache.felix.framework.Felix$RefreshHelper.stop(Felix.java:4489) at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3581) at org.apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:363) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: org.osgi.framework.ServiceRegistration not found by org.springframework.osgi.core [88] at org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(Module Impl.java:787) at org.apache.felix.framework.ModuleImpl.access$400(ModuleImpl.java:71) at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl .java:1768) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 11 more Any more ideas? Glen On 10/30/2011 09:53 PM, Daniel Kulp wrote: The README.txt needs updating. You need to edit the jre.properties and comment out a bunch of the javax.* things that are provided by the bundles. That would include javax.xml.bind*, javax.jws*, javax.xml.soap*, javax.xml.ws*, I think javax.mail, javax.activation. Dan On Sunday, October 30, 2011 7:10:21 PM Glen Mazza wrote: Hello, I'm trying to run the Camel 2.8.2 sample camel-example-cxf-osgi on Apache Karaf 2.2.4. Following these instructions: https://svn.apache.org/repos/asf/camel/trunk/examples/camel-example-cx f-osgi /README.txt, I'm able to run the first four of these five commands with no problem: features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.8.2/xml/features features:install war features:install camel-spring features:install camel-jaxb features:install camel-cxf The last command above, however, reports this error: karaf@root features:install camel-cxf Error executing command: Could not start bundle mvn:org.apache.camel/camel-cxf-transport/2.8.2 in feature(s) camel-cxf-2.8.2: Unable to resolve module org.apache.cxf.bundle [137.0] because it is exposed to package 'javax.xml.bind.attachment' from org.apache.felix.framework [0] and org.apache.servicemix.specs.jaxb-api-2.2 [53.0] via two dependency chains. Chain 1: org.apache.cxf.bundle [137.0] import: (package=javax.xml.bind.attachment) export: package=javax.xml.bind.attachment org.apache.felix.framework [0] Chain 2: org.apache.cxf.bundle [137.0] import: (package=com.sun.tools.xjc.reader.xmlschema.parser) export: package=com.sun.tools.xjc.reader.xmlschema.parser; uses:=javax.xml.bind org.apache.servicemix.bundles.jaxb-xjc [58.0] import: ((package=javax.xml.bind)(version=2.2.0)(!(version=3.0 .0))) export: package=javax.xml.bind; uses:=javax.xml.bind.attachment export: package=javax.xml.bind.attachment org.apache.servicemix.specs.jaxb-api-2.2 [53.0] Any idea what the solution would be? Thanks, Glen --
Re: route pulling message by query
I think that things could be more easy for you if instead of having a tap queue, you used a short of cache (e.g. camel-cache). You could use camel-cache and camel-activemq to store the tap message to the cache and the result message to activemq. From there you could consume message from activemq, retrieve the message from the cache and then store the message to the database either by using camel-sql, camel-jpa etc. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Problem running camel-example-cxf-osgi
The spring bundles have a lot of optional imports and in some cases when installing features causes all there refreshes, which may result in such errors. In some cases the order may help you with this. I find that when using equinox instead of felix, things work somehow better. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Camel + Peaberry on Karaf
Hi, I'm using camel for a project. My environment is Karaf 2.2.4, with Guice 3.0 (API version 1.3) and Peaberry 1.2 for service injection. Because camel-guice only supports Guice 2.0, and seems to have no built-in support for Peaberry, I'm rolling my own OSGi compatible camel environment. I'm open to structuring this in multiple ways but my general thinking is to have a bundle contain a shared CamelContext (which is an instance of OsgiDefaultCamelContext) and have other bundles contribute Routes to the shared CamelContext by exposing them as services, and when those bundles are stopped, the corresponding routes are stopped and removed. Does that make sense? I have managed to configure Peaberry to create an instance of OsgiDefaultCamelContext and register it as an OSGi service. The Karaf camel:list-contexts command does list the context. I have also succeeded in registering the RoutesBuilder with the CamelContext by calling addRoutesToCamelContext(context); in the routes bundle using the context obtained from the OSGi service registry. At this point the route does successfully run when the context is started. However, when the route bundle is stopped, the route continues to run, even though I call: context.stopRoute(routeId); context.removeRoute(routeId); during the stop (via a Peaberry @Stop annotated method). I have confirmed the stop method is being executed. The route continues to run even if the bundle containing the RoutesBuilder is uninstalled. Has anyone else successfully combined Camel and Guice Peaberry? I'd love some tips on getting this working. Cheers, Raman
camel-cxf service publish address problem
I have a camel-cxf application running in Tomcat behind a proxy with the following camel-cxf.xml: I would like to change myservername:8890 in the endpoint address attribute to localhost:8890, but it doesn't work, i.e, I can't get to the wsdl at the published endpoint URL (with?wsdl appended). Any suggestions as to why that might be and is there a better way to configure this in Tomcat? Note: I am running Tomcat on port 8882 in this scenario and I'm using camel version 2.7.1 and cxf version 2.3.2. -- View this message in context: http://camel.465427.n5.nabble.com/camel-cxf-service-publish-address-problem-tp4953917p4953917.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel-cxf service publish address problem
As you are using the http jetty transport， when you set the address to be http://0.0.0.0:8890/ProcessPrescriptionOrder;, you should be able to get the wsdl with the url http://localhost:8890/ProcessPrescriptionOrder。 0.0.0.0 just let Jetty to listen to all the network interface. Willem -- View this message in context: http://camel.465427.n5.nabble.com/camel-cxf-service-publish-address-problem-tp4953917p4954099.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel + Peaberry on Karaf
Hi Raman, I didn't try Camel and Guice Peaberry together. If you perform camel:route-stop, do you see the route status changed ? Is the behavior the same if you stop the context ? Regards JB On 10/31/2011 11:13 PM, Raman Gupta wrote: Hi, I'm using camel for a project. My environment is Karaf 2.2.4, with Guice 3.0 (API version 1.3) and Peaberry 1.2 for service injection. Because camel-guice only supports Guice 2.0, and seems to have no built-in support for Peaberry, I'm rolling my own OSGi compatible camel environment. I'm open to structuring this in multiple ways but my general thinking is to have a bundle contain a shared CamelContext (which is an instance of OsgiDefaultCamelContext) and have other bundles contribute Routes to the shared CamelContext by exposing them as services, and when those bundles are stopped, the corresponding routes are stopped and removed. Does that make sense? I have managed to configure Peaberry to create an instance of OsgiDefaultCamelContext and register it as an OSGi service. The Karaf camel:list-contexts command does list the context. I have also succeeded in registering the RoutesBuilder with the CamelContext by calling addRoutesToCamelContext(context); in the routes bundle using the context obtained from the OSGi service registry. At this point the route does successfully run when the context is started. However, when the route bundle is stopped, the route continues to run, even though I call: context.stopRoute(routeId); context.removeRoute(routeId); during the stop (via a Peaberry @Stop annotated method). I have confirmed the stop method is being executed. The route continues to run even if the bundle containing the RoutesBuilder is uninstalled. Has anyone else successfully combined Camel and Guice Peaberry? I'd love some tips on getting this working. Cheers, Raman -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
