I don't mean using it. I mean borrowing the patterns it uses architecturally. Though I might be thinking a bit too high level here to be really useful.
So basically, we've got Appenders, Filters, Layouts (and patterns), StrLookups, and ContextSelectors. Using Camel/EIP vocab, that gives us message consumers (for log events), message filters, content filters, unknown (templates aren't a thing in Camel; I guess that's business logic), and class loading stuff. Are you suggesting the other side of an endpoint for consuming foreign log messages? This would be an interesting use case that could help abstract the logging system bridges as well. On 25 March 2014 21:24, Gary Gregory <[email protected]> wrote: > OK, I think Camel is higher level than our low-level net bits. > > Gary > > > On Tue, Mar 25, 2014 at 10:20 PM, Matt Sicker <[email protected]> wrote: > >> Using routes, consumers, producers, processors, endpoints, etc. All >> enterprise integration pattern sort of things. Somewhat similar to how >> Flume works, really. >> >> >> On 25 March 2014 21:14, Gary Gregory <[email protected]> wrote: >> >>> On Tue, Mar 25, 2014 at 9:38 PM, Matt Sicker <[email protected]> wrote: >>> >>>> I've been reading up on Camel lately. Maybe we could adopt some >>>> conventions from there? >>>> >>> >>> Please explain. >>> >>> Gary >>> >>> >>>> >>>> >>>> On 25 March 2014 10:29, Ralph Goers <[email protected]> wrote: >>>> >>>>> We have JMS receivers and a SocketServer. I would expect that the >>>>> XMLSocketReceiver is expecting log events in XML format? If so, it would >>>>> seem that extending SocketServer to do that wouldn’t be very hard. >>>>> >>>>> Ralph >>>>> >>>>> >>>>> >>>>> On Mar 25, 2014, at 6:51 AM, Scott Deboy <[email protected]> >>>>> wrote: >>>>> >>>>> We need to add receivers to log4j2 :) >>>>> >>>>> Dcott >>>>> On Mar 25, 2014 5:19 AM, "Gary Gregory" <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi All: >>>>>> >>>>>> Our server uses v1's org.apache.log4j.net.XMLSocketReceiver. >>>>>> >>>>>> I do not see a v2 equivalent. >>>>>> >>>>>> Thoughts? >>>>>> >>>>>> Gary >>>>>> >>>>>> -- >>>>>> E-Mail: [email protected] | [email protected] >>>>>> Java Persistence with Hibernate, Second >>>>>> Edition<http://www.manning.com/bauer3/> >>>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >>>>>> Spring Batch in Action <http://www.manning.com/templier/> >>>>>> Blog: http://garygregory.wordpress.com >>>>>> Home: http://garygregory.com/ >>>>>> Tweet! http://twitter.com/GaryGregory >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Matt Sicker <[email protected]> >>>> >>> >>> >>> >>> -- >>> E-Mail: [email protected] | [email protected] >>> Java Persistence with Hibernate, Second >>> Edition<http://www.manning.com/bauer3/> >>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >>> Spring Batch in Action <http://www.manning.com/templier/> >>> Blog: http://garygregory.wordpress.com >>> Home: http://garygregory.com/ >>> Tweet! http://twitter.com/GaryGregory >>> >> >> >> >> -- >> Matt Sicker <[email protected]> >> > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second > Edition<http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > -- Matt Sicker <[email protected]>
