Http Status code from CXFRS - not working.

Hi I am posting a message to external web service using cxfrs web service. I gave in the route as .to(cxfrs://{{url}) , its connecting to server and i am expecting the http response status (like 201, 404, etc) in return. After .to statement i have a processor where i am trying to print the head

[jira] [Commented] (CAMEL-4125) Some components missing from final assemblies

[ https://issues.apache.org/jira/browse/CAMEL-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052363#comment-13052363 ] Claus Ibsen commented on CAMEL-4125: Yes, camel-core-xml is an "abstract" component. I

[jira] [Issue Comment Edited] (CAMEL-4125) Some components missing from final assemblies

[ https://issues.apache.org/jira/browse/CAMEL-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052300#comment-13052300 ] Willem Jiang edited comment on CAMEL-4125 at 6/21/11 2:54 AM: --

[jira] [Commented] (CAMEL-4127) camel-jboss 2.6.0 is incompatible with camel-core 2.7.2

[ https://issues.apache.org/jira/browse/CAMEL-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052330#comment-13052330 ] Willem Jiang commented on CAMEL-4127: - We need to release new version of camel extra t

[jira] [Updated] (CAMEL-4127) camel-jboss 2.6.0 is incompatible with camel-core 2.7.2

[ https://issues.apache.org/jira/browse/CAMEL-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Shepherd updated CAMEL-4127: -- Attachment: CAMEL-4127.diff > camel-jboss 2.6.0 is incompatible with camel-core 2.7.2 > ---

[jira] [Created] (CAMEL-4127) camel-jboss 2.6.0 is incompatible with camel-core 2.7.2

camel-jboss 2.6.0 is incompatible with camel-core 2.7.2 --- Key: CAMEL-4127 URL: https://issues.apache.org/jira/browse/CAMEL-4127 Project: Camel Issue Type: Bug Affects Versions: 2.7.2

[jira] [Commented] (CAMEL-4125) Some components missing from final assemblies

[ https://issues.apache.org/jira/browse/CAMEL-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052300#comment-13052300 ] Willem Jiang commented on CAMEL-4125: - @Hadrian, camel-spring bundle and camel-bluepri

[jira] [Commented] (CAMEL-4120) camel-sql - JDBC aggregation repository - Should use ClassResolver from Camel to load classes

[ https://issues.apache.org/jira/browse/CAMEL-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052247#comment-13052247 ] Christian Müller commented on CAMEL-4120: - Committed r1137802 > camel-sql - JDBC

[jira] [Closed] (CAMEL-4120) camel-sql - JDBC aggregation repository - Should use ClassResolver from Camel to load classes

[ https://issues.apache.org/jira/browse/CAMEL-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller closed CAMEL-4120. --- Resolution: Fixed > camel-sql - JDBC aggregation repository - Should use ClassResolver from C

[jira] [Updated] (CAMEL-4120) camel-sql - JDBC aggregation repository - Should use ClassResolver from Camel to load classes

[ https://issues.apache.org/jira/browse/CAMEL-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-4120: Fix Version/s: (was: 2.9.0) 2.8.0 > camel-sql - JDBC aggregation rep

[jira] [Work started] (CAMEL-4120) camel-sql - JDBC aggregation repository - Should use ClassResolver from Camel to load classes

[ https://issues.apache.org/jira/browse/CAMEL-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-4120 started by Christian Müller. > camel-sql - JDBC aggregation repository - Should use ClassResolver from Camel > to load classes > -

[jira] [Assigned] (CAMEL-4126) S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType

[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller reassigned CAMEL-4126: --- Assignee: Christian Müller > S3Producer does not use CamelAwsS3ContentLength or Camel

[jira] [Assigned] (CAMEL-4120) camel-sql - JDBC aggregation repository - Should use ClassResolver from Camel to load classes

[ https://issues.apache.org/jira/browse/CAMEL-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller reassigned CAMEL-4120: --- Assignee: Christian Müller > camel-sql - JDBC aggregation repository - Should use Cla

[jira] [Updated] (CAMEL-4126) S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType

[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brendan Long updated CAMEL-4126: Attachment: s3-content-length-and-type-patch.diff Patch to use these headers > S3Producer does not

[jira] [Commented] (CAMEL-4126) S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType

[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052193#comment-13052193 ] Richard Kettelerij commented on CAMEL-4126: --- Patches are always welcome. > S3Pr

[jira] [Updated] (CAMEL-4126) S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType

[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brendan Long updated CAMEL-4126: Component/s: (was: camel-atom) camel-aws > S3Producer does not use CamelAwsS3C

[jira] [Created] (CAMEL-4126) S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType

S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType Key: CAMEL-4126 URL: https://issues.apache.org/jira/browse/CAMEL-4126 Project: Camel Issue Type

[jira] [Issue Comment Edited] (CAMEL-4125) Some components missing from final assemblies

[ https://issues.apache.org/jira/browse/CAMEL-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052115#comment-13052115 ] Hadrian Zbarcea edited comment on CAMEL-4125 at 6/20/11 6:16 PM: ---

[jira] [Commented] (CAMEL-4125) Some components missing from final assemblies

[ https://issues.apache.org/jira/browse/CAMEL-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052115#comment-13052115 ] Hadrian Zbarcea commented on CAMEL-4125: @Claus, do yo want to elaborate more what

[jira] [Commented] (CAMEL-4125) Some components missing from final assemblies

[ https://issues.apache.org/jira/browse/CAMEL-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052085#comment-13052085 ] Claus Ibsen commented on CAMEL-4125: And I dont think camel-karaf-commands should be t

[jira] [Commented] (CAMEL-4125) Some components missing from final assemblies

[ https://issues.apache.org/jira/browse/CAMEL-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052083#comment-13052083 ] Claus Ibsen commented on CAMEL-4125: camel-core-xml is not a released component (its j

[jira] [Created] (CAMEL-4125) Some components missing from final assemblies

Some components missing from final assemblies - Key: CAMEL-4125 URL: https://issues.apache.org/jira/browse/CAMEL-4125 Project: Camel Issue Type: Task Components: build system

[jira] [Updated] (CAMEL-4125) Some components missing from final assemblies

[ https://issues.apache.org/jira/browse/CAMEL-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated CAMEL-4125: --- Attachment: CAMEL-4125.txt > Some components missing from final assemblies >

[jira] [Commented] (CAMEL-1817) Moved logic for defensive copy of current exchange from Pipeline to RedeliveryErrorHandler

[ https://issues.apache.org/jira/browse/CAMEL-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052074#comment-13052074 ] Claus Ibsen commented on CAMEL-1817: Implemented this today > Moved logic for defensi

[jira] [Resolved] (CAMEL-4123) camel-jms - Should create JmsMessage with default message delivery mode

[ https://issues.apache.org/jira/browse/CAMEL-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4123. Resolution: Fixed > camel-jms - Should create JmsMessage with default message delivery mode > -

[jira] [Resolved] (CAMEL-4124) camel-jms - Issue with using preserveMessageQos and JMS delivery mode not being propagated correctly

[ https://issues.apache.org/jira/browse/CAMEL-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4124. Resolution: Fixed > camel-jms - Issue with using preserveMessageQos and JMS delivery mode not > be

[jira] [Commented] (CAMEL-4122) JMX API to create/delete endpoint

[ https://issues.apache.org/jira/browse/CAMEL-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052047#comment-13052047 ] james strachan commented on CAMEL-4122: --- BTW you can create endpoints via the Java A

[jira] [Commented] (CAMEL-4122) JMX API to create/delete endpoint

[ https://issues.apache.org/jira/browse/CAMEL-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052046#comment-13052046 ] james strachan commented on CAMEL-4122: --- In ActiveMQ and ServiceMix you can view/cre

[jira] [Created] (CAMEL-4124) camel-jms - Issue with using preserveMessageQos and JMS delivery mode not being propagated correctly

camel-jms - Issue with using preserveMessageQos and JMS delivery mode not being propagated correctly Key: CAMEL-4124 URL: https://issues.apache.org/jira/browse/CA

[jira] [Created] (CAMEL-4123) camel-jms - Should create JmsMessage with default message delivery mode

camel-jms - Should create JmsMessage with default message delivery mode --- Key: CAMEL-4123 URL: https://issues.apache.org/jira/browse/CAMEL-4123 Project: Camel Issue Type:

[jira] [Commented] (CAMEL-4122) JMX API to create/delete endpoint

[ https://issues.apache.org/jira/browse/CAMEL-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052036#comment-13052036 ] Hadrian Zbarcea commented on CAMEL-4122: Agree, but isn't it a bit too low level?

Re: [jira] [Commented] (CAMEL-3948) Issue with the RSET command with POP3 servers

POP3Folder and POP3Message are both included in the javadoc for the Javamail API... http://javamail.kenai.com/nonav/javadocs/index.html?com/sun/mail/pop3/package-summary.html And the license that comes in the API download explicitly lists pop3.jar along with mail.jar as redistributables. So is t

[jira] [Assigned] (CAMEL-4122) JMX API to create/delete endpoint

[ https://issues.apache.org/jira/browse/CAMEL-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4122: -- Assignee: Claus Ibsen > JMX API to create/delete endpoint > - >

[jira] [Updated] (CAMEL-4122) JMX API to create/delete endpoint

[ https://issues.apache.org/jira/browse/CAMEL-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4122: --- Component/s: jmx Priority: Minor (was: Major) Affects Version/s: 2.7.0 > JMX

[jira] [Created] (CAMEL-4122) JMX API to create/delete endpoint

JMX API to create/delete endpoint - Key: CAMEL-4122 URL: https://issues.apache.org/jira/browse/CAMEL-4122 Project: Camel Issue Type: Improvement Reporter: james strachan Fix For: 2.8.0

Re: [jira] [Commented] (CAMEL-3948) Issue with the RSET command with POP3 servers

com.sun.mail.pop3.POP3Folder and com.sun.mail.pop3.POP3Message are supplied by mail.jar in the Javamail API, version 1.4.4. If the mail component can't be dependent on part of mail.jar, does that mean it can't be dependent on any of mail.jar? Don On Mon, Jun 20, 2011 at 2:57 AM, Claus Ibsen (JIR

Re: [DISCUSS] - Error handler and redelivery with a Processor - Time to take action

Hi For the past two days I have been working on this and running many tests to ensure my changes are working as expected. I actually spotted a few unit tests that was wrong and could correct those as well. I have just committed the changes as I feel it fixes issues with redelivery and also improv

[jira] [Resolved] (CAMEL-1817) Moved logic for defensive copy of current exchange from Pipeline to RedeliveryErrorHandler

[ https://issues.apache.org/jira/browse/CAMEL-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1817. Resolution: Fixed Fix Version/s: (was: 3.0.0) 2.8.0 > Moved logic for

[jira] [Resolved] (CAMEL-4121) Prefer to use SetExchangePattern over InOut / InOnly to permanently alter the MEP

[ https://issues.apache.org/jira/browse/CAMEL-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4121. Resolution: Fixed > Prefer to use SetExchangePattern over InOut / InOnly to permanently alter the

[jira] [Resolved] (CAMEL-4117) RedeliverErrorHandler - Should make defensive copy of Exchange so redelivery works for using Processor

[ https://issues.apache.org/jira/browse/CAMEL-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4117. Resolution: Fixed Fix Version/s: (was: 2.9.0) > RedeliverErrorHandler - Should make defe

[jira] [Created] (CAMEL-4121) Prefer to use SetExchangePattern over InOut / InOnly to permanently alter the MEP

Prefer to use SetExchangePattern over InOut / InOnly to permanently alter the MEP -- Key: CAMEL-4121 URL: https://issues.apache.org/jira/browse/CAMEL-4121 Project: Camel

[jira] [Commented] (CAMEL-4116) SpringWebserviceConsumer should check if there is an Exception connected to the exchange and throw that one if it exists so that the default Errorhandling in spring-ws

[ https://issues.apache.org/jira/browse/CAMEL-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051846#comment-13051846 ] Joakim Sundqvist commented on CAMEL-4116: - I have have tried the snapshot build an