Yeah, I'm going through them right now. Trying to find out what broke
NTEventLogAppenderr.

Right now I'm betting on the move from Java 6 to Java 7 but that's just a
guess so far.

/Bengt

2016-07-01 10:47 GMT+02:00 'Achim Nierbeck' via OPS4J <
[email protected]>:

> Hi Bengt,
>
> did you check the changes between the two versions?
>
> regards, Achim
>
>
> 2016-07-01 10:08 GMT+02:00 Bengt Rodehav <[email protected]>:
>
>> I have now tested with Pax-logging 1.8.4 on Karaf 4.0.5 and the 
>> NTEventLogAppender
>> is resolved there. So, the change that broke NTEventLogAppender happened
>> between Pax-logging 1.8.4 and 1.8.5.
>>
>> /Bengt
>>
>> 2016-07-01 9:35 GMT+02:00 Bengt Rodehav <[email protected]>:
>>
>>> This has been discussed on the Karaf user list:
>>>
>>>
>>> http://karaf.922171.n3.nabble.com/Log4j-NTEventLogAppender-in-Karaf-4-0-5-td4046993.html
>>>
>>> /Bengt
>>>
>>> 2016-07-01 9:33 GMT+02:00 Bengt Rodehav <[email protected]>:
>>>
>>>> On the Karaf mailing list, Achim has informed me that log4j 1.2.x is
>>>> still being used for the implementation of Pax-logging 1.8.5 so things
>>>> should still work.
>>>>
>>>> However, I have tested (although with some problems) to use Pax-logging
>>>> 1.8.1 (instead of 1.8.5 which is normally used) with Karaf 4.0.5. The
>>>> results indicate that the NTEventLogAppender works with Pax-logging 1.8.1
>>>> but not with Pax-logging 1.8.5.
>>>>
>>>> Can anyone explain why this is? I do not understand it myself.
>>>>
>>>> Both versions of Pax-logging seem to depend on version 1.2.16 of log4j
>>>> but has different dependencies on log4j2 (2.0.2 in Pax-logging 1.8.1 and
>>>> 2.5 in Pax-logging 1.8.5).
>>>>
>>>> /Bengt
>>>>
>>>>
>>>>
>>>> 2016-06-30 17:00 GMT+02:00 Bengt Rodehav <[email protected]>:
>>>>
>>>>> Hello,
>>>>>
>>>>> I'm currently upgrading (trying to) from Karaf 2.4.1 to 4.0.5. This
>>>>> also means upgrading from Pax-logging 1.8.1 to 1.8.5.
>>>>>
>>>>> I am depending on the ability to log events to the Windows event log.
>>>>> I have been doing this by using the NTEventLogAppender.dll. There is both 
>>>>> a
>>>>> 32 bit and a 64 bit version of this DLL.
>>>>>
>>>>> This has worked fine but...
>>>>>
>>>>> It seems like Pax-logging 1.8.5 no longer supports log4j 1.2.x but
>>>>> only log4j 2.x. This breaks the NTEventLogAppender.dll.
>>>>>
>>>>> I haven't found any way to be able to log to Windows event log via
>>>>> Pax-logging 1.8.5. The closest I've found is the project log4jna (
>>>>> https://github.com/dblock/log4jna). There is a commit that seems to
>>>>> upgrade to log4j 2.x but no release.
>>>>>
>>>>> Does anyone have a solution to the problem on how to log to Windows
>>>>> event log using Pax-logging 1.8.5?
>>>>>
>>>>> /Bengt
>>>>>
>>>>
>>>>
>>>
>> --
>> --
>> ------------------
>> OPS4J - http://www.ops4j.org - [email protected]
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "OPS4J" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
> Software Architect / Project Manager / Scrum Master
>
> --
> --
> ------------------
> OPS4J - http://www.ops4j.org - [email protected]
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
------------------
OPS4J - http://www.ops4j.org - [email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to