Re: CXF component fails to marshal SOAP fault details

Cheers Willem. Viktoras -- View this message in context: http://camel.465427.n5.nabble.com/CXF-component-fails-to-marshal-SOAP-fault-details-tp5718686p5718701.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Getting consumer endpoint details or exchange headers in custom ExceptionHandler

Hi During routing a message you can use the Camel error handling. http://camel.apache.org/error-handling-in-camel.html Such as an onException to deal with the exception. The exchange gets enriched with a header/property with the last endpoint it was sent to, so you can grab that detail to known w

Re: Getting consumer endpoint details or exchange headers in custom ExceptionHandler

I'm not sure if you are using consumer.exceptionHandler[1] to do this kind of job. There are some enhancement since Camel 2.10.0, you can define a consumer.bridgeErrorHandler[2] to catch the exception if it is thrown from the file of ftp consumer. [1]http://camel.apache.org/file2.html#File2-How

Re: CXF component fails to marshal SOAP fault details

In the PAYLOAD dataformat, you need to marshal the SOAP fault detail yourself, like this[1] In the MESSAGE dataformat, you need to marshal the whole SOAP fault yourself, as camel-cxf just redirect the input stream itself. [1]https://svn.apache.org/repos/asf/camel/trunk/camel/components/camel-cxf/s

Re: CXF consumer to ActiveMQ results in exhausted attempts

Babak you have saved my day! Thanks a lot!! I have added to my pom.xml the last available release of org.springframework:spring-jms and problem solved. org.springframework spring-jms 3.1.2.RELEASE Thanks a lot guys! -- View this message in context: http://camel.

Re: Getting consumer endpoint details or exchange headers in custom ExceptionHandler

Guys please if you can comment? I am kinda stuck -- View this message in context: http://camel.465427.n5.nabble.com/Getting-consumer-endpoint-details-or-exchange-headers-in-custom-ExceptionHandler-tp5718633p5718694.html Sent from the Camel - Users mailing list archive at Nabble.com.

CXF component fails to marshal SOAP fault details

Hi, I have a simple test.HelloWorld service which is deployed to ServiceMix 4.4.2 (Camel 2.8.5). The service has one operation: The service is exposed using cxfEndpoint. The endpoint passes the payload to FatalProcessor. The processor just throws CantTalkFault. Camel context looks like this:

Re: JAXB Data Format

Wondering how you had the patience to go through this entire mail thread that helped you resolve your issue. The Camel Riders are awesome! Regards, Jothi On Wed, Sep 5, 2012 at 2:32 PM, Naveen Raj wrote: > Thanks, > > This helped me with the same issue i faced. > > thanks, > Naveen Raj Balasub

Re: Issue with Camel annotations not being processed [OSGi, Blueprint, Javaconfig]

I didn't know it was meant to be Aries and not Gemini. I see the documentation clearly states Aries, my bad! I'll try Aries and see if this fixes my problem. I am in no way bound to use Gemini... -- View this message in context: http://camel.465427.n5.nabble.com/Issue-with-Camel-annotations-

Re: Issue with Camel annotations not being processed [OSGi, Blueprint, Javaconfig]

Hi Using Aries Blueprint should work fine. There is possible a need for a Gemini integration with Camel to make this work out of the box. Fell free to help out, and take a look at camel-blueprint, which is the component that integrates with Aries Blueprint. Yeah that should maybe have been named

How to act as TCP-client with Camel + Mina/Netty?

I'm working on my first Camel-based integration project and have a question about integrating to an existing TCP-server (for which I don't have a source code so no changes can be done to it) with either Mina or Netty (not sure which is the better one to use for this). I've read the Camel in Action-

Re: JAXB Data Format

Thanks, This helped me with the same issue i faced. thanks, Naveen Raj Balasubramaniam -- View this message in context: http://camel.465427.n5.nabble.com/Re-JAXB-Data-Format-tp5717522p5718669.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Problem with Camel proxies and hashCode()

Here's an issue with a test case attached: https://issues.apache.org/jira/browse/CAMEL-5571 Best regards, Harald > 2012/9/5 Claus Ibsen : >> >> Yeah methods from java.lang.Object should be omitted to be remotely called. >> >> Do you have a stacktrace? And can you create a small unit test that >>

Optimal way of exposing a JMX MBean when using Camel

Hi Folks, I have a bean that I would like to expose via JMX. I am currently using the org.springframework.jmx.export.MBeanExporter to reference/export the bean. The bean then gets exported to the MBeanServer that Camel stands up and I can manage it via JConsole etc. I'm wondering what are the bes

Re: Problem with Camel proxies and hashCode()

Ok, I'll try to write a self-contained test. Shouldn't be too hard, I see the same exception when calling proxy.hashCode() in my own methods. Best regards, Harald 2012/9/5 Claus Ibsen : > > Yeah methods from java.lang.Object should be omitted to be remotely called. > > Do you have a stacktrace? A

Re: Problem with Camel proxies and hashCode()

On Wed, Sep 5, 2012 at 10:43 AM, Harald Wellmann wrote: > In a Spring Web + JPA application running on Tomcat, I'm using > CamelProxyFactoryBean to create a proxy for a service interface, where > the actual service implementation is a remote JMS endpoint. The > service is @InOnly. > > When shuttin

Problem with Camel proxies and hashCode()

In a Spring Web + JPA application running on Tomcat, I'm using CamelProxyFactoryBean to create a proxy for a service interface, where the actual service implementation is a remote JMS endpoint. The service is @InOnly. When shutting down the web application, I'm getting an exception from the proxy

Re: Camel CXF Component with ActiveMQ

I was facing a similar issue and the solution was very useful. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-Component-with-ActiveMQ-tp474631p5718646.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CXF consumer to ActiveMQ results in exhausted attempts

Hi You've got some old version of spring-jms-xxx.jar on your classpath which is the root cause of the problem. In case you make use of Maven for your build then: mvn dependency:tree -Dverbose=true could help you to spot this. Babak -- View this message in context: http://camel.465427.n5.n

CXF consumer to ActiveMQ results in exhausted attempts

Hi all, I have the following situation: I need to expose a code-first cxf webservice and send that consult to an activeMQ. I get an error that you can follow in the stack trace but what I cannot understand is that it doesn't matter if I bean component representing the activeMQ connection