I created a Log4J-appserver module and added the Tomcat support there. I took a look at jetty and it supports Log4J by routing it through slf4j. I'd like to change that but I am not too familiar with the internals of jetty so that might take a bit.
Ralph > On Sep 7, 2017, at 4:47 AM, Mikael Ståldal <mi...@apache.org> wrote: > > But is it more generic than JavaEE? If not, a generic name is misleading. > > >> On 2017-09-07 00:07, Remko Popma wrote: >> log4j-container? >> (To be more generic than javaee) >>> On Sep 7, 2017, at 4:56, Ralph Goers <ralph.go...@dslextreme.com> wrote: >>> >>> Yes, the intent would be to allow containers to use Log4j as their logging >>> implementation. >>> >>> Ralph >>> >>>> On Sep 6, 2017, at 12:26 PM, Mikael Ståldal <mi...@apache.org> wrote: >>>> >>>> Is the point to integrate with JavaEE containers, not necessarily from a >>>> web app? >>>> >>>> Then I would suggest a new module log4j-javaee, and to put it in the main >>>> repo. >>>> >>>> >>>>> On 2017-09-06 20:49, Ralph Goers wrote: >>>>> On the commons list I got some pointers on how to integrate with Tomcat >>>>> 8.5+ and TomEE. I’ve written the class that is required but am wondering >>>>> where to put it. It could go in log4j-core, but that isn’t where we have >>>>> been putting these things. It really shouldn’t go in log4j-web as users >>>>> may not want that jar just to get the integration with log4j. >>>>> I am thinking a new module should be created for this - something like >>>>> log4j-containers. If I do that does it belong in log4j2 or in >>>>> log4j-tools, log4j-boot or some other repo? >>>> >>> >>> > >
