On Sat, Feb 1, 2014 at 9:40 PM, Remko Popma <remko.po...@gmail.com> wrote:
> Well done guys! > +1 G > > On Sunday, February 2, 2014, Nick Williams <nicho...@nicholaswilliams.net> > wrote: > >> Matt and I coordinated off-list today and got our presentation proposals >> submitted to ApacheCon. Assuming they're all accepted, Log4j will have four >> presentations representing it. Go us! >> >> Nick >> >> >> On Jan 31, 2014, at 11:25 PM, Nick Williams wrote: >> >> > Matt, sorry for the delay. I've had a bad cold today. Ick. Anyway, my >> proposals are below. I haven't submitted them yet. Haven't seen your >> proposals yet--can you get them to me ASAP? If you decide you're >> uncomfortable committing to two presentations, I'm prepared to also take on >> "Extending Log4j 2: Writing Custom Appenders, Filters, and Layouts" and >> leave you to deal with just the first/intro one. I've been using the >> following guidelines from the ApacheCon website: >> > >> >> • Choose a submission type (Presentation, Panel, BoFs, Tutorial) >> >> • Choose the category for your proposal (Developer, Operations, >> Business/Legal, Wildcard) >> >> • Provide a biography, including your previous speaking >> experience (900 characters maximum). >> >> • Provide us with an abstract about what you will be presenting >> at the event (900 characters maximum). >> >> • Describe who the audience is and what you expect them to gain >> from your presentation (900 characters maximum). >> >> • Tell us how the content of your presentation will help better >> the Apache and open source ecosystem. (900 characters maximum). >> >> • Select the experience level (Beginner, Intermediate, Advanced, >> Any). >> >> • List any technical requirements that you have for your >> presentation over and above the standard projector, screen and wireless >> Internet. >> > >> > ------- >> > Title: Log4j 2 in Web Applications: A Deeper Look at Effective Java EE >> Logging >> > Experience: Intermediate >> > >> > Abstract: The newly-released Log4j 2 includes much greater support than >> previous versions for Java EE web applications and proper initialization >> and deinitialization of the framework with the application lifecycle. The >> Servlet and JSP specifications have changed significantly in the 12 years >> since Log4j 1.2 first released. Some of those changes make logging easier, >> and some of them make it harder. In this presentation you will learn about >> properly configuring Log4j in a web application, what to do when the >> container is using Log4j, how to log within your JSPs using the Log4j tag >> library, and what to do when handling requests asynchronously. >> > >> > Audience Gain: The audience will gain a better understanding of the >> lifecycle and class loader hierarchy of Java EE web applications and how >> they affect the lifecycle and configuration of Log4j. They'll take a look >> at some of the different ways to initialize and configure Log4j and learn >> when each approach is appropriate and--more importantly--when it's not. >> They'll explore some of the pitfalls of asynchronous request handling and >> learn about the important tools that Log4j provides to help and the steps >> they must take to keep logging working. Finally, they'll see that logging >> in JSPs is easy, too, and doesn't require a single line of Java code. >> > >> > Benefit: This is one in a series of hopefully four different >> presentations on Log4j lead by the Apache Logging community. These >> presentations will benefit the community by providing exposure for the new >> version of Log4j, explaining its benefits and strengths over other >> frameworks, and encouraging Log4j users to improve the framework and >> contribute those improvements back to the community. I am submitting two >> presentations and Matt Sicker is submitting the other two. For the most >> part their order doesn't matter, but Matt's "An Intro to Log4j 2.0: A New >> Generation of Apache Logging" should happen earlier on the schedule than >> the other three. >> > ------- >> > >> > ------- >> > Title: Logging to Relational and NoSQL Databases with Log4j 2 >> > Experience: Intermediate >> > >> > Abstract: The newly-released Log4j 2 contains a number of different >> appenders to help you deliver log events to the storage device you desire. >> Among those are the JDBCAppender, JPAAppender, and NoSQLAppender, allowing >> you to store your log events in essentially any database you can imagine. >> While very powerful, configuring these appenders requires more knowledge >> and care than configuring standard file appenders with the PatternLayout. >> In this presentation you will learn more about these appenders, how to >> properly configure and use them, and how to easily support your specific >> NoSQL database of choice. >> > >> > Audience Gain: The audience will gain a better understanding of how >> these three database appenders work. Configuring these appenders involves >> carefully mapping log event properties to columns and creating appropriate >> database tables and columns to match. Audience members will learn about >> these nuances and explore the various options, as well as how to achieve >> the best performance possible. Finally, only a few NoSQL databases are >> supported initially, but creating support for >> > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org 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
