On Thu, Nov 24, 2011 at 9:55 PM, Johan Edstrom <seij...@gmail.com> wrote: > I'll just need to get past the Turkey hibernation :) > But it would be awesome I think if we could remain in the ASF license land > with one > component, checking for which converter to use in the converters and > specifying manually > one of the two in a declared context? > > That make sense? > So we'd need an unmarshaller (which looks the same as the other one more or > less) > and a marshaller as well to spit out the message. > > And yeah, adding to the Syslog object seems a good idea to me, I do not think > there are a > ton of users of it right now but adding fields shouldn't be the end of the > world. > > Sound good? >
I like this. +1 from here. > Thanks! > > On Nov 23, 2011, at 3:33 PM, geemang wrote: > >> How would you like to proceed? >> >> It'd also be nice to handle the structured data un/marshal with a map or >> something. Perhaps a property on the SyslogMessage object? >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/syslog-RFC-5424-dataformat-component-tp5015386p5018448.html >> Sent from the Camel Development 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/
