Re: Karaf 2.2.3 and Camel 2.8.0
Hi Achim and all, I propose: 1. to cover all Spring bundles in different Karaf spring features including spring-tx 2. release Karaf 2.2.4 soon with this change 3. update Camel features descriptor to use the Karaf spring-tx features (and eventually others, I have to check) 4. release Camel 2.8.1 WDYT ? Regards JB On 09/03/2011 09:38 PM, Achim Nierbeck wrote: Hi JB, I'm +1 on that one, often I was missing the spring-tx feature in the first place :) regards, Achim Am 03.09.2011 18:54, schrieb Jean-Baptiste Onofré: Hi, I checked the issue and the problem is about the spring-tx bundle. spring-tx bundle is not installed by a Karaf features, the first feature which install it is camel-jms (part of the camel-spring). That's why we have a bundle version mismatch between the spring bundles provides by Karaf spring* features, and the one provided by Camel features. I think that it makes sense that Karaf provides all Spring* features, convering all spring bundle, and Camel just uses it. I'm going to discuss with the team to see how we move. Regards JB On 09/02/2011 10:50 PM, mgardiner wrote: I have recently tried using Karaf 2.2.3 which has just updated to use Spring 3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0 because two versions of spring are available. With a new camel release underway are you considering upgrading camel to spring 3.0.6.RELEASE? Thanks. Here's the output Error executing command: Could not start bundle mvn:org.apache.camel/camel-jms/2.8.0 in feature(s) camel-jms-2.8.0: Unable to resolve module org.apache.camel.camel-jms [88.0] because it is exposed to package 'org.springframework.util' from org.springframework.core [82.0] and org.springframework.core [43.0] via two dependency chains. Chain 1: org.apache.camel.camel-jms [88.0] import: ((package=org.springframework.util)(version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.util org.springframework.core [82.0] Chain 2: org.apache.camel.camel-jms [88.0] import: ((package=org.apache.camel.impl)(version=2.8.0)(!(version=2.9.0))) | export: package=org.apache.camel.impl; uses:=org.springframework.jmx.export.annotation org.apache.camel.camel-core [80.0] import: ((package=org.springframework.jmx.export.annotation)(version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.jmx.export.annotation; uses:=org.springframework.aop.target org.springframework.context [48.0] import: ((package=org.springframework.aop.target)(version=3.0.6)(!(version=3.0.7))) | export: package=org.springframework.aop.target; uses:=org.springframework.core org.springframework.aop [47.0] import: ((package=org.springframework.core)(version=3.0.6)(!(version=3.0.7))) | export: package=org.springframework.core; uses:=org.springframework.util export: package=org.springframework.util org.springframework.core [43.0] -- View this message in context: http://camel.465427.n5.nabble.com/Karaf-2-2-3-and-Camel-2-8-0-tp4763828p4763828.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Unable to change throttle with inflight messages
You can change the throttler using JMX http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/management/mbean/ManagedThrottler.html On Fri, Sep 2, 2011 at 12:17 AM, awillia antony.willi...@fronde.com wrote: I would like to be able to change the throttle value dynamically based on a some setting. I have created a bean that returns this value, so it basically looks like this. def.throttle(bean(applicationService, getApplicationChannelQuota)).timePeriodMillis(DAY_IN_MILLI_SECONDS) We are essentially using it to manage a daily quota of messages, which I understand it is not essentialy what it was designed for, but the functionality is much the same. The problem is that if we hit the limit, the message is throttled and stays inflight. This means that we we change the quota to a higher value then that message still remains at the lower value and as such the messages are not released. I have tried to stop and start the route, but this doesnt seem to clear the message (should it?), only restarting the whole application seems to clear things up. Is there a way to do this or would we have to implement our own way of doing quotas? regards Antony -- View this message in context: http://camel.465427.n5.nabble.com/Unable-to-change-throttle-with-inflight-messages-tp4760204p4760204.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: Netty with syslog decoder
Hi Claus Ibsen, Thank you for responding on this, I have already gone thru camel-syslog component, it just provides a DataFormat to convert BSDSyslog stream into string, but it doesn't have any codec implementation to collect all the data over TCP. I am looking for help in how to create my own codec for Netty. Thanks, Trivedi -- View this message in context: http://camel.465427.n5.nabble.com/Netty-with-syslog-decoder-tp4763467p4765477.html Sent from the Camel - Users mailing list archive at Nabble.com.
CXF HTTP Conduit settings not loaded, Pls Help
Hi, I hit the following error when I try to start the server:
Caused by: sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
I suspect the HTTP Conduit config is not loaded caused even I change the
location of the truststore to an invalid location, the system doesn't
complain on the file not found. Pls advice.
Thanks in advance.
attached below is the configuration for my app:
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:cxf=http://camel.apache.org/schema/cxf;
xmlns:http=http://cxf.apache.org/transports/http/configuration;
xmlns:httpj=http://cxf.apache.org/transports/http-jetty/configuration;
xmlns:sec=http://cxf.apache.org/configuration/security;
xmlns:camel=http://camel.apache.org/schema/spring;
xmlns:jaxws=http://cxf.apache.org/jaxws;
xmlns:aop=http://www.springframework.org/schema/aop;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/aop
http://www.springframework.org/schema/aop/spring-aop-2.5.xsd
http://cxf.apache.org/transports/http/configuration
http://cxf.apache.org/schemas/configuration/http-conf.xsd
http://cxf.apache.org/transports/http-jetty/configuration
http://cxf.apache.org/schemas/configuration/http-jetty.xsd
http://cxf.apache.org/configuration/security
http://cxf.apache.org/schemas/configuration/security.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd;
import resource=classpath:META-INF/cxf/cxf.xml /
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml /
import resource=classpath:META-INF/cxf/cxf-extension-http-jetty.xml
/
import resource=/cbig-interceptor-spring.xml /
import resource=/cbig-property-spring.xml /
import resource=/cbig-transformer-spring.xml /
bean id=propertyConfigurer
class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
property name=location
valueclasspath:config.properties/value
/property
/bean
aop:aspectj-autoproxy /
bean id=loggingAspect class=com.test.cbig.aspect.LoggingAspect /
camelContext xmlns=http://camel.apache.org/schema/spring;
packagecom.test/package
/camelContext
httpj:engine-factory bus=cxf
httpj:engine port=${cbigserver.port}
httpj:tlsServerParameters
sec:keyManagers keyPassword=cbig1234
sec:keyStore type=JKS password=cbig123
resource=cbigserver.jks /
/sec:keyManagers
sec:trustManagers
sec:keyStore type=JKS password=cbig123
resource=cbigserver.jks /
/sec:trustManagers
sec:cipherSuitesFilter
sec:include.*_WITH_3DES_.*/sec:include
sec:include.*_WITH_DES_.*/sec:include
sec:exclude.*_WITH_NULL_.*/sec:exclude
sec:exclude.*_DH_anon_.*/sec:exclude
/sec:cipherSuitesFilter
sec:clientAuthentication want=true
required=false /
/httpj:tlsServerParameters
/httpj:engine
/httpj:engine-factory
http:conduit id=http-conduit
name=*.http-conduit
http:tlsClientParameters disableCNCheck=true
secureSocketProtocol=SSL
sec:trustManagers
sec:keyStore type=JKS password=sgleapclient123
file=sgleapclient.jks /
/sec:trustManagers
sec:cipherSuitesFilter
sec:include.*_EXPORT_.*/sec:include
sec:include.*_EXPORT1024_.*/sec:include
sec:include.*_WITH_3DES_.*/sec:include
sec:include.*_WITH_DES_.*/sec:include
sec:include.*_WITH_NULL_.*/sec:include
sec:exclude.*_DH_anon_.*/sec:exclude
/sec:cipherSuitesFilter
/http:tlsClientParameters
/http:conduit
camel:camelContext id=cbigServerContext
camel:onException
camel:exceptioncom.test.cbig.exception.ValidationException/camel:exception
camel:exceptioncom.dbx.wsdl.customersvc.IpException/camel:exception
camel:handled
camel:constanttrue/camel:constant
/camel:handled
camel:process
ref=com.test.cbig.exception.CbigExceptionHandler /
/camel:onException
camel:route
camel:from uri=cxf:bean:cbigEndpoint
camel:description/camel:description
/camel:from
camel:bean
Re: CXF HTTP Conduit settings not loaded, Pls Help
The Camel version is 2.6.0 and CXF version is 2.3.2. -- View this message in context: http://camel.465427.n5.nabble.com/CXF-HTTP-Conduit-settings-not-loaded-Pls-Help-tp4766809p4766820.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Karaf 2.2.3 and Camel 2.8.0
On Sun, Sep 4, 2011 at 8:29 AM, Jean-Baptiste Onofré j...@nanthrax.net wrote: Hi Achim and all, I propose: 1. to cover all Spring bundles in different Karaf spring features including spring-tx 2. release Karaf 2.2.4 soon with this change 3. update Camel features descriptor to use the Karaf spring-tx features (and eventually others, I have to check) 4. release Camel 2.8.1 How soon can Karaf 2.2.4 be released? Would it speed up if the release was based on the 2.2.3 tags, and either did - a) revert back to Spring 3.0.5 - b) bullet #1 above from Jean eg so there are no other changes and thus a confort in the community that Karaf 2.2.4 is a patch release with this single fix to ensure using Karaf + Camel runs smoothly. As its to be used for the next SMX release as well. WDYT ? Regards JB On 09/03/2011 09:38 PM, Achim Nierbeck wrote: Hi JB, I'm +1 on that one, often I was missing the spring-tx feature in the first place :) regards, Achim Am 03.09.2011 18:54, schrieb Jean-Baptiste Onofré: Hi, I checked the issue and the problem is about the spring-tx bundle. spring-tx bundle is not installed by a Karaf features, the first feature which install it is camel-jms (part of the camel-spring). That's why we have a bundle version mismatch between the spring bundles provides by Karaf spring* features, and the one provided by Camel features. I think that it makes sense that Karaf provides all Spring* features, convering all spring bundle, and Camel just uses it. I'm going to discuss with the team to see how we move. Regards JB On 09/02/2011 10:50 PM, mgardiner wrote: I have recently tried using Karaf 2.2.3 which has just updated to use Spring 3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0 because two versions of spring are available. With a new camel release underway are you considering upgrading camel to spring 3.0.6.RELEASE? Thanks. Here's the output Error executing command: Could not start bundle mvn:org.apache.camel/camel-jms/2.8.0 in feature(s) camel-jms-2.8.0: Unable to resolve module org.apache.camel.camel-jms [88.0] because it is exposed to package 'org.springframework.util' from org.springframework.core [82.0] and org.springframework.core [43.0] via two dependency chains. Chain 1: org.apache.camel.camel-jms [88.0] import: ((package=org.springframework.util)(version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.util org.springframework.core [82.0] Chain 2: org.apache.camel.camel-jms [88.0] import: ((package=org.apache.camel.impl)(version=2.8.0)(!(version=2.9.0))) | export: package=org.apache.camel.impl; uses:=org.springframework.jmx.export.annotation org.apache.camel.camel-core [80.0] import: ((package=org.springframework.jmx.export.annotation)(version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.jmx.export.annotation; uses:=org.springframework.aop.target org.springframework.context [48.0] import: ((package=org.springframework.aop.target)(version=3.0.6)(!(version=3.0.7))) | export: package=org.springframework.aop.target; uses:=org.springframework.core org.springframework.aop [47.0] import: ((package=org.springframework.core)(version=3.0.6)(!(version=3.0.7))) | export: package=org.springframework.core; uses:=org.springframework.util export: package=org.springframework.util org.springframework.core [43.0] -- View this message in context: http://camel.465427.n5.nabble.com/Karaf-2-2-3-and-Camel-2-8-0-tp4763828p4763828.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.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: Karaf 2.2.3 and Camel 2.8.0
Hi Claus, I'm going to work on Karaf Spring features today and tomorrow and test it with Camel, CXF and ActiveMQ. The 2.2.4 could contain only this and one other issue (about JMX). So it could be ready by tomorrow evening, and we can cut off the release on Tuesday. So I think that we could be inline for Camel 2.8.1. Is it OK for you ? Regards JB On 09/04/2011 09:24 AM, Claus Ibsen wrote: On Sun, Sep 4, 2011 at 8:29 AM, Jean-Baptiste Onofréj...@nanthrax.net wrote: Hi Achim and all, I propose: 1. to cover all Spring bundles in different Karaf spring features including spring-tx 2. release Karaf 2.2.4 soon with this change 3. update Camel features descriptor to use the Karaf spring-tx features (and eventually others, I have to check) 4. release Camel 2.8.1 How soon can Karaf 2.2.4 be released? Would it speed up if the release was based on the 2.2.3 tags, and either did - a) revert back to Spring 3.0.5 - b) bullet #1 above from Jean eg so there are no other changes and thus a confort in the community that Karaf 2.2.4 is a patch release with this single fix to ensure using Karaf + Camel runs smoothly. As its to be used for the next SMX release as well. WDYT ? Regards JB On 09/03/2011 09:38 PM, Achim Nierbeck wrote: Hi JB, I'm +1 on that one, often I was missing the spring-tx feature in the first place :) regards, Achim Am 03.09.2011 18:54, schrieb Jean-Baptiste Onofré: Hi, I checked the issue and the problem is about the spring-tx bundle. spring-tx bundle is not installed by a Karaf features, the first feature which install it is camel-jms (part of the camel-spring). That's why we have a bundle version mismatch between the spring bundles provides by Karaf spring* features, and the one provided by Camel features. I think that it makes sense that Karaf provides all Spring* features, convering all spring bundle, and Camel just uses it. I'm going to discuss with the team to see how we move. Regards JB On 09/02/2011 10:50 PM, mgardiner wrote: I have recently tried using Karaf 2.2.3 which has just updated to use Spring 3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0 because two versions of spring are available. With a new camel release underway are you considering upgrading camel to spring 3.0.6.RELEASE? Thanks. Here's the output Error executing command: Could not start bundle mvn:org.apache.camel/camel-jms/2.8.0 in feature(s) camel-jms-2.8.0: Unable to resolve module org.apache.camel.camel-jms [88.0] because it is exposed to package 'org.springframework.util' from org.springframework.core [82.0] and org.springframework.core [43.0] via two dependency chains. Chain 1: org.apache.camel.camel-jms [88.0] import: ((package=org.springframework.util)(version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.util org.springframework.core [82.0] Chain 2: org.apache.camel.camel-jms [88.0] import: ((package=org.apache.camel.impl)(version=2.8.0)(!(version=2.9.0))) | export: package=org.apache.camel.impl; uses:=org.springframework.jmx.export.annotation org.apache.camel.camel-core [80.0] import: ((package=org.springframework.jmx.export.annotation)(version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.jmx.export.annotation; uses:=org.springframework.aop.target org.springframework.context [48.0] import: ((package=org.springframework.aop.target)(version=3.0.6)(!(version=3.0.7))) | export: package=org.springframework.aop.target; uses:=org.springframework.core org.springframework.aop [47.0] import: ((package=org.springframework.core)(version=3.0.6)(!(version=3.0.7))) | export: package=org.springframework.core; uses:=org.springframework.util export: package=org.springframework.util org.springframework.core [43.0] -- View this message in context: http://camel.465427.n5.nabble.com/Karaf-2-2-3-and-Camel-2-8-0-tp4763828p4763828.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Karaf 2.2.3 and Camel 2.8.0
On Sun, Sep 4, 2011 at 9:30 AM, Jean-Baptiste Onofré j...@nanthrax.net wrote: Hi Claus, I'm going to work on Karaf Spring features today and tomorrow and test it with Camel, CXF and ActiveMQ. The 2.2.4 could contain only this and one other issue (about JMX). So it could be ready by tomorrow evening, and we can cut off the release on Tuesday. So I think that we could be inline for Camel 2.8.1. Is it OK for you ? Perfect +1 Regards JB On 09/04/2011 09:24 AM, Claus Ibsen wrote: On Sun, Sep 4, 2011 at 8:29 AM, Jean-Baptiste Onofréj...@nanthrax.net wrote: Hi Achim and all, I propose: 1. to cover all Spring bundles in different Karaf spring features including spring-tx 2. release Karaf 2.2.4 soon with this change 3. update Camel features descriptor to use the Karaf spring-tx features (and eventually others, I have to check) 4. release Camel 2.8.1 How soon can Karaf 2.2.4 be released? Would it speed up if the release was based on the 2.2.3 tags, and either did - a) revert back to Spring 3.0.5 - b) bullet #1 above from Jean eg so there are no other changes and thus a confort in the community that Karaf 2.2.4 is a patch release with this single fix to ensure using Karaf + Camel runs smoothly. As its to be used for the next SMX release as well. WDYT ? Regards JB On 09/03/2011 09:38 PM, Achim Nierbeck wrote: Hi JB, I'm +1 on that one, often I was missing the spring-tx feature in the first place :) regards, Achim Am 03.09.2011 18:54, schrieb Jean-Baptiste Onofré: Hi, I checked the issue and the problem is about the spring-tx bundle. spring-tx bundle is not installed by a Karaf features, the first feature which install it is camel-jms (part of the camel-spring). That's why we have a bundle version mismatch between the spring bundles provides by Karaf spring* features, and the one provided by Camel features. I think that it makes sense that Karaf provides all Spring* features, convering all spring bundle, and Camel just uses it. I'm going to discuss with the team to see how we move. Regards JB On 09/02/2011 10:50 PM, mgardiner wrote: I have recently tried using Karaf 2.2.3 which has just updated to use Spring 3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0 because two versions of spring are available. With a new camel release underway are you considering upgrading camel to spring 3.0.6.RELEASE? Thanks. Here's the output Error executing command: Could not start bundle mvn:org.apache.camel/camel-jms/2.8.0 in feature(s) camel-jms-2.8.0: Unable to resolve module org.apache.camel.camel-jms [88.0] because it is exposed to package 'org.springframework.util' from org.springframework.core [82.0] and org.springframework.core [43.0] via two dependency chains. Chain 1: org.apache.camel.camel-jms [88.0] import: ((package=org.springframework.util)(version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.util org.springframework.core [82.0] Chain 2: org.apache.camel.camel-jms [88.0] import: ((package=org.apache.camel.impl)(version=2.8.0)(!(version=2.9.0))) | export: package=org.apache.camel.impl; uses:=org.springframework.jmx.export.annotation org.apache.camel.camel-core [80.0] import: ((package=org.springframework.jmx.export.annotation)(version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.jmx.export.annotation; uses:=org.springframework.aop.target org.springframework.context [48.0] import: ((package=org.springframework.aop.target)(version=3.0.6)(!(version=3.0.7))) | export: package=org.springframework.aop.target; uses:=org.springframework.core org.springframework.aop [47.0] import: ((package=org.springframework.core)(version=3.0.6)(!(version=3.0.7))) | export: package=org.springframework.core; uses:=org.springframework.util export: package=org.springframework.util org.springframework.core [43.0] -- View this message in context: http://camel.465427.n5.nabble.com/Karaf-2-2-3-and-Camel-2-8-0-tp4763828p4763828.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.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: Karaf 2.2.3 and Camel 2.8.0
Hi JB, To be honest I'm a lit bit concern about this solution. If Karaf 2.2.4 ship spring 3.0.6 anyway, even it cover all spring related bundles, and camel can refer those spring features using version range(it might be ok during resolve, but don't forget cxf 2.4.2 features.xml still have srping-jms(3.0.5) feature directly and it's not from karaf, :-)), however it still means the OSGi container provided spring version is 3.0.6, but the cxf(2.4.2) and camel(2.8.1) which will be running in this container are still with spring 3.0.5, it MIGHT be ok with spring 3.0.6 but we can't be that sure(as spring is a kind of fundamental libs for lots of other projects), right? So I suggest either karaf 2.2.4 revert to spring 3.0.5(lit bit weird to me) or camel 2.8.1 should stay with karaf 2.2.2. Regards Freeman On 2011-9-4, at 下午3:30, Jean-Baptiste Onofré wrote: Hi Claus, I'm going to work on Karaf Spring features today and tomorrow and test it with Camel, CXF and ActiveMQ. The 2.2.4 could contain only this and one other issue (about JMX). So it could be ready by tomorrow evening, and we can cut off the release on Tuesday. So I think that we could be inline for Camel 2.8.1. Is it OK for you ? Regards JB On 09/04/2011 09:24 AM, Claus Ibsen wrote: On Sun, Sep 4, 2011 at 8:29 AM, Jean-Baptiste Onofréj...@nanthrax.net wrote: Hi Achim and all, I propose: 1. to cover all Spring bundles in different Karaf spring features including spring-tx 2. release Karaf 2.2.4 soon with this change 3. update Camel features descriptor to use the Karaf spring-tx features (and eventually others, I have to check) 4. release Camel 2.8.1 How soon can Karaf 2.2.4 be released? Would it speed up if the release was based on the 2.2.3 tags, and either did - a) revert back to Spring 3.0.5 - b) bullet #1 above from Jean eg so there are no other changes and thus a confort in the community that Karaf 2.2.4 is a patch release with this single fix to ensure using Karaf + Camel runs smoothly. As its to be used for the next SMX release as well. WDYT ? Regards JB On 09/03/2011 09:38 PM, Achim Nierbeck wrote: Hi JB, I'm +1 on that one, often I was missing the spring-tx feature in the first place :) regards, Achim Am 03.09.2011 18:54, schrieb Jean-Baptiste Onofré: Hi, I checked the issue and the problem is about the spring-tx bundle. spring-tx bundle is not installed by a Karaf features, the first feature which install it is camel-jms (part of the camel-spring). That's why we have a bundle version mismatch between the spring bundles provides by Karaf spring* features, and the one provided by Camel features. I think that it makes sense that Karaf provides all Spring* features, convering all spring bundle, and Camel just uses it. I'm going to discuss with the team to see how we move. Regards JB On 09/02/2011 10:50 PM, mgardiner wrote: I have recently tried using Karaf 2.2.3 which has just updated to use Spring 3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0 because two versions of spring are available. With a new camel release underway are you considering upgrading camel to spring 3.0.6.RELEASE? Thanks. Here's the output Error executing command: Could not start bundle mvn:org.apache.camel/camel-jms/2.8.0 in feature(s) camel- jms-2.8.0: Unable to resolve module org.apache.camel.camel-jms [88.0] because it is exposed to package 'org.springframework.util' from org.springframework.core [82.0] and org.springframework.core [43.0] via two dependency chains. Chain 1: org.apache.camel.camel-jms [88.0] import: ((package=org.springframework.util)(version=3.0.0)(! (version=4.0.0))) | export: package=org.springframework.util org.springframework.core [82.0] Chain 2: org.apache.camel.camel-jms [88.0] import: ((package=org.apache.camel.impl)(version=2.8.0)(! (version=2.9.0))) | export: package=org.apache.camel.impl; uses:=org.springframework.jmx.export.annotation org.apache.camel.camel-core [80.0] import: ((package=org.springframework.jmx.export.annotation) (version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.jmx.export.annotation; uses:=org.springframework.aop.target org.springframework.context [48.0] import: ((package=org.springframework.aop.target)(version=3.0.6)(! (version=3.0.7))) | export: package=org.springframework.aop.target; uses:=org.springframework.core org.springframework.aop [47.0] import: ((package=org.springframework.core)(version=3.0.6)(! (version=3.0.7))) | export: package=org.springframework.core; uses:=org.springframework.util export: package=org.springframework.util org.springframework.core [43.0] -- View this message in context: http://camel.465427.n5.nabble.com/Karaf-2-2-3-and-Camel-2-8-0-tp4763828p4763828.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com --
Re: Karaf 2.2.3 and Camel 2.8.0
I got your point but: - for a general point of view, I still think that Karaf should provide all features for all Spring version, else, it means that we can't warranty the spring version used by the others applications like Camel or CXF - we should have named Karaf 2.3.0 in place of 2.2.3 to address this kind of major update. As reminder, we update to Spring 3.0.6 and add the spring-jms feature to be able to install/support CXF 2.5.0. What we can do: - in Karaf 2.2.4, rollback to Spring 3.0.5 and so be sure that Camel 2.8.x and CXF 2.4.x are supported. - create a Karaf 2.3.x branch (waiting for the 3.0.0), which is exactly like 2.2.x but including Spring 3.0.6.RELEASE (I have to talk with the Karaf team about that, and I put it in copy) WDYT ? Regards JB On 09/04/2011 01:52 PM, Freeman Fang wrote: Hi JB, To be honest I'm a lit bit concern about this solution. If Karaf 2.2.4 ship spring 3.0.6 anyway, even it cover all spring related bundles, and camel can refer those spring features using version range(it might be ok during resolve, but don't forget cxf 2.4.2 features.xml still have srping-jms(3.0.5) feature directly and it's not from karaf, :-)), however it still means the OSGi container provided spring version is 3.0.6, but the cxf(2.4.2) and camel(2.8.1) which will be running in this container are still with spring 3.0.5, it MIGHT be ok with spring 3.0.6 but we can't be that sure(as spring is a kind of fundamental libs for lots of other projects), right? So I suggest either karaf 2.2.4 revert to spring 3.0.5(lit bit weird to me) or camel 2.8.1 should stay with karaf 2.2.2. Regards Freeman On 2011-9-4, at 下午3:30, Jean-Baptiste Onofré wrote: Hi Claus, I'm going to work on Karaf Spring features today and tomorrow and test it with Camel, CXF and ActiveMQ. The 2.2.4 could contain only this and one other issue (about JMX). So it could be ready by tomorrow evening, and we can cut off the release on Tuesday. So I think that we could be inline for Camel 2.8.1. Is it OK for you ? Regards JB On 09/04/2011 09:24 AM, Claus Ibsen wrote: On Sun, Sep 4, 2011 at 8:29 AM, Jean-Baptiste Onofréj...@nanthrax.net wrote: Hi Achim and all, I propose: 1. to cover all Spring bundles in different Karaf spring features including spring-tx 2. release Karaf 2.2.4 soon with this change 3. update Camel features descriptor to use the Karaf spring-tx features (and eventually others, I have to check) 4. release Camel 2.8.1 How soon can Karaf 2.2.4 be released? Would it speed up if the release was based on the 2.2.3 tags, and either did - a) revert back to Spring 3.0.5 - b) bullet #1 above from Jean eg so there are no other changes and thus a confort in the community that Karaf 2.2.4 is a patch release with this single fix to ensure using Karaf + Camel runs smoothly. As its to be used for the next SMX release as well. WDYT ? Regards JB On 09/03/2011 09:38 PM, Achim Nierbeck wrote: Hi JB, I'm +1 on that one, often I was missing the spring-tx feature in the first place :) regards, Achim Am 03.09.2011 18:54, schrieb Jean-Baptiste Onofré: Hi, I checked the issue and the problem is about the spring-tx bundle. spring-tx bundle is not installed by a Karaf features, the first feature which install it is camel-jms (part of the camel-spring). That's why we have a bundle version mismatch between the spring bundles provides by Karaf spring* features, and the one provided by Camel features. I think that it makes sense that Karaf provides all Spring* features, convering all spring bundle, and Camel just uses it. I'm going to discuss with the team to see how we move. Regards JB On 09/02/2011 10:50 PM, mgardiner wrote: I have recently tried using Karaf 2.2.3 which has just updated to use Spring 3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0 because two versions of spring are available. With a new camel release underway are you considering upgrading camel to spring 3.0.6.RELEASE? Thanks. Here's the output Error executing command: Could not start bundle mvn:org.apache.camel/camel-jms/2.8.0 in feature(s) camel-jms-2.8.0: Unable to resolve module org.apache.camel.camel-jms [88.0] because it is exposed to package 'org.springframework.util' from org.springframework.core [82.0] and org.springframework.core [43.0] via two dependency chains. Chain 1: org.apache.camel.camel-jms [88.0] import: ((package=org.springframework.util)(version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.util org.springframework.core [82.0] Chain 2: org.apache.camel.camel-jms [88.0] import: ((package=org.apache.camel.impl)(version=2.8.0)(!(version=2.9.0))) | export: package=org.apache.camel.impl; uses:=org.springframework.jmx.export.annotation org.apache.camel.camel-core [80.0] import: ((package=org.springframework.jmx.export.annotation)(version=3.0.0)(!(version=4.0.0))) | export: package=org.springframework.jmx.export.annotation; uses:=org.springframework.aop.target
XML Validation... getting to the error messages using Camel
I'm using Spring DSL with a camel route to validate XML messages: to uri=validator:file:schemas/schema_name.xsd/ How do I get to the error messages for invalid XML files that do not pass validation? Thanks!
Re: XML Validation... getting to the error messages using Camel
It will throw an ValidationException - see the docs for the component. Den 4. sep. 2011 21:48 skrev Robert J. Liguori ca...@gliesian.com følgende: I'm using Spring DSL with a camel route to validate XML messages: to uri=validator:file:schemas/schema_name.xsd/ How do I get to the error messages for invalid XML files that do not pass validation? Thanks!
Re: Karaf 2.2.3 and Camel 2.8.0
Sounds good to me. Regards Freeman On 2011-9-5, at 上午1:03, Jean-Baptiste Onofré wrote: I got your point but: - for a general point of view, I still think that Karaf should provide all features for all Spring version, else, it means that we can't Sound the spring version used by the others applications like Camel or CXF - we should have named Karaf 2.3.0 in place of 2.2.3 to address this kind of major update. As reminder, we update to Spring 3.0.6 and add the spring-jms feature to be able to install/support CXF 2.5.0. What we can do: - in Karaf 2.2.4, rollback to Spring 3.0.5 and so be sure that Camel 2.8.x and CXF 2.4.x are supported. - create a Karaf 2.3.x branch (waiting for the 3.0.0), which is exactly like 2.2.x but including Spring 3.0.6.RELEASE (I have to talk with the Karaf team about that, and I put it in copy) WDYT ? Regards JB On 09/04/2011 01:52 PM, Freeman Fang wrote: Hi JB, To be honest I'm a lit bit concern about this solution. If Karaf 2.2.4 ship spring 3.0.6 anyway, even it cover all spring related bundles, and camel can refer those spring features using version range(it might be ok during resolve, but don't forget cxf 2.4.2 features.xml still have srping-jms(3.0.5) feature directly and it's not from karaf, :-)), however it still means the OSGi container provided spring version is 3.0.6, but the cxf(2.4.2) and camel(2.8.1) which will be running in this container are still with spring 3.0.5, it MIGHT be ok with spring 3.0.6 but we can't be that sure(as spring is a kind of fundamental libs for lots of other projects), right? So I suggest either karaf 2.2.4 revert to spring 3.0.5(lit bit weird to me) or camel 2.8.1 should stay with karaf 2.2.2. Regards Freeman On 2011-9-4, at 下午3:30, Jean-Baptiste Onofré wrote: Hi Claus, I'm going to work on Karaf Spring features today and tomorrow and test it with Camel, CXF and ActiveMQ. The 2.2.4 could contain only this and one other issue (about JMX). So it could be ready by tomorrow evening, and we can cut off the release on Tuesday. So I think that we could be inline for Camel 2.8.1. Is it OK for you ? Regards JB On 09/04/2011 09:24 AM, Claus Ibsen wrote: On Sun, Sep 4, 2011 at 8:29 AM, Jean-Baptiste Onofréj...@nanthrax.ne t wrote: Hi Achim and all, I propose: 1. to cover all Spring bundles in different Karaf spring features including spring-tx 2. release Karaf 2.2.4 soon with this change 3. update Camel features descriptor to use the Karaf spring-tx features (and eventually others, I have to check) 4. release Camel 2.8.1 How soon can Karaf 2.2.4 be released? Would it speed up if the release was based on the 2.2.3 tags, and either did - a) revert back to Spring 3.0.5 - b) bullet #1 above from Jean eg so there are no other changes and thus a confort in the community that Karaf 2.2.4 is a patch release with this single fix to ensure using Karaf + Camel runs smoothly. As its to be used for the next SMX release as well. WDYT ? Regards JB On 09/03/2011 09:38 PM, Achim Nierbeck wrote: Hi JB, I'm +1 on that one, often I was missing the spring-tx feature in the first place :) regards, Achim Am 03.09.2011 18:54, schrieb Jean-Baptiste Onofré: Hi, I checked the issue and the problem is about the spring-tx bundle. spring-tx bundle is not installed by a Karaf features, the first feature which install it is camel-jms (part of the camel- spring). That's why we have a bundle version mismatch between the spring bundles provides by Karaf spring* features, and the one provided by Camel features. I think that it makes sense that Karaf provides all Spring* features, convering all spring bundle, and Camel just uses it. I'm going to discuss with the team to see how we move. Regards JB On 09/02/2011 10:50 PM, mgardiner wrote: I have recently tried using Karaf 2.2.3 which has just updated to use Spring 3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0 because two versions of spring are available. With a new camel release underway are you considering upgrading camel to spring 3.0.6.RELEASE? Thanks. Here's the output Error executing command: Could not start bundle mvn:org.apache.camel/camel-jms/2.8.0 in feature(s) camel- jms-2.8.0: Unable to resolve module org.apache.camel.camel-jms [88.0] because it is exposed to package 'org.springframework.util' from org.springframework.core [82.0] and org.springframework.core [43.0] via two dependency chains. Chain 1: org.apache.camel.camel-jms [88.0] import: ((package=org.springframework.util)(version=3.0.0)(! (version=4.0.0))) | export: package=org.springframework.util org.springframework.core [82.0] Chain 2: org.apache.camel.camel-jms [88.0] import: ((package=org.apache.camel.impl)(version=2.8.0)(! (version=2.9.0))) | export: package=org.apache.camel.impl; uses:=org.springframework.jmx.export.annotation org.apache.camel.camel-core [80.0] import:
Qpid ObjectMessage problem
I have a simple POC for my problem. I have a producer and a consumer to read and write ObjectMessage to Qpid queue. All that the Dummy object has, is a String. The Dummy object is Serializable as well. Producer seems to be writing the object to the queue without throwing an error but the Consumer which is listening to the queue, is not able to de-serialize the Dummy object. OnMessage (on receiving the message), a simple Dummy dummyObj = (Dummy)((JMSObjectMessage)arg0).getObject(); throws the following error - javax.jms.MessageFormatException: Could not deserialize message: java.io.EOFException at org.apache.qpid.client.message.JMSObjectMessage.getObject(JMSObjectMessage.java:146) at producer.QpidConsumer.onMessage(QpidConsumer.java:81) I have also checked that the Dummy object is getting serialized/deserialized without any problem in a simple POC to test serialization. I don't know what I am missing. Please help. Thanks. ***The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review,retransmission,dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.***
