[jira] Created: (CAMEL-2808) Upgrade to Quartz 1.8.1

Upgrade to Quartz 1.8.1 --- Key: CAMEL-2808 URL: https://issues.apache.org/activemq/browse/CAMEL-2808 Project: Apache Camel Issue Type: Task Components: camel-quartz Affects Versions: 2.3.0 Repor

[jira] Created: (CAMEL-2807) Upgrade to Jetty 7.1.4

Upgrade to Jetty 7.1.4 -- Key: CAMEL-2807 URL: https://issues.apache.org/activemq/browse/CAMEL-2807 Project: Apache Camel Issue Type: Task Components: camel-jetty Affects Versions: 2.3.0 Reporter

Re: List in CXF Web Service using Camel

the web service i am calling that is Axis2 web service so in the service side ... List type of parameter is not received willem.jiang wrote: > > devkatiyar wrote: >> hi Willem , >> >> Thanks for reply what if in same > sendMessage ( >>> @WebParam(name = "carrierList

Re: List in CXF Web Service using Camel

Hi .. Thanks for reply... that's working fine a you told me but .. the web service which i am calling that service do not receive the parameter type java.util.List do i need the type converter dev willem.jiang wrote: > > devkatiyar wrote: >> hi Willem , >> >> Thanks for reply w

[jira] Resolved: (CAMEL-2705) Add class as component for invoking beans but based on FQN classnames

[ https://issues.apache.org/activemq/browse/CAMEL-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-2705. Resolution: Fixed Added wiki documentation as well. > Add class as component for invoking bean

[jira] Commented: (CAMEL-2705) Add class as component for invoking beans but based on FQN classnames

[ https://issues.apache.org/activemq/browse/CAMEL-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60033#action_60033 ] Claus Ibsen commented on CAMEL-2705: There is now a new {{class}} component in Camel trun

[jira] Commented: (CAMEL-2705) Add class as component for invoking beans but based on FQN classnames

[ https://issues.apache.org/activemq/browse/CAMEL-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60032#action_60032 ] Claus Ibsen commented on CAMEL-2705: Yeah the {{class}} gives us the chance to support se

[jira] Assigned: (CAMEL-2705) Add class as component for invoking beans but based on FQN classnames

[ https://issues.apache.org/activemq/browse/CAMEL-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-2705: -- Assignee: Claus Ibsen > Add class as component for invoking beans but based on FQN classnam

[jira] Commented: (CAMEL-2806) camel-jetty can't config the temp directory for the multi part form support rightly

[ https://issues.apache.org/activemq/browse/CAMEL-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60031#action_60031 ] Claus Ibsen commented on CAMEL-2806: Willem could you add documentation on the Jetty wiki

Re: Issue with class : BindySimpleKeyValuePairWithoutSectionMarshallDslTest

Hi I have fixed the test in rev 954023. On Fri, Jun 11, 2010 at 5:05 PM, Charles Moulliard wrote: > Hi, > > I have made modification in camel-bindy concerning the jira ticket : > 2773. I have created a new test for that : > org.apache.camel.dataformat.bindy.fix.BindySimpleKeyValuePairWithoutSect

Re: [DISCUSS] Camel 1.x end of life

+1 Am 11.06.2010 19:53 schrieb "Hadrian Zbarcea" : Hi, We just released Camel 1.6.3 with only 39 issues resolved in about 6 months. Given that: * 1.x is quite stable * 2.x is more feature rich * most of the projects that use Camel we know of already migrated to 2.x * the api changes and migratio

Re: [DISCUSS] Camel 1.x end of life

+1 On 06/12/2010 07:46 AM, Jon Anstey wrote: +1 On Fri, Jun 11, 2010 at 3:22 PM, Hadrian Zbarcea wrote: Hi, We just released Camel 1.6.3 with only 39 issues resolved in about 6 months. Given that: * 1.x is quite stable * 2.x is more feature rich * most of the projects that use Camel we

Re: [DISCUSS] Camel 1.x end of life

+1 On Fri, Jun 11, 2010 at 3:22 PM, Hadrian Zbarcea wrote: > Hi, > > We just released Camel 1.6.3 with only 39 issues resolved in about 6 > months. Given that: > * 1.x is quite stable > * 2.x is more feature rich > * most of the projects that use Camel we know of already migrated to 2.x > * the

Re: [DISCUSS] Camel 1.x end of life

+1 Hadrian Zbarcea schrieb: Hi, We just released Camel 1.6.3 with only 39 issues resolved in about 6 months. Given that: * 1.x is quite stable * 2.x is more feature rich * most of the projects that use Camel we know of already migrated to 2.x * the api changes and migration effort is not that

Re: [DISCUSS] Camel 1.x end of life

+1 On Fri, Jun 11, 2010 at 7:52 PM, Hadrian Zbarcea wrote: > Hi, > > We just released Camel 1.6.3 with only 39 issues resolved in about 6 months. > Given that: > * 1.x is quite stable > * 2.x is more feature rich > * most of the projects that use Camel we know of already migrated to 2.x > * the