Re: [VOTE] Release Apache Camel 2.8.0

+0 I think this issue is quite a bit ugly in OSGi but I think it does not absolutely warrant a new release. What do others think? Christian Am 15.07.2011 08:14, schrieb Freeman Fang: Hi Team, Figured out this was caused by improper call BaseTypeConverterRegistry.loadTypeConverters() in OS

Re: [VOTE] Release Apache Camel 2.8.0

Hi Team, Figured out this was caused by improper call BaseTypeConverterRegistry.loadTypeConverters() in OSGi container, which throw exception and prevent Activator in camel-core to get chance to load type converter from bundles, so it's may not only affect the JBI example I mentioned befo

[jira] [Assigned] (CAMEL-4231) shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi container

[ https://issues.apache.org/jira/browse/CAMEL-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4231: -- Assignee: Claus Ibsen > shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi

[jira] [Created] (CAMEL-4232) duplicated camel-core-osgi module in camel-spring and camel-blueprint

duplicated camel-core-osgi module in camel-spring and camel-blueprint - Key: CAMEL-4232 URL: https://issues.apache.org/jira/browse/CAMEL-4232 Project: Camel Issue Type: Impr

[jira] [Updated] (CAMEL-4231) shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi container

[ https://issues.apache.org/jira/browse/CAMEL-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-4231: Attachment: CAMEL-4231.patch > shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSG

[jira] [Updated] (CAMEL-4231) shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi container

[ https://issues.apache.org/jira/browse/CAMEL-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-4231: Fix Version/s: 2.8.0 > shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi > con

[jira] [Created] (CAMEL-4231) shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi container

shouldn't call BaseTypeConverterRegistry.loadTypeConverters() in OSGi container --- Key: CAMEL-4231 URL: https://issues.apache.org/jira/browse/CAMEL-4231 Project: Camel

[jira] [Created] (CAMEL-4230) BeanProcessor - Improved exception message if failed to invoke method

BeanProcessor - Improved exception message if failed to invoke method - Key: CAMEL-4230 URL: https://issues.apache.org/jira/browse/CAMEL-4230 Project: Camel Issue Type: Impr

[jira] [Created] (CAMEL-4229) Added wrap method for template, consumer and context in org.apache.camel.test.junit4.CamelContextSupport

Added wrap method for template, consumer and context in org.apache.camel.test.junit4.CamelContextSupport - Key: CAMEL-4229 URL: https://issues.apache.org/jira

[jira] [Created] (CAMEL-4228) Use the customer configuration for camel-itest-osgi

Use the customer configuration for camel-itest-osgi Key: CAMEL-4228 URL: https://issues.apache.org/jira/browse/CAMEL-4228 Project: Camel Issue Type: Improvement Components: test

[jira] [Reopened] (CAMEL-4176) camel-http4 component does not support proxy settings for HTTPS

[ https://issues.apache.org/jira/browse/CAMEL-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Doffe reopened CAMEL-4176: -- Regression: [Regression] > camel-http4 component does not support proxy settings for HTTPS > --

[jira] [Commented] (CAMEL-4176) camel-http4 component does not support proxy settings for HTTPS

[ https://issues.apache.org/jira/browse/CAMEL-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065644#comment-13065644 ] Don Doffe commented on CAMEL-4176: -- I'm testing against the Release Candidate from the re

Re: [VOTE] Release Apache Camel 2.8.0

I'm hitting an issue with 2.8.0 using Scala. I can no longer reference the template variable in CamelTestSupport because it has been turned into a protected static variable. See for more details: http://camel.465427.n5.nabble.com/CamelTestSupport-template-variable-missing-changed-in-2-8-0-td458770

[jira] [Resolved] (CAMEL-4214) A name should be specified in the karaf features-file

[ https://issues.apache.org/jira/browse/CAMEL-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller resolved CAMEL-4214. - Resolution: Fixed > A name should be specified in the karaf features-file > -

[jira] [Closed] (CAMEL-4214) A name should be specified in the karaf features-file

[ https://issues.apache.org/jira/browse/CAMEL-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller closed CAMEL-4214. --- > A name should be specified in the karaf features-file > ---

[jira] [Commented] (CAMEL-4214) A name should be specified in the karaf features-file

[ https://issues.apache.org/jira/browse/CAMEL-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065551#comment-13065551 ] Christian Müller commented on CAMEL-4214: - Committed r1146903 Thanks Jonas for the

[jira] [Work started] (CAMEL-4214) A name should be specified in the karaf features-file

[ https://issues.apache.org/jira/browse/CAMEL-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4214 started by Christian Müller. > A name should be specified in the karaf features-file > - > >

Re: [DISCUSS] - Camel 2.9 - JMX and reducing Spring depdendency

+1 I also think it's a good idea. Let me know if you would like to distribute the work... Best, Christian On Thu, Jul 14, 2011 at 8:53 AM, Claus Ibsen wrote: > Hi > > Now that Camel 2.8 is getting close to being released. Its in vote. > > I took a bit time to writeup a design note about some go

[jira] [Updated] (CAMEL-4118) Improve the Aggregator to be able to force a flush all aggregated exchanges

[ https://issues.apache.org/jira/browse/CAMEL-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben O'Day updated CAMEL-4118: - Attachment: CAMEL-4118.patch > Improve the Aggregator to be able to force a flush all aggregated exchange

[jira] [Updated] (CAMEL-4118) Improve the Aggregator to be able to force a flush all aggregated exchanges

[ https://issues.apache.org/jira/browse/CAMEL-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben O'Day updated CAMEL-4118: - Attachment: (was: CAMEL-4118.patch) > Improve the Aggregator to be able to force a flush all aggregat

[jira] [Updated] (CAMEL-4118) Improve the Aggregator to be able to force a flush all aggregated exchanges

[ https://issues.apache.org/jira/browse/CAMEL-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben O'Day updated CAMEL-4118: - Attachment: (was: CAMEL-4097-4118.patch) > Improve the Aggregator to be able to force a flush all agg

[jira] [Updated] (CAMEL-4118) Improve the Aggregator to be able to force a flush all aggregated exchanges

[ https://issues.apache.org/jira/browse/CAMEL-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben O'Day updated CAMEL-4118: - Attachment: CAMEL-4118.patch thanks Claus, here is an updated patch to simply support forcing completion

[jira] [Resolved] (CAMEL-4226) add Expressions support on to(), bean() and beanRef() to allow for dynamic endpints (similar to recipientList)

[ https://issues.apache.org/jira/browse/CAMEL-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben O'Day resolved CAMEL-4226. -- Resolution: Won't Fix thanks Claus, I figured there were good reasons this wasn't done already, but it

[jira] [Resolved] (CAMEL-4212) http components should support parameters with multiple values when mapping to Camel headers

[ https://issues.apache.org/jira/browse/CAMEL-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4212. Resolution: Fixed Okay was a bit more icky to implement as we have in Camel - 4 http producers - 2

Re: [DISCUSS] - Camel 2.9 - JMX and reducing Spring depdendency

+1 Speaking of reducing to slf4j...I'm in the process of stripping Pax Logger down to a single .jar for my own convenience. Would a single-jar logger be desirable as a Camel ingredient? Don On Thu, Jul 14, 2011 at 11:00 AM, Christian Schneider wrote: > I also think it is a good time now to get

[jira] [Commented] (CAMEL-4212) http components should support parameters with multiple values when mapping to Camel headers

[ https://issues.apache.org/jira/browse/CAMEL-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065367#comment-13065367 ] Claus Ibsen commented on CAMEL-4212: This also applies for HTTP headers. And on the

Re: [VOTE] Release Apache Camel 2.8.0

Tried a few examples and they look good. However the manual just shows "Download of http://camel.apache.org/book-in-one-page.html failed" Not sure what happened there in the build. Also, the NOTICE.txt file has the wrong date copyright date Copyright 2007-2010 The Apache Software Foundation Thi

Re: [DISCUSS] - Camel 2.9 - JMX and reducing Spring depdendency

I also think it is a good time now to get a bit more independent from spring. +1 Christian Am 14.07.2011 08:53, schrieb Claus Ibsen: Hi Now that Camel 2.8 is getting close to being released. Its in vote. I took a bit time to writeup a design note about some goals for Camel 2.9. At first it

Re: [DISCUSS] - Camel 2.9 - JMX and reducing Spring depdendency

I am all for that. Especially removing the JMX annotations that are Spring based. /je On Jul 14, 2011, at 12:53 AM, Claus Ibsen wrote: > Hi > > Now that Camel 2.8 is getting close to being released. Its in vote. > > I took a bit time to writeup a design note about some goals for Camel 2.

Re: [VOTE] Release Apache Camel 2.8.0

Hi Team, I build servicemix component and then servicemix 4 kit against camel 2.8.0 stage repo. I found one issue that when I try to deploy camel and bridge-camel example shipped with servicemix4 kit. I get stacktrace like

Re: Camel SMPP Delivery report reconcilliation

Thanks! I will repost the thread and response to the users list. Regards Jan -- View this message in context: http://camel.465427.n5.nabble.com/Camel-SMPP-Delivery-report-reconcilliation-tp4582833p4585990.html Sent from the Camel Development mailing list archive at Nabble.com.

[jira] [Commented] (CAMEL-4086) Ability to send multipart and multilingual messages in camel-smpp

[ https://issues.apache.org/jira/browse/CAMEL-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065109#comment-13065109 ] Sergey Zhemzhitsky commented on CAMEL-4086: --- Hi, unfortunately I don't have enou

Re: [VOTE] Release Apache Camel 2.8.0

+1 I tested a bunch of routes and components in Karaf 2.2.2 without problem. Regards JB On 07/13/2011 10:49 PM, Hadrian Zbarcea wrote: A new minor release apache-camel-2.8.0 is out with approximately 409 issues resolved: improvements and bug fixes [1]. This is a release with a record number of

Re: [VOTE] Release Apache Camel 2.8.0

Hi I gave the Camel in Action source code an upgrade to Camel 2.8.0 and a test spin. So far it looked fine. I will check later in the examples and a few other tings before I cast my vote. On Wed, Jul 13, 2011 at 10:49 PM, Hadrian Zbarcea wrote: > A new minor release apache-camel-2.8.0 is out

[jira] [Commented] (CAMEL-4226) add Expressions support on to(), bean() and beanRef() to allow for dynamic endpints (similar to recipientList)

[ https://issues.apache.org/jira/browse/CAMEL-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065096#comment-13065096 ] Claus Ibsen commented on CAMEL-4226: Ben you may be able to experiment with ToDefiniti