Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Subject: Re: cayenne library changes log level in struts2
From: Andrus Adamchik <andrus@objectstyle.org>
In-Reply-To: <454A7C66-1D8A-4F1C-9E24-21EB55EFE43E@gmail.com>
Date: Tue, 3 Dec 2013 20:35:43 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5196873-371A-4B25-B3A0-0636E2345F8A@objectstyle.org>
References: 
 <CAMiU5btoqWK9ZHG4O+i_Cqcjjt++EJBKXGd21UfVQET=QxA8EQ@mail.gmail.com>
 <87B7E069-4E4A-4D45-BDC0-B1B5FA753756@gmail.com>
 <856BD870-2E11-4A12-8FF5-06C4200CAD1E@objectstyle.org>
 <D653BB25-212D-4427-ACF3-02780253AC72@gmail.com>
 <CAM1yOjYHGcCW5MCm5Y0+0CBreU=LD4qwXbHD9GzzsaHJzpFHig@mail.gmail.com>
 <047CCB6E-A97C-40EE-AE83-FA72B5434D9F@gmail.com>
 <CAM1yOjZN59AcQnBvC5Xu5eQ48VK4qZrrcYUxC8D_t4rqJ1Ty1g@mail.gmail.com>
 <1977D58A-8A5E-4640-94AC-0A68AEDD66F6@objectstyle.org>
 <CAM1yOjaChSES+=bK+sv04EoPU4H2tVKqy7Bw74D_TJyXw9nMRA@mail.gmail.com>
 <454A7C66-1D8A-4F1C-9E24-21EB55EFE43E@gmail.com>
To: user@cayenne.apache.org

Hah, I read this when I was typing something along the lines of =93we =
need a JSR to address this..=94 :)

On Dec 3, 2013, at 8:20 PM, Christian Grobmeier <grobmeier@gmail.com> =
wrote:

> On 3 Dec 2013, at 16:14, Mike Kienenberger wrote:
>=20
>> On Tue, Dec 3, 2013 at 10:01 AM, Andrus Adamchik =
<andrus@objectstyle.org> wrote:
>>> Ideally I=92d love to have zero dependency on a third-party logging =
framework. So that probably means using j.u.l and let the users bridge =
that as they want. Wonder if we=92ll make everyone=92s life miserable as =
a result?
>>=20
>> No, we made that horrible mistake of going with j.u.l at MyFaces a
>> while back based in part on my lobbying for it.  It is a disaster to
>> end-users to have j.u.l as the default logging system.   There's no
>> way to bridge from j.u.l back to something else without huge
>> performance hits, so you lose any control over what logging system
>> your end-users can use.   It's very difficult to get it to read
>> configuration information from a file.   It has horrible two-line
>> logging output by default, which is again difficult to change.   At
>> least under weblogic app servers, you cannot identify which
>> applications are generating which log messages, and I'm pretty sure
>> that this is true in general for it.
>>=20
>> Really, there's nothing good you can say about it other than it might
>> save you the 721K commons logging dependency.
>=20
> I agree here. Jul is painfully broken and doesn't work well with =
others.
> Even bridging from $x to Jul is painful.
>=20
> However I am currently preparing to put some effort into a new Logging =
JSR:
> https://java.net/projects/newlogging
> So far I didn't haven the time yet, but I plan to push this around =
xmas.
>=20
> Imagine a logging proxy like slf4j or log4j2 in the JDK. Not =
implementation like
> JUL, just the interfaces. This is the goal. Unfortunately this will be =
a tough road
> and if it ever happens is not sure.
>=20
>=20
>=20
>=20
>=20
> ---
> http://www.grobmeier.de
> @grobmeier
> GPG: 0xA5CC90DB
>=20