Re: Modifying SOAP:Fault errors raised by endpoints

Hi, if you are using the Camel transport for CXF then I have an idea what the problem could be. By default the cxf transport for camel does not handle faults as exceptions. You have to manually add a CamelTransportFactory and configure it like described in http://camel.apache.org/camel-transp

Re: Modifying SOAP:Fault errors raised by endpoints

On Sun, Mar 7, 2010 at 8:05 AM, Claus Ibsen wrote: > Hi > > You can enable the soapFault=true on the CamelContext which turns > faults into exceptions. > > Or you can simply add a processor step at the end of your route, and > check if the exchange is a fault > > public void process(Exchange excha

camel-hibernate and sessionFactory

Hi all, I'd like to use an hibernate endPoint but I don't how to set the sessionFactory to this end point. There is no option of the end point allowing to do that and I can't find any documentation about this (or even anyone using it on google). If anyone knows the answer... Or have an idea, ple

Re: camel-hibernate and sessionFactory

Hi Check the source code, and in the unit tests to see how the component test itself. As always we love contributions so you can help improving the documentation or the component itself. http://camel.apache.org/contributing.html On Sun, Mar 7, 2010 at 11:40 AM, altoro wrote: > > Hi all, > > I'

Re: Modifying SOAP:Fault errors raised by endpoints

Hi Claus, I didn't find there is a soapFault option int he CamelContext or cxfEndpoint URI. BTW, There is HandleFault InterceptStrategy, which could be used to turn a fault message into a exception. Here is the DSL for configure it public void configure() throws Exception { HandleFault

Re: Modifying SOAP:Fault errors raised by endpoints

Yeah See void setHandleFault(Boolean handleFault); on RuntimeConfiguration which CamelContext extends. So you can do in a Java DSL route builder context.setHandleFault(true); from("direct:start").to("log:foo").to("log:bar").to("mock:result"); Or you can enable it on a per

activemq component and selector

Hi all, today I tried to use the message selector with activemq camel component. But It seems to just return the message even if the message does not match the selector I used this as uri: consumerTemplate.receiveNoWait("activemq:queue:myqueue?selector=NEXT_RETRY < " + System.currentTimeMillis())

Re: Modifying SOAP:Fault errors raised by endpoints

exchange.getIn().On 07/03/2010 07:05, Claus Ibsen wrote: Hi You can enable the soapFault=true on the CamelContext which turns faults into exceptions. Or you can simply add a processor step at the end of your route, and check if the exchange is a fault public void process(Exchange exchange) { b

Re: Modifying SOAP:Fault errors raised by endpoints

On 07/03/2010 20:08, Jim Talbut wrote: exchange.getIn().On 07/03/2010 07:05, Claus Ibsen wrote: Hi You can enable the soapFault=true on the CamelContext which turns faults into exceptions. Or you can simply add a processor step at the end of your route, and check if the exchange is a fault

Re: Modifying SOAP:Fault errors raised by endpoints

Hi Jim, In MESSAGE DataFormat, camel-cxf endpoint will not read the Message detail information, it just redirect the input stream. PAYLOAD and POJO DataFormat will give you the exception that you want. Willem Jim Talbut wrote: On 07/03/2010 20:08, Jim Talbut wrote: exchange.getIn().On 07/

Re: activemq component and selector

Hi, It's look like camel-activemq[1] or camel-jms[2] don't support to specify the selector option in the URI. [1]http://camel.apache.org/activemq.html [2]http://camel.apache.org/jms.html Willem Norman Maurer wrote: Hi all, today I tried to use the message selector with activemq camel compo

Re: activemq component and selector

Hi Willem, its listed in the jms component site (the one you linked)... Most commonly used options: selector nullSets the JMS Selector, which is an SQL 92 predicate that is used to filter messages within the broker. You may have to encode special characters such as = as %3D Bye, Norm

Re: issue with HTTP response content length being set to CXF request length - causing truncated responses.

On Tue, Mar 2, 2010 at 3:35 AM, Willem Jiang wrote: > Hi > Can you check out the latest released Camel 2.2.0 ? > working on camel 2.2.0, CXF 2.2.6 on Mac10.6 Thanks, Wayne

Re: activemq component and selector

Hi Norman, It's my mistake, and I just committed a unit test[1] to verify the selector option, everything looks good, can you try the test on your environment? [1]http://svn.apache.org/viewvc?rev=920216&view=rev Willem Norman Maurer wrote: Hi Willem, its listed in the jms component site (t

Re: activemq component and selector

Hi William, will try the test later today when I have the code around. At the moment I wonder if its possible something related to use the ConsumerTemplate. I created a Consumer which use the ConsumerTemplate to check for messages on a queue and checks for a header value against the current time.