Return-Path: X-Original-To: apmail-logging-log4j-user-archive@www.apache.org Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A78DA10ADF for ; Sun, 30 Mar 2014 05:43:06 +0000 (UTC) Received: (qmail 37558 invoked by uid 500); 30 Mar 2014 05:43:05 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 36923 invoked by uid 500); 30 Mar 2014 05:43:03 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 36913 invoked by uid 99); 30 Mar 2014 05:43:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Mar 2014 05:43:02 +0000 X-ASF-Spam-Status: No, hits=3.3 required=5.0 tests=HTML_IMAGE_ONLY_08,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_REMOTE_IMAGE X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of james.a.hutton@gmail.com designates 209.85.128.176 as permitted sender) Received: from [209.85.128.176] (HELO mail-ve0-f176.google.com) (209.85.128.176) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Mar 2014 05:42:54 +0000 Received: by mail-ve0-f176.google.com with SMTP id db11so4091085veb.35 for ; Sat, 29 Mar 2014 22:42:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=h4Y07OlcQfyuD21Sha19PzzKSL86osf54wHrQjErXRs=; b=F9b8K7tDShLYVUmhmbWRzOh0s/51nFU3DFSVilVLuF7ncuqhL6Ae7fhwhQUHm+1QV2 Orl2sZ05oi7+yiBorPPIkuLFlkokSq0BGM6/WFcNrLOhZSqpVszaSL3yArv9zA+RqLj7 Emt91uF/fsy2gDn6ROEov5HFVeNZTaFHvfJHq3uI+thQH3cY/HQxjZEX4uBD3NQbM7c3 aOmvavP7pNdciDqwP5xcCtTJAOUlirBQi+u4/3F7eZebPO+H2yDho6/mULvsQ+4Rd0sX IKnTzDrqKPo+pVyPhAqmCUx2xoCM/uqPCEse+Y20pokXfxratkAIGBqLpzsb5RWVP6E+ YFGQ== MIME-Version: 1.0 X-Received: by 10.220.109.1 with SMTP id h1mr325263vcp.20.1396158153214; Sat, 29 Mar 2014 22:42:33 -0700 (PDT) Received: by 10.220.106.138 with HTTP; Sat, 29 Mar 2014 22:42:33 -0700 (PDT) Date: Sun, 30 Mar 2014 01:42:33 -0400 Message-ID: Subject: Merging log4j2 contexts From: James Hutton To: log4j-user@logging.apache.org Content-Type: multipart/alternative; boundary=001a11c308d6c5d18f04f5cc6634 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c308d6c5d18f04f5cc6634 Content-Type: text/plain; charset=UTF-8 I'm looking to leverage log4j2 in a spring application that uses spring profiles heavily. I know in log4j1.2 we could use the DOMConfigurator to parse an additional xml and merge it into the context. James --001a11c308d6c5d18f04f5cc6634--