X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.22.2a (ClamAV engine v0.102.2) X-Junk-Score: 0 [] X-KAS-Score: 0 [] From: "Paul Hoadley" Received: from wout2-smtp.messagingengine.com ([64.147.123.25] verified) by post.selbstdenker.com (CommuniGate Pro SMTP 6.3.3) with ESMTPS id 25569335 for webobjects-dev@wocommunity.org; Mon, 15 Mar 2021 06:16:02 +0100 Received-SPF: none receiver=post.selbstdenker.com; client-ip=64.147.123.25; envelope-from=paulh@logicsquad.net Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id BE1AB16DB for ; Mon, 15 Mar 2021 01:15:39 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 15 Mar 2021 01:15:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=V6f8MYbzJ706ymZtvmzBnfFJYten+ HPXMGiLV6ldV9Y=; b=LLm5zrScCgMG6BUKl35E/+fpV9/DyCDYU13gUBOA04qx3 CWzOy7keA6gZOCasLwfh99rEIJ/Zdes76OeqTpszdUo7kjCdab/E9a4GXIf9mYjN eJauDb27KKltYhsQbs7I4jQ1vZ9Se5IV6l52rGb3C8s2aCmlDac+1iMsiOCQz2Z/ C/7e+uVAyAeATO6pzot2KS2l/YYqgDFpIMb7egZ6n+iZ047SGa0o8OyuQ1uSa4JA KHL+OA/5qbDWgQGQnxD2MMiSAciBbvuUyqMK2Ht2n4NRrKqTCL9xtTFHEHXJ5TVI zUc62OdQo6c6aDRsxoGmksMFbzLKZV2K9mmgu5WYg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddvkedgkedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephfgtggfukfffvffosegrtdhmrehhtdejnecuhfhrohhmpefrrghulhcujfho rggulhgvhicuoehprghulhhhsehlohhgihgtshhquhgrugdrnhgvtheqnecuggftrfgrth htvghrnhepgeelveefkeekiefgheffgfevteduvdfftdffteeuvdefhfetgfehudfhtddt ledvnecuffhomhgrihhnpehlohhgihgtshhquhgrugdrnhgvthdplhhinhhkvgguihhnrd gtohhmnecukfhppedvtdefrddvudejrddutddrvdegleenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehprghulhhhsehlohhgihgtshhquhgrug drnhgvth X-ME-Proxy: Received: from [192.168.10.100] (203-217-10-249.perm.iinet.net.au [203.217.10.249]) by mail.messagingengine.com (Postfix) with ESMTPA id 9FF0524005A for ; Mon, 15 Mar 2021 01:15:36 -0400 (EDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_431FFE6E-26E0-4A76-B758-786928EBFBF6" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\)) Subject: Log4J 2.x Message-Id: Date: Mon, 15 Mar 2021 15:45:31 +1030 To: WebObjects & WOnder Development X-Mailer: Apple Mail (2.3445.104.17) --Apple-Mail=_431FFE6E-26E0-4A76-B758-786928EBFBF6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hello, I asked about this on Slack a few weeks ago, with no success. Hopefully = this list will be a wider or at least a different net. I have two = questions that are different but related. 1. Is anyone using Log4J 2.x in a Wonder project? Is there a pain free = way to migrate from 1.x =E2=86=92 2.x while retaining the convenience of = Wonder's hierarchical Properties file loading? 2. Failing that, is anyone using Log4J 1.x and sending log events to = Loggly, but not using Loggly's suggested syslog-based approach? What I want is the lowest effort path from a Wonder application to = Loggly. In another project, I've used Logback's LogglyBatchAppender, = which works just fine, but with Logback's XML-based configuration, I = lose the convenience of setting up logging via hierarchical Properties = files. There are a few "LogglyAppender" projects in various states of = repair on GitHub that appear to be compatible with 1.x, but if anyone = has a known-good solution, I'd love to hear about it. A "HTTPAppender" = that works with 1.x would probably be sufficient. --=20 Paul Hoadley https://logicsquad.net/ https://www.linkedin.com/company/logic-squad/ --Apple-Mail=_431FFE6E-26E0-4A76-B758-786928EBFBF6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hello,

I = asked about this on Slack a few weeks ago, with no success. Hopefully = this list will be a wider or at least a different net. I have two = questions that are different but related.

1. Is anyone using Log4J 2.x in a = Wonder project? Is there a pain free way to migrate from 1.x =E2=86=92 = 2.x while retaining the convenience of Wonder's = hierarchical Properties file loading?

2. Failing that, is anyone using Log4J 1.x and sending log = events to Loggly, but not using Loggly's suggested = syslog-based approach?

What I want is the lowest effort path from a Wonder = application to Loggly. In another project, I've = used Logback's LogglyBatchAppender, which works just fine, but = with Logback's XML-based configuration, I lose the convenience of = setting up logging via hierarchical Properties files. There = are a few "LogglyAppender" projects in various states of repair on = GitHub that appear to be compatible with 1.x, but if anyone has a = known-good solution, I'd love to hear about it. A "HTTPAppender" that = works with 1.x would probably be sufficient.

-- 
Paul Hoadley
https://logicsquad.net/https://www.linkedin.com/company/logic-squad/


= --Apple-Mail=_431FFE6E-26E0-4A76-B758-786928EBFBF6--