Bought this but it's pretty shallow for a real-world example, not seeing
much I didn't learn from the web site. Adding encryption/decryption where
there already exists marshalling/un-marshalling would have been far more
meaningful.

On 24 December 2014 at 10:58, Claus Ibsen <claus.ib...@gmail.com> wrote:

> Scott and Jakubs book has an excellent chapter about security where
> they cover this
>
> https://www.packtpub.com/application-development/apache-camel-developers-cookbook
>
> On Wed, Dec 24, 2014 at 11:29 AM, James Green <james.mk.gr...@gmail.com>
> wrote:
> > So something like:
> >
> >
> from("the.input.queue").unmarshal(cryptoDataFormat).unmarshal(jaxbMapper).process(byBusinessProcessor).marshal(cryptoDataFormat).to("the.output.queue")
> > ?
> >
> > Not entirely convinced I have this mentally modelled yet...
> >
> > On 24 December 2014 at 10:22, David Karlsen <davidkarl...@gmail.com>
> wrote:
> >
> >> Sure! The crypto is agnostic of transport and payload - stick it in
> between
> >> the marshalling and the endpoint - and inbetween endpoint and
> unmarshalling
> >> and you should be fit for fight.
> >> Good luck!
> >>
> >> 2014-12-24 11:17 GMT+01:00 James Green <james.mk.gr...@gmail.com>:
> >> >
> >> > I'm looking at Camel's CryptoDataFormat and am wondering to what
> extent
> >> we
> >> > might employ it.
> >> >
> >> > In our use-case we want multiple Camel-powered JARs to send each other
> >> > messages via a message broker. Some of message needs to remain
> private so
> >> > cryptography needs to be used. Right now we have routes that produce
> and
> >> > consume from brokers and use jaxb classes for mapping to/from POJOs.
> >> >
> >> > http://camel.apache.org/crypto.html Does not really deal with
> anything
> >> > realistic - only mock endpoints. Can this be put into the above
> >> > applications?
> >> >
> >> > Thanks,
> >> >
> >> > James
> >> >
> >>
> >>
> >> --
> >> --
> >> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
> >>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cib...@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> hawtio: http://hawt.io/
> fabric8: http://fabric8.io/
>

Reply via email to