1 Reply Latest reply on Aug 9, 2012 10:18 PM by Willem Jiang

    Stream inline processing, Is it possible?

    mikek753_michael.korolyov Newbie

      hi experts,

       

      I'd like to do stream inline processing as part of Camel route.

      Something like

      from("stream:secureURL").beanRef("myProcess").to("stream:anotherSecureURL");

       

      this is like a proxy to process stream.

      What isn't clear for me is how to pass stream via Exchange?

       

      Also, how to secure via SSL incoming stream EndPoint that just http and not XML / SOAP?

      lets say large text file is uploaded via https that has to be analyzed while pass through to another https endpoint.

       

      Another use case is to create Exchange messages from incoming stream - sequencer, via custom split bean with later parallel  processing.

      How to read from Exchange that incoming stream to be able read incoming in split bean instead of incoming endpoint?

      Will Exchange has ref to that incoming stream for splitter?

       

      thanks.

       

      Mike.

        • 1. Re: Stream inline processing, Is it possible?
          Willem Jiang Master
          mikek753 wrote:

          hi experts,

           

          I'd like to do stream inline processing as part of Camel route.

          Something like

          from("stream:secureURL").beanRef("myProcess").to("stream:anotherSecureURL");

           

          this is like a proxy to process stream.

          What isn't clear for me is how to pass stream via Exchange?

           

          Normally we just put the Stream into the message body.

           

          Also, how to secure via SSL incoming stream EndPoint that just http and not XML / SOAP?

           

          Camel-Jetty endpoint supports to setup the SSL connection for you.

           

          lets say large text file is uploaded via https that has to be analyzed while pass through to another https endpoint.

           

          Another use case is to create Exchange messages from incoming stream - sequencer, via custom split bean with later parallel  processing.

           

          It dependents on the Stream size and how fast you want to process it.

          If you want to process the stream concurrently, you need cache the Stream first, as the Stream is sequence naturally. And you need to find a way to aggregat these Streams when you finished the processing.

             

          How to read from Exchange that incoming stream to be able read incoming in split bean instead of incoming endpoint?

          I'm not quit understand it.

           

          Will Exchange has ref to that incoming stream for splitter?

          You can store some property in the exchange for the reference。

           

          thanks.

           

          Mike.

           

          Willem