Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Appender's append() method
From: Ralph Goers <ralph.goers@dslextreme.com>
In-Reply-To: 
 <CACZkXPyXVAA-PN9uQt-i_s3P2c98ucZp8-RtgSZLwDro98b4wA@mail.gmail.com>
Date: Wed, 13 Jan 2016 17:28:11 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A6754F97-787F-4666-B47F-CED59ACFCFA9@dslextreme.com>
References: <COL126-W13F9EB61ADFC8EF14E775CDBCB0@phx.gbl>
 <BC2368EF-25BD-4045-99E7-8CA09FC13439@dslextreme.com>
 <CACZkXPyXVAA-PN9uQt-i_s3P2c98ucZp8-RtgSZLwDro98b4wA@mail.gmail.com>
To: Log4J Users List <log4j-user@logging.apache.org>

Sorry, that was what I meant.

Ralph

> On Jan 13, 2016, at 3:17 PM, Gary Gregory <garydgregory@gmail.com> =
wrote:
>=20
> IMO a RuntimeException subclass is appropriate while RuntimeException
> should not be used.
>=20
> Gary
>=20
> On Wed, Jan 13, 2016 at 1:53 PM, Ralph Goers =
<ralph.goers@dslextreme.com>
> wrote:
>=20
>> Your appender is automatically wrapped by an AppenderControl object. =
The
>> AppenderControl will inspect the ignoreExceptions flag so your =
Appender
>> does not have to.  Your Appender should just throw a RuntimeException =
if it
>> encounters a problem.
>>=20
>> Ralph
>>=20
>>> On Jan 13, 2016, at 2:38 PM, Nicholas Duane <nickdu@msn.com> wrote:
>>>=20
>>> I'm new to java so maybe this should be an obvious question to most =
java
>> developers.  If I'm trying to override the append() method but also =
throw
>> exceptions, how is that done?
>>>=20
>>> I'm asking because I assume my append method's outermost catch block =
is
>> to inspect the ignoreExceptions flag and either bubble up the =
exception if
>> ignoreExceptions is false or eat the exception otherwise, most likely =
just
>> logging an event.  Is that true?  If so, then how do I accomplish =
that?  I
>> tried coding it as I mentioned above (actually someone else did it =
for me),
>> but the compiler I guess was complaining about the throw needing to =
be in a
>> catch block, I assume because the append() method is not defined to =
throw
>> exceptions.
>>>=20
>>> In addition, looking at what I think was source for one of your
>> appenders at:
>>>=20
>>>=20
>> =
https://git-wip-us.apache.org/repos/asf?p=3Dlogging-log4j2.git;a=3Dblob;f=3D=
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/AbstractOu=
tputStreamAppender.java;h=3D9a4cfde83194c866c30c4687e9f4ebb19cb20a17;hb=3D=
75d33d96ac00356014cf11f8ad9e8c6ead4db37a
>>>=20
>>> Why does it always throw an exception in the catch block instead of
>> checking the state of the ignoreExceptions flag?
>>>=20
>>> Thanks,
>>> Nick
>>>=20
>>=20
>>=20
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>=20
>>=20
>=20
>=20
> --=20
> E-Mail: garydgregory@gmail.com | ggregory@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


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org