On Sep 10, 2016 11:33 PM, "Ralph Goers" <ralph.go...@dslextreme.com> wrote:
>
> But Gary said he didn’t want the OS390 appender created unless he is
running on OS390.
Right, IRL, I am going to use an Appender that does some JNI calls that
will only work on OS/390.
Gary
>
> But your example makes me think we also need an AppenderRef Selector.
>
> Ralph
>
>> On Sep 10, 2016, at 5:28 PM, Remko Popma <remko.po...@gmail.com> wrote:
>>
>> What you can also do (without Log4j enhancements) is create a plugin
appender that takes two Appender-Refs and delegates to the correct one for
your application.
>>
>> In configuration this could look like this:
>>
>> <Appenders>
>> <FileAppender name="unix" ...
>> <FileAppender name="OS390" ...
>>
>> <MyDelegatingAppender name="delegator">
>> <AppenderRef ref="unix" />
>> <AppenderRef ref="OS390" />
>> </MyDelegatingAppender>
>>
>> Remko
>>
>> Sent from my iPhone
>>
>> On 2016/09/11, at 3:48, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>>
>>> Oops. I forgot the closing CDATA tag in the script.
>>>
>>> Ralph
>>>
>>>> On Sep 10, 2016, at 11:43 AM, Ralph Goers <ralph.go...@dslextreme.com>
wrote:
>>>>
>>>> Interesting. OS/390. I worked on MVS, OS/370, z/OS, etc many moons
ago but haven’t worked on a mainframe since 2001.
>>>>
>>>> This sort of sounds like you want an Appender Selector, which would be
an Appender that uses a Selector to figure out which Appender to delegate
to. This is a bit like the PatternSelector. I would imagine it would make
sense to implement AppenderSelectors and LayoutSelectors. You probably
would want to dynamically initialize the Appenders much like the
RoutingAppender does.
>>>>
>>>> Maybe it would look like:
>>>>
>>>> <Appenders>
>>>> <ScriptSelector name=“" default=“”>
>>>> <Script language=“groovy”><