logging-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <ralph.go...@dslextreme.com>
Subject Re: [log4j] MongoDB Appender changes heads up.
Date Thu, 11 Jan 2018 05:04:14 GMT
So now we need Java 7, 8 and 9 to perform a build? Did you update the build documentation?
Is that the only tool available to test MongoDB?


> On Jan 10, 2018, at 8:18 PM, Gary Gregory <garydgregory@gmail.com> wrote:
> The changes are both binary compatible and behavior compatible. The new
> code kicks in only if the NoSqlAppender node contains a MessageLayout
> child, which was not possible before.
> I also added some code to test against an embedded MongoDB instance by
> using code from de.flapdoodle.embed.mongo. This all works from Eclipse and
> from my Windows command line but Jenkins is having some trouble it seems.
> The code from de.flapdoodle.embed.mongo requires Java 8 so I am using a
> special JUnit test suite to run the code with a JUnit Assume that only runs
> the suite on Java 8 and above.
> But for some reason, when Jenkins compiles the MongoDB tests it complains
> about byte code versions 52 vs. 51. It might be the case that the MongoDB
> tests will need to be compiled with Java 8. Not sure yet...
> Gary
> On Wed, Jan 10, 2018 at 5:22 PM, Remko Popma <remko.popma@gmail.com> wrote:
>> No objection, but please do this in a way that existing users of this
>> appender are not affected.
>> So if the new behavior is incompatible with the current behavior, then the
>> new behavior should be switched on explicitly in configuration.
>> Remko
>> (Shameless plug) Every java main() method deserves http://picocli.info
>>> On Jan 11, 2018, at 7:49, Gary Gregory <garydgregory@gmail.com> wrote:
>>> Hi All:
>>> I need for the MongoDB Appender to behave similarly to the JMS Appender
>>> regarding MapMessages.
>>> What I plan on doing:
>>> Like with the JMS Appender, if the MongoDB element contains a child
>>> MessageLayout element, the MongoDB appender will apply this layout.
>>> Like with the JMS Appender, my goal is to let a MapMessage be converted
>> to
>>> a MongbDB object with key and values from the MapMessage, not from the
>>> LogEvent.
>>> I will create a Jira.
>>> Gary

View raw message