Re: sharing exchange properties in mutlicast route

2022-02-25 Thread Rohan Emmanuel
Thank you Claus so much for your quick reply.Much appreciated.

On Fri, 25 Feb 2022, 7:57 pm Claus Ibsen,  wrote:

> Hi
>
> That is not possible as the design when using multicast is that the
> exchange are independent.
> If you need to share some data then use an external shared bean you
> can access from the multicased sub routes.
>
>
> On Fri, Feb 25, 2022 at 1:26 PM Rohan Emmanuel
>  wrote:
> >
> > Hi ,
> >   I am using multicast in my route like mentioned below.
> > i am setting a property in one of these routes with id route2, which i
> want
> > to access in the multicast route1. i see that the exchange property is
> null
> > in the route1.
> >   can you please let me know how can i achieve this?
> >
> >
> >
> >  
> > 
> >
> > 
> >
> > 
> > 
> > 
> >
> >
> > 
> > 
> > 
> > hello
> > 
> > 
> >
> >
> > 
> > 
> > 
> >
> > --
> > Regards,
> > Rohan Emmanuel
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


RE: How Camel consumes files using multithreading

2022-02-25 Thread Chirag
Were you able to solve this?

why would threads in SEDA itself not work?

On 2021/10/25 06:07:47 "robbenp...@foxmail.com" wrote:
> Dear all,
>  I am using Apache Camel to handle files from SFTP. Becausethere are too 
> many file in the same directoty, I want to use multithreading to handle these 
> files.

>
> Hera is my code.
> from("sftp://${sftp.username}:${sftp.password}@${sftp.host}:${sftp.port}/myDirectory?;
>  +
> 
> "readLock=changed=10s=true=finish/$simple{date:now:MMdd}/$simple{file:onlyname}"
>  +

> 
> "=failed/$simple{date:now:MMdd}/$simple{file:onlyname}")
> .to("seda:img");
>
> from("seda:img")
> .threads(5,20)
> .keepAliveTime(20)
> .process(parseTypeProcessor)
> .process(uploadToOSSProcessor)
> .process(saveImgProcessor)
> .end();
> But it does not work.
>
> Is there any way to use multithreading  in Apache Camel?
>
> Any help or information that you can provide will be greatly appreciated.
>
> Sincerely,
> Robben
>
>
> robbenp...@foxmail.com
>


Re: camel-jetty and access log

2022-02-25 Thread Claus Ibsen
Hi

I would look at the Jetty docs to see what logging they have and see
how to setup that on Jetty.
Then we can see how to do this in camel-jetty afterwards.



On Fri, Feb 25, 2022 at 2:14 PM Daniel Johansson  wrote:
>
> Hi
>
> We use camel version 2.23.2 and spring-boot version 2.3.12.
>
> We can log get access logs for Spring Boot Web Server according to:
> https://docs.spring.io/spring-boot/docs/2.3.x/reference/html/howto.html#howto-configure-accesslogs
> 
> (and also
> https://howtodoinjava.com/spring-boot2/logging/embedded-server-logging-config/
> )
>
>
> How do we get access logs for Camel REST APIs when using camel-jetty, i.e.
>
>
>  org.apache.camel
> camel-jetty 
>
> BR
>
> /Daniel



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2


Re: sharing exchange properties in mutlicast route

2022-02-25 Thread Claus Ibsen
Hi

That is not possible as the design when using multicast is that the
exchange are independent.
If you need to share some data then use an external shared bean you
can access from the multicased sub routes.


On Fri, Feb 25, 2022 at 1:26 PM Rohan Emmanuel
 wrote:
>
> Hi ,
>   I am using multicast in my route like mentioned below.
> i am setting a property in one of these routes with id route2, which i want
> to access in the multicast route1. i see that the exchange property is null
> in the route1.
>   can you please let me know how can i achieve this?
>
>
>
>  
> 
>
> 
>
> 
> 
> 
>
>
> 
> 
> 
> hello
> 
> 
>
>
> 
> 
> 
>
> --
> Regards,
> Rohan Emmanuel



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2


camel-jetty and access log

2022-02-25 Thread Daniel Johansson
Hi

We use camel version 2.23.2 and spring-boot version 2.3.12.

We can log get access logs for Spring Boot Web Server according to:
https://docs.spring.io/spring-boot/docs/2.3.x/reference/html/howto.html#howto-configure-accesslogs

(and also
https://howtodoinjava.com/spring-boot2/logging/embedded-server-logging-config/
)


How do we get access logs for Camel REST APIs when using camel-jetty, i.e.


 org.apache.camel
camel-jetty 

BR

/Daniel


sharing exchange properties in mutlicast route

2022-02-25 Thread Rohan Emmanuel
Hi ,
  I am using multicast in my route like mentioned below.
i am setting a property in one of these routes with id route2, which i want
to access in the multicast route1. i see that the exchange property is null
in the route1.
  can you please let me know how can i achieve this?



 












hello








-- 
Regards,
Rohan Emmanuel


Re: EXT:Re: A change in the website search - looking for feedback

2022-02-25 Thread Zoran Regvart
Hi Frank,

On Fri, Feb 25, 2022 at 8:57 AM Zinner, Frank Uwe Alfred
 wrote:
>
> Hi I tried searching the documentation of components and got an error page.
>
> URI: https://pr-724--camel.netlify.app/components/latest/
>
> Error-Page Content:
>
> "This file exists solely to defeat the limitations of the link checker, that 
> is unaware of the .htaccess redirect from this page to the latest released 
> version.
> If you see this, you are not viewing the site through httpd or there is 
> something wrong with the .htaccess file: in the latter case please let the 
> camel developers know."

Thank you for the feedback. What you're seeing is a placeholder file
that we need to have in place in order for the link checker not to
report issues with missing `index.html` in the `.../latest/` path. On
the production website we're running Apache HTTPD and we have a
redirect rules that redirect from `.../latest/` to the latest release
version (right now 3.15.x), so the url changes from `.../latest/` to
`.../3.15.x/`.

These rules are Apache HTTPD-specific, so the preview websites and the
local previews do not support them.

There should not be any change to the inline search of the component
list which is not performed using Algolia. I should have been a bit
clearer in the original email, the search I'm referring to is the
search in the top right of every page that searches the whole website.

Anyways, thank you for your feedback and willingness to help :)

zoran
-- 
Zoran Regvart


Re: A change in the website search - looking for feedback

2022-02-25 Thread Zoran Regvart
Hi Claus,

On Thu, Feb 24, 2022 at 7:10 PM Claus Ibsen  wrote:
> One feedback that I think we may consider is that Camel users would
> usually use a runtime such as Spring Boot, Quarkus or Camel K etc and
> then prefer if the search would be aware of this
> and filter the search to be only about that scope. The core camel
> project should be included as it is for all of Camel.

Thanks for the feedback. This would be a new feature that we would
need to implement and is orthogonal to the current crawling/indexing
change that I'm asking folk to provide feedback.

The support for faceted search is available with Algolia Crawler
change there would not be difficult to make. The UI for search we
currently use is custom-developed for the Camel website, as there were
issues with early version of Algolia-provided UIs which make users
download two orders of magnitude more JavaScript/CSS than the version
we built. The Algolia-provided UIs for search have components for
faceted search which we could take advantage of. Changing that to the
new v4 version of Algolia UI would be a larger task IMO.

zoran
-- 
Zoran Regvart