date:20110902

Re: Karaf 2.2.3 and Camel 2.8.0

2011-09-02 Thread Jean-Baptiste Onofré

Let me test it because I checked in the Camel features descriptor, and 
Camel uses version range for features like spring.


I make a try and keep you posted.

Regards
JB

On 09/02/2011 10:50 PM, mgardiner wrote:

I have recently tried using Karaf 2.2.3 which has just updated to use Spring
3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0 because
two versions of spring are available.  With a new camel release underway are
you considering upgrading camel to spring 3.0.6.RELEASE?

Thanks.

Here's the output

Error executing command: Could not start bundle
mvn:org.apache.camel/camel-jms/2.8.0 in feature(s) camel-jms-2.8.0: Unable
to resolve module org.apache.camel.camel-jms [88.0] because it is exposed to
package 'org.springframework.util' from org.springframework.core [82.0] and
org.springframework.core [43.0] via two dependency chains.

Chain 1:
   org.apache.camel.camel-jms [88.0]
 import:
(&(package=org.springframework.util)(version>=3.0.0)(!(version>=4.0.0)))
  |
 export: package=org.springframework.util
   org.springframework.core [82.0]

Chain 2:
   org.apache.camel.camel-jms [88.0]
 import:
(&(package=org.apache.camel.impl)(version>=2.8.0)(!(version>=2.9.0)))
  |
 export: package=org.apache.camel.impl;
uses:=org.springframework.jmx.export.annotation
   org.apache.camel.camel-core [80.0]
 import:
(&(package=org.springframework.jmx.export.annotation)(version>=3.0.0)(!(version>=4.0.0)))
  |
 export: package=org.springframework.jmx.export.annotation;
uses:=org.springframework.aop.target
   org.springframework.context [48.0]
 import:
(&(package=org.springframework.aop.target)(version>=3.0.6)(!(version>=3.0.7)))
  |
 export: package=org.springframework.aop.target;
uses:=org.springframework.core
   org.springframework.aop [47.0]
 import:
(&(package=org.springframework.core)(version>=3.0.6)(!(version>=3.0.7)))
  |
 export: package=org.springframework.core; uses:=org.springframework.util
 export: package=org.springframework.util
   org.springframework.core [43.0]




--
View this message in context: 
http://camel.465427.n5.nabble.com/Karaf-2-2-3-and-Camel-2-8-0-tp4763828p4763828.html
Sent from the Camel - Users mailing list archive at Nabble.com.


--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Camel 2.2 Removal of Endpoint Files

2011-09-02 Thread Craig Taylor

I resolved this issue by dynamically creating a RouteBuilder,  then removing
the route after a small period of time had passed (in my case, it should be
safe to do).

However, one of the other thoughts that had occurred to me afterwards is
that camel may be maintaining a list of exchanges internally that have yet
to be considered "complete".  If I had used a producer template to send the
returned exchange to, a eg: "log:blah" would the delete processing of the
file endpoint have occurred?

On Fri, Sep 2, 2011 at 3:34 PM, Craig Taylor  wrote:

> From a file based endpoint (eg: file, ftp, sftp) uri I'm attempting to
> remove files via the following:
>
> public void removeFilesFromUri( ConsumerTemplate consumerTempl,
> CamelContext camlContext, String uri )
> {
> uri = uri + "&delete=true";
>
> consumerTempl.start();
>
> Exchange exc = consumerTempl.receive(uri,1);
> while( exc != null )
> {
> System.err.println( "Deleting:" +
> exc.getIn().getHeader(Exchange.FILE_NAME) );
>
> // Receive and toss...
> exc = consumerTempl.receive(uri,1);
> }
> consumerTempl.stop();
> camlContext.removeEndpoints(uri);
> }
>
> The files are not deleted.  I am able to see the "Deleting: " println
> entries for the affected endpoint files.  I had expected that the act of
> receiving an exchange would generate the deletion of them.
>
> Is there anything I need to do to indicate to camel that I'm finished with
> the exchange and it's safe for it to remove the file?  In other posts I've
> seen references to :
> exc.getUnitOfWork().done(exc) however, in the code above getUnitOfWork()
> returns null.
>
> This is in Camel 2.2 btw (I know... I know... )
>
> Thanks,
>
> --
> ---
> Craig Taylor
> ctalk...@ctalkobt.net
>
>

-- 
---
Craig Taylor
ctalk...@ctalkobt.net

Re: Karaf 2.2.3 and Camel 2.8.0

2011-09-02 Thread David Karlsen

2.9.0 could maybe aim for Spring 3.1 if it's out soon enough?

2011/9/3 Freeman Fang 

> Hi,
>
> Per the discussion on this forum before, camel 2.8.1 won't upgrade to
> spring 3.0.6(as it's a minor version fix release and need backward
> compatible), but camel 2.9.0 definitely will use new spring version.
>
> Freeman
> On 2011-9-3, at 上午4:50, mgardiner wrote:
>
>  I have recently tried using Karaf 2.2.3 which has just updated to use
>> Spring
>> 3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0 because
>> two versions of spring are available.  With a new camel release underway
>> are
>> you considering upgrading camel to spring 3.0.6.RELEASE?
>>
>> Thanks.
>>
>> Here's the output
>>
>> Error executing command: Could not start bundle
>> mvn:org.apache.camel/camel-**jms/2.8.0 in feature(s) camel-jms-2.8.0:
>> Unable
>> to resolve module org.apache.camel.camel-jms [88.0] because it is exposed
>> to
>> package 'org.springframework.util' from org.springframework.core [82.0]
>> and
>> org.springframework.core [43.0] via two dependency chains.
>>
>> Chain 1:
>>  org.apache.camel.camel-jms [88.0]
>>   import:
>> (&(package=org.**springframework.util)(version>**
>> =3.0.0)(!(version>=4.0.0)))
>>|
>>   export: package=org.springframework.**util
>>  org.springframework.core [82.0]
>>
>> Chain 2:
>>  org.apache.camel.camel-jms [88.0]
>>   import:
>> (&(package=org.apache.camel.**impl)(version>=2.8.0)(!(**version>=2.9.0)))
>>|
>>   export: package=org.apache.camel.impl;
>> uses:=org.springframework.jmx.**export.annotation
>>  org.apache.camel.camel-core [80.0]
>>   import:
>> (&(package=org.**springframework.jmx.export.**
>> annotation)(version>=3.0.0)(!(**version>=4.0.0)))
>>|
>>   export: package=org.springframework.**jmx.export.annotation;
>> uses:=org.springframework.aop.**target
>>  org.springframework.context [48.0]
>>   import:
>> (&(package=org.**springframework.aop.target)(**
>> version>=3.0.6)(!(version>=3.**0.7)))
>>|
>>   export: package=org.springframework.**aop.target;
>> uses:=org.springframework.core
>>  org.springframework.aop [47.0]
>>   import:
>> (&(package=org.**springframework.core)(version>**
>> =3.0.6)(!(version>=3.0.7)))
>>|
>>   export: package=org.springframework.**core;
>> uses:=org.springframework.util
>>   export: package=org.springframework.**util
>>  org.springframework.core [43.0]
>>
>>
>>
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.**
>> com/Karaf-2-2-3-and-Camel-2-8-**0-tp4763828p4763828.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
> --**---
> Freeman Fang
>
> FuseSource
> Email:ff...@fusesource.com
> Web: fusesource.com
> Twitter: freemanfang
> Blog: http://freemanfang.blogspot.**com 
>
>
>
>
>
>
>
>
>
>


-- 
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

Re: Karaf 2.2.3 and Camel 2.8.0

2011-09-02 Thread Freeman Fang


Hi,

Per the discussion on this forum before, camel 2.8.1 won't upgrade to  
spring 3.0.6(as it's a minor version fix release and need backward  
compatible), but camel 2.9.0 definitely will use new spring version.


Freeman
On 2011-9-3, at 上午4:50, mgardiner wrote:

I have recently tried using Karaf 2.2.3 which has just updated to  
use Spring
3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0  
because
two versions of spring are available.  With a new camel release  
underway are

you considering upgrading camel to spring 3.0.6.RELEASE?

Thanks.

Here's the output

Error executing command: Could not start bundle
mvn:org.apache.camel/camel-jms/2.8.0 in feature(s) camel-jms-2.8.0:  
Unable
to resolve module org.apache.camel.camel-jms [88.0] because it is  
exposed to
package 'org.springframework.util' from org.springframework.core  
[82.0] and

org.springframework.core [43.0] via two dependency chains.

Chain 1:
 org.apache.camel.camel-jms [88.0]
   import:
(&(package=org.springframework.util)(version>=3.0.0)(! 
(version>=4.0.0)))

|
   export: package=org.springframework.util
 org.springframework.core [82.0]

Chain 2:
 org.apache.camel.camel-jms [88.0]
   import:
(&(package=org.apache.camel.impl)(version>=2.8.0)(!(version>=2.9.0)))
|
   export: package=org.apache.camel.impl;
uses:=org.springframework.jmx.export.annotation
 org.apache.camel.camel-core [80.0]
   import:
(&(package=org.springframework.jmx.export.annotation)(version>=3.0.0) 
(!(version>=4.0.0)))

|
   export: package=org.springframework.jmx.export.annotation;
uses:=org.springframework.aop.target
 org.springframework.context [48.0]
   import:
(&(package=org.springframework.aop.target)(version>=3.0.6)(! 
(version>=3.0.7)))

|
   export: package=org.springframework.aop.target;
uses:=org.springframework.core
 org.springframework.aop [47.0]
   import:
(&(package=org.springframework.core)(version>=3.0.6)(! 
(version>=3.0.7)))

|
   export: package=org.springframework.core;  
uses:=org.springframework.util

   export: package=org.springframework.util
 org.springframework.core [43.0]




--
View this message in context: 
http://camel.465427.n5.nabble.com/Karaf-2-2-3-and-Camel-2-8-0-tp4763828p4763828.html
Sent from the Camel - Users mailing list archive at Nabble.com.


-
Freeman Fang

FuseSource
Email:ff...@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com

Re: Set response by a second route through "direct" routing?

2011-09-02 Thread boday

Martin, this should work...just make sure you are setting the OUT message on
the exchange (exchange.getOut().setBody("RESPONSE"), etc)...


heinrichheine wrote:
> 
> Hi,
> to make my route nicer i created a splitter in my incoming http route.
> Depending of the content i route the request to different routes via
> direct.
> The thing is, that i have to create the response for the http-request in
> my first route. But i want to create a response from within my directed
> routes. Is this possible?
> 
> Example
> 
> from("jetty://http://127.0.0.1:1234/";)
>  .choice()
>   .when().xpath(expression1)
>   .to("direct:goodRoute")
>   .when().xpath("expression2)
>   .to("direct:badRoute");
> 
> So, i want to create the response for the http request in goodRoute and
> badRoute. But in real life, the response is just empty if i do so. Do i
> have to add an option to the direct route?
> 
> Thanks
>  martin
> 


-
Ben O'Day
IT Consultant -http://consulting-notes.com

--
View this message in context: 
http://camel.465427.n5.nabble.com/Set-response-by-a-second-route-through-direct-routing-tp4761827p4763955.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Karaf 2.2.3 and Camel 2.8.0

2011-09-02 Thread mgardiner

I have recently tried using Karaf 2.2.3 which has just updated to use Spring
3.0.6.RELEASE and we are now getting conflicts in camel-jms 2.8.0 because
two versions of spring are available.  With a new camel release underway are
you considering upgrading camel to spring 3.0.6.RELEASE?

Thanks.

Here's the output

Error executing command: Could not start bundle
mvn:org.apache.camel/camel-jms/2.8.0 in feature(s) camel-jms-2.8.0: Unable
to resolve module org.apache.camel.camel-jms [88.0] because it is exposed to
package 'org.springframework.util' from org.springframework.core [82.0] and
org.springframework.core [43.0] via two dependency chains.

Chain 1:
  org.apache.camel.camel-jms [88.0]
import:
(&(package=org.springframework.util)(version>=3.0.0)(!(version>=4.0.0)))
 |
export: package=org.springframework.util
  org.springframework.core [82.0]

Chain 2:
  org.apache.camel.camel-jms [88.0]
import:
(&(package=org.apache.camel.impl)(version>=2.8.0)(!(version>=2.9.0)))
 |
export: package=org.apache.camel.impl;
uses:=org.springframework.jmx.export.annotation
  org.apache.camel.camel-core [80.0]
import:
(&(package=org.springframework.jmx.export.annotation)(version>=3.0.0)(!(version>=4.0.0)))
 |
export: package=org.springframework.jmx.export.annotation;
uses:=org.springframework.aop.target
  org.springframework.context [48.0]
import:
(&(package=org.springframework.aop.target)(version>=3.0.6)(!(version>=3.0.7)))
 |
export: package=org.springframework.aop.target;
uses:=org.springframework.core
  org.springframework.aop [47.0]
import:
(&(package=org.springframework.core)(version>=3.0.6)(!(version>=3.0.7)))
 |
export: package=org.springframework.core; uses:=org.springframework.util
export: package=org.springframework.util
  org.springframework.core [43.0]




--
View this message in context: 
http://camel.465427.n5.nabble.com/Karaf-2-2-3-and-Camel-2-8-0-tp4763828p4763828.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Camel 2.2 Removal of Endpoint Files

2011-09-02 Thread Craig Taylor

>From a file based endpoint (eg: file, ftp, sftp) uri I'm attempting to
remove files via the following:

public void removeFilesFromUri( ConsumerTemplate consumerTempl, CamelContext
camlContext, String uri )
{
uri = uri + "&delete=true";

consumerTempl.start();

Exchange exc = consumerTempl.receive(uri,1);
while( exc != null )
{
System.err.println( "Deleting:" +
exc.getIn().getHeader(Exchange.FILE_NAME) );

// Receive and toss...
exc = consumerTempl.receive(uri,1);
}
consumerTempl.stop();
camlContext.removeEndpoints(uri);
}

The files are not deleted.  I am able to see the "Deleting: " println
entries for the affected endpoint files.  I had expected that the act of
receiving an exchange would generate the deletion of them.

Is there anything I need to do to indicate to camel that I'm finished with
the exchange and it's safe for it to remove the file?  In other posts I've
seen references to :
exc.getUnitOfWork().done(exc) however, in the code above getUnitOfWork()
returns null.

This is in Camel 2.2 btw (I know... I know... )

Thanks,

-- 
---
Craig Taylor
ctalk...@ctalkobt.net

Netty with syslog decoder

2011-09-02 Thread trivedikumarb

Hi All,

I am trying to expose TCP endpoint using Netty
[from('netty:tcp://localhost:12346?sync=false&allowDefaultCodec=false&encoding=UTF-8&disconnect=true')],
from the client I am sending a big syslog message. At the server side, I am
receiving the message as chunks instead of full byte[] or string. Can
someone help me or guide me on how to write decoder to handle this?

Thanks,
Trivedi

--
View this message in context: 
http://camel.465427.n5.nabble.com/Netty-with-syslog-decoder-tp4763467p4763467.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Errors with SFTP producer and large files

2011-09-02 Thread Claus Ibsen

Thanks Mike for the details report. I have marked this conversation to
get back to it.
Its a bit odd as writing a file ought to be stream based and not take
up memory space.




On Thu, Sep 1, 2011 at 11:57 PM, Mike D  wrote:
> Update:
>
> I was able to workaround this problem using ylambert's approach (thank you
> sir!), however it makes me a little uneasy that the problem must be dealt
> with in such a way.  It seems to me like this is a bug in the way Camel
> handles transferring a local file to a remote system with SFTP/FTP(S).
>
> I cannot envision a case when it is appropriate to try to read the entire
> contents of a (large) file into a byte buffer in order to stream data over
> the network, and I think most people would agree this is common sense.  I
> can only conclude that this is the product of some nuance of the
> TypeConverter system that I do not understand, and that it is not really
> meant to work this way - at least not in this case.
>
> With regards to localWorkDirectory and its usefulness in the upload
> scenario, I can see that this might be helpful if I was trying to send data
> that was already memory bound and so writing out data to a local temporary
> file would help things stay within memory limits.  However, in my scenario
> the file already exists on the local disk, so I don't see how writing that
> file out to *another* file is going to help anything.
>
> I do appreciate the quick response Claus, I'm just guessing you thought I
> was dealing with the download use-case instead of the upload case.  Camel
> still rocks; I know it is hard to please everybody and there are a LOT of
> components to support.  Hopefully this thread helps anybody else who runs
> into this issue.
>
> Cheers,
> Mike
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Errors-with-SFTP-producer-and-large-files-tp4757404p4760166.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Re: Does onException not support multiple statements?

2011-09-02 Thread koseki nonuyuki


Jens wrote:
> 
> 
> Claus Ibsen-2 wrote:
>> 
>> On Thu, Sep 1, 2011 at 6:31 PM, Jens wrote:
>>> koseki nonuyuki wrote:
 I encountered the same trouble when I got SOAP fault.

 The first processor in the onException route, I put
 "exchange.getOut().setBody(null)" , then multiple
 process worked.

 When onException route received SOAP fault, the outMessage already
 contains Exception info, that
 cause another Exception at the next process and rollback, I guess.
>>>
>>> I'm doing the same thing, plus
>>>
>>>      exchange.setProperty(Exchange.EXCEPTION_CAUGHT,
>>> exchange.getOut.getBody());
>>>
>>> before that so the exception remains accessible. It seems to me that's
>>> what
>>> the onException handler should do already, though.
>>>
>> 
>> SOAP Faults is not part of the Camel error handling by default.
>> 
>> There is a handle fault (interceptor) you can enable which turns a
>> SOAP Fault -> Exception,
>> which the Camel error handler will be abel to detect and react upon.
>> 
> 
> Hi Claus,
> 
> as I wrote previously, handleFault doesn't seem to work in this case
> (Camel 2.6.0).
> 
> Regards,
> Jens
> 

Hi,

handleFault doesn't seem to work on Camel 2.7.3 either.

When I intentionally generate Exception(not SOAP fault), onException route
works fine even if there are multiple statement. 
But When I return SOAP Fault, onException route stop at the first statement
and cause  another Exception.

--
View this message in context: 
http://camel.465427.n5.nabble.com/Does-onException-not-support-multiple-statements-tp4381958p4762392.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Activemq dynamic endpoint configuration

2011-09-02 Thread Mick Knutson

I looked at that link and did not see an example of how to use the event
driven consumer. Are there any code examples?

---
Thank You…

Mick Knutson, President

BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring & Agile Consulting
p. (855) BASE-LOGIC: (227-3564-42)
p. (478) BASE-LOGIC (227-3564-42)
f. (855) BASE-LOGIC: (227-3564-42)

Website: http://www.baselogic.com
Blog: http://www.baselogic.com/blog/
Linked IN: http://linkedin.com/in/mickknutson
Twitter: http://twitter.com/mickknutson
---



On Fri, Sep 2, 2011 at 2:07 AM, Claus Ibsen  wrote:

> The configure method is called *once* when Camel bootup and create the
> runtime routes from the model (eg RouteBuilder's).
>
> The JMS consumer is an event driven consumer
> http://camel.apache.org/event-driven-consumer.html
>
>
>
>
> On Fri, Sep 2, 2011 at 1:57 AM, kal2420  wrote:
> > Ashwin,
> >
> >   Thanks, I agree this is a bad approach.  I am a bit confused about how
> > often configure() method is invoked and when the message would be read
> from
> > the queue.  For Example:
> >
> >  public class TestRouteBuilder extends RouteBuilder {
> >
> >public String current_State = "process";
> >
> >@Override
> >public void configure() throws Exception {
> >
> >  String selector = generateSelectorURI(current_state);
> >
> >from("activemq:queue:test?selector="+selector)
> >.to("log:test")
> >.process(new Processor() {
> >
> >@Override
> >public void process(Exchange
> exchange) throws Exception {
> >
> >current_State="waiting";
> >sendSoapRequest("test");
> >}
> >});
> >}
> > }
> >
> > I only want to read and process messages if current_state is “process” (
> so
> > in "waiting" state change selector value so none of the messages would be
> > read).
> >
> > What type of endpoint would camel create based on
> > “from(“activemq:queue..”)” ?  ex: polled or scheduled endpoint.
> >
> > Would the selector uri get re-created on every read? does camel just
> change
> > endpoint configuration or re-create a new endpoint ?
> >
> > If you have a good example on how to do dynamic selector with
> > camel/activemq, I would love to see it.
> >
> > I really appreciate all your help.
> >
> > Thanks
> > Kal
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/Activemq-dynamic-endpoint-configuration-tp4749853p4760387.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
> >
>
>
>
> --
> Claus Ibsen
> -
> FuseSource
> Email: cib...@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>

Re: Does onException not support multiple statements?

2011-09-02 Thread Jens


Claus Ibsen-2 wrote:
> 
> On Thu, Sep 1, 2011 at 6:31 PM, Jens wrote:
>> koseki nonuyuki wrote:
>>> I encountered the same trouble when I got SOAP fault.
>>>
>>> The first processor in the onException route, I put
>>> "exchange.getOut().setBody(null)" , then multiple
>>> process worked.
>>>
>>> When onException route received SOAP fault, the outMessage already
>>> contains Exception info, that
>>> cause another Exception at the next process and rollback, I guess.
>>
>> I'm doing the same thing, plus
>>
>>      exchange.setProperty(Exchange.EXCEPTION_CAUGHT,
>> exchange.getOut.getBody());
>>
>> before that so the exception remains accessible. It seems to me that's
>> what
>> the onException handler should do already, though.
>>
> 
> SOAP Faults is not part of the Camel error handling by default.
> 
> There is a handle fault (interceptor) you can enable which turns a
> SOAP Fault -> Exception,
> which the Camel error handler will be abel to detect and react upon.
> 

Hi Claus,

as I wrote previously, handleFault doesn't seem to work in this case (Camel
2.6.0).

Regards,
Jens

--
View this message in context: 
http://camel.465427.n5.nabble.com/Does-onException-not-support-multiple-statements-tp4381958p4762156.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Set response by a second route through "direct" routing?

2011-09-02 Thread heinrichheine

Hi,
to make my route nicer i created a splitter in my incoming http route.
Depending of the content i route the request to different routes via direct.
The thing is, that i have to create the response for the http-request in my
first route. But i want to create a response from within my directed routes.
Is this possible?

Example

from("jetty://http://127.0.0.1:1234/";)
 .choice()
  .when().xpath(expression1)
  .to("direct:goodRoute")
  .when().xpath("expression2)
  .to("direct:badRoute");

So, i want to create the response for the http request in goodRoute and
badRoute. But in real life, the response is just empty if i do so. Do i have
to add an option to the direct route?

Thanks
 martin

--
View this message in context: 
http://camel.465427.n5.nabble.com/Set-response-by-a-second-route-through-direct-routing-tp4761827p4761827.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Splitter file name automatic generation

2011-09-02 Thread kmute79

Hi Claus,


thanks for reply it was grate. I solved my problem with you help, I'm an
Apache Camel newbie.

Thanks again,

Best Regards

Matteo

--
View this message in context: 
http://camel.465427.n5.nabble.com/Splitter-file-name-automatic-generation-tp4754576p4761533.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Karaf 2.2.3 and Camel 2.8.0

Re: Camel 2.2 Removal of Endpoint Files

Re: Karaf 2.2.3 and Camel 2.8.0

Re: Karaf 2.2.3 and Camel 2.8.0

Re: Set response by a second route through "direct" routing?

Karaf 2.2.3 and Camel 2.8.0

Camel 2.2 Removal of Endpoint Files

Netty with syslog decoder

Re: Errors with SFTP producer and large files

Re: Does onException not support multiple statements?

Re: Activemq dynamic endpoint configuration

Re: Does onException not support multiple statements?

Set response by a second route through "direct" routing?

Re: Splitter file name automatic generation

14 matches

Site Navigation

Mail list logo

Footer information