Is this a bug of try-catch or transaction?

Hi: The camel's transaction required the transacted-error-handler, but try-catch required no-error-handler. They will conflict; following is a sample that the try-catch cannot works while using transaction. but I am not sure if this is bug or just a camel's limit? For example, the following rout

Re: does camel support custom policy for processor level ?

ext2 wrote: Thanks Willem: I got it; and using this feature I could define custom transaction range in a single route(need not separate them in different route just for transaction purpose); I'm afraid you cannot configure the transaction per process, as Camel transaction is based on Spring,

Re: Is this a bug of try-catch or transaction?

Move the before the On Thu, Apr 22, 2010 at 9:08 AM, ext2 wrote: > > Hi: > > The camel's transaction required the transacted-error-handler, but try-catch > required no-error-handler. They will conflict; following is a sample that > the try-catch cannot works while using transaction. but I am n

Re: does camel support custom policy for processor level ?

ext2 wrote: Thanks Willem: I got it; and using this feature I could define custom transaction range in a single route(need not separate them in different route just for transaction purpose); I just checked the code, the SpringTransactionPolicy is setting a new TransactionErrorHandler per rout

答复: Is this a bug of try-catch o r transaction?

Thanks Claus Ibsen: If we just consider this example, move policy before doTry could resolve it; but If we consider another situation: ..some other operation .. > > > > > > > java.lang.Exception > > > > As for normal unders

Re: does camel support custom policy for processor level ?

Thanks Willem: You are right; It seems I must do something else to support the feature(define custom transaction-section in single route). And the real problem is not only the spring's transaction-template, but also the camel's transaction support ; the camel's transaction always ask for tran

XPath Spliiter Problem

Hello everyone, I am not an advanced user of Camel. When I use XPath Splitter , I get only one record in the result. How do I get multiple records ? For example : My XML file is abc xyz abc123 xyz123 abcqqq xyzqqq I use the following configuration in the xml file : http://cam

Re: 答复: Is this a bug of try-catch or transaction?

How about using the onExeption[1] ? It works within the ErrorHandler, and it can do the same thing as doTry... doCatch does. [1]http://camel.apache.org/exception-clause.html Willem ext2 wrote: Thanks Claus Ibsen: If we just consider this example, move policy before doTry could resolve it;

Re: XPath Spliiter Problem

The root tag in the xml file is a , the sub tag is b and then cone and ctwo are the subtags of b. It did not get printed in the above post. Sorry for the inconvience. -- View this message in context: http://old.nabble.com/XPath-Spliiter-Problem-tp28325959p28325991.html Sent from the Camel - User

Re: XPath Spliiter Problem

Do not use resultType="java.lang.String" By default it uses some XPath standard type (NODESET) which is defined in javax.xml.xpath.XPathConstants The NODESET should be able to contain multiple nodes in the result. On Thu, Apr 22, 2010 at 10:56 AM, mitul1411 wrote: > > Hello everyone, > I am n

Re: XPath Spliiter Problem

When I do not provide any resultType (i.e. using the default one) , I get the following error. No type converter available to convert from type: com.sun.org.apache.xerces.internal.dom.DeferredElementNSImpl to the required type: java.io.InputStream with value [cone: null] The above statement is o

Re: XPath Spliiter Problem

Hi You can convert that yourself in a processor / bean // use iterator to walk the XML Iterator it = exchange.getIn().getBody(Iterator.class); while (it.hasNext()) { Object value = it.next(); String s = exchange.getContext().getTypeConverter().convertTo(String.class, value); // now add t

Re: SFTP rename problems

Great stuff Claus Will test as soon as i can, very busy here so it will probably be a few days. I'll keep you posted. Claus Ibsen-2 wrote: > > Hi > > I tacked down an issue in the camel-core > https://issues.apache.org/activemq/browse/CAMEL-2662 > > Can you try to test with latest code on yo

Re: XPath Spliiter Problem

I used file output for testing the values. My requirement is that I have to send the values from the nodes to the CXF endpoint. Adding a bean would mean an overhead to the route. I need your suggestions on it. Claus Ibsen-2 wrote: > > Hi > > You can convert that yourself in a processor / bean

Re: Is this a bug of try-catch or transaction?

Thanks willem: It seems that the onException has a little different difference to try-catch; That's : try-catch could recover the exception and continue to execute next processor in pipeline But on-Exception always stop execute when exception occurs in pipeline I am not very sure about this(Bu

Re: XPath Spliiter Problem

On Thu, Apr 22, 2010 at 12:00 PM, mitul1411 wrote: > > I used file  output for testing the values. > My requirement is that I have to send the values from the nodes to the CXF > endpoint. > Adding a bean would mean an overhead to the route. > I need your suggestions on it. > There is not much ove

Re: does camel support custom policy for processor level ?

Hi I am opening up this in Camel 2.3.0 so you can use Policy at per processor level. I have created a ticket to track it https://issues.apache.org/activemq/browse/CAMEL-2667 On Thu, Apr 22, 2010 at 9:45 AM, ext2 wrote: > > > Thanks Willem: > > You are right; >  It seems I must do something el

Re: Handle finite number of remote requests?

Hi Something similar you can do is to throttle intaking messages according to some metrics, such as the rate of speed that external server can handle. Check out RoutePolicy http://camel.apache.org/routepolicy.html On Wed, Apr 21, 2010 at 10:19 PM, dnn wrote: > > My application will send reques

Re: Split Body in Spring DSL

On Wed, Apr 21, 2010 at 9:23 PM, Olivier Roger wrote: > > I understand the better now, > > Anyways, this would really be a useful features in our case :) > I have fixed the body and ${body} now returning the same = the body instance as it is. > > Claus Ibsen-2 wrote: >> >> Hi >> >> Yeah I can se

Re: Split Body in Spring DSL

That's great news. Thanks! Using body is also working like you indicated ;) Olivier Claus Ibsen-2 wrote: > > On Wed, Apr 21, 2010 at 9:23 PM, Olivier Roger > wrote: >> >> I understand the better now, >> >> Anyways, this would really be a useful features in our case :) >> > > I have fixed

camel-mina and multicast

The camel-mina wiki web page mentions that we can configure the camel-mina endpoint with multicast protocol (mina:multicast://hostname[:port][?options] ) but the faq of apache Mina web site says that this is not possible : Does MINA support multicast? Not yet. Java NIO doesn't support multicast y

Re: camel-mina and multicast

Hi There is no multicast in camel-mina so the wiki page should be fixed. On Thu, Apr 22, 2010 at 2:40 PM, Charles Moulliard wrote: > The camel-mina wiki web page mentions that we can configure the > camel-mina endpoint with multicast protocol > (mina:multicast://hostname[:port][?options] > ) bu

Re: camel-mina and multicast

I update the page. Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel Committer *** - Blog : http://cmoulliard.blogspot.com - Twitter : http://twitter.com/cmoulliard - Linkedlin : http://www.linkedin.com/in

How to test

Dear All I want to create a component which also use its own uri. How to unit test the component? I see nothing about testing components (e.g. camel-mina) in the source apache-camel-2.2.0-src.tar.gz -- ~The best men are men who benefit to others http://michsan.web.id

Re: How to test

Hi I dont tink the tar have the -test source code. You can view that online at https://svn.apache.org/repos/asf/camel/trunk/components/camel-mina/src/test/ On Thu, Apr 22, 2010 at 3:05 PM, Muhammad Ichsan wrote: > Dear All > > I want to create a component which also use its own uri. How to uni

Typo in docs

Hi all, there is a typo in the docs: ${file:name.ext}. must be .${file:ext}. It's located here: http://camel.apache.org/file2.html About moveFailed The moveFailed option allows you to move files that could not be processed succesfully to another location such as a error folder of your choice.

Re: Velocity component

I could indeed unmarshal using JAXB but I would like to use as less Java as possible. I am facing an other problem now: When I extract the value using XPath like this: /ns1:person/ns1:firstName/text() and use it in the velocity template with: Hello ${headers.firstname} It produce this kind of

Re: Velocity component

On Thu, Apr 22, 2010 at 3:59 PM, Olivier Roger wrote: > > I could indeed unmarshal using JAXB but I would like to use as less Java as > possible. > > I am facing an other problem now: > When I extract the value using XPath like this: > > headerName="firstname">/ns1:person/ns1:firstName/text() > >

Re: Handle finite number of remote requests?

That's pretty close to what I want to do, but the ThrottlingInflightRoutePolicy appears to throttle at the end of the route (or so it seems from the 'onExchangeDone' method). I think I could make it work by writing my own policy to check the DB in the 'onExchangeBegin' method. Thanks Claus! Cl

Re: Typo in docs

Hi Thanks for spotting this. Unfortunately the Apache wiki pages cannot be edited right now, that does not work currently. I will add the "name.ext" variation as well so you can use either in 2.3 onwards. On Thu, Apr 22, 2010 at 3:31 PM, Malte Hübner wrote: > > Hi all, > > there is a typo in

camel-mina and objects

Hi, I send an object through a camel-mina endpoint to a mina server. When the server receives the object, mina generates the following error : [pache.camel.spring.Main.main()] DefaultCamelContextINFO Apache Camel 2.2.0 (CamelContext:camelContext) started 23781 [Camel thread 2: MinaThr

Re: camel-mina and objects

I have found the solution. This paramete rmust be set to true : allowDefaultCodec=true Kind regards, Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel Committer *** - Blog : http://cmoulliard.blogspot.c

Mina or other transport - would like blocking

I'm not sure if I'm going to explain this well but let me try: We have 1000's of messages we want to send to a remote process.These messages are really 1 way only as the response comes back only for some of them when a message comes in. However because there is some timing related issues sur

Re: Remote broker message behavior

Sure, here is the route: from("servlet:///data-in").convertBodyTo(String.class) .to("validator:schema-file.xsd") .inOnly("jms:queue:inbound") .choice() .when().xpath("/a:data/a:dataLog1", ns) .unmarshal(jaxbDf) .beanRef("data

Re: How to test

I checked the apache-camel-2.3.0-SNAPSHOT-src.tar.gz and the apache-camel-2.2.0-src.tar.gz The camel-mina unit test files are in the director of "components/camel-mina/src/test/" Willem Claus Ibsen wrote: Hi I dont tink the tar have the -test source code. You can view that online at https:

Re: How to test

On Thu, Apr 22, 2010 at 8:24 PM, Claus Ibsen wrote: > Hi > > I dont tink the tar have the -test source code. > > You can view that online at > > https://svn.apache.org/repos/asf/camel/trunk/components/camel-mina/src/test/ > Thanks, this URL is enough for me. But the test class needs some modific

Re: How to test

Muhammad Ichsan wrote: On Thu, Apr 22, 2010 at 8:24 PM, Claus Ibsen wrote: Hi I dont tink the tar have the -test source code. You can view that online at https://svn.apache.org/repos/asf/camel/trunk/components/camel-mina/src/test/ Thanks, this URL is enough for me. But the test class ne

Re: camel-mina and objects

On Thu, Apr 22, 2010 at 5:22 PM, Charles Moulliard wrote: > I have found the solution. > > This paramete rmust be set to true : > > allowDefaultCodec=true > Where do you set this option? Can you post the mina endpoint uri you use? In fact I didn't know such an option existed. Maybe we need to add

Re: camel-mina and objects

Here is the uri used : This is defined in the wiki page of camel-mina ;-) Kind regards, Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel Committer *** - Blog : http://cmoulliard.blogspot.com - Twitter