Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 10 Apr 2015 13:19:13 +0000 (UTC)
From: "Jan Bernhardt (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12820061.1428670472000.53867.1428671953082@Atlassian.JIRA>
In-Reply-To: <JIRA.12820061.1428670472000@Atlassian.JIRA>
References: <JIRA.12820061.1428670472000@Atlassian.JIRA>
 <JIRA.12820061.1428670472328@arcas>
Subject: [jira] [Resolved] (CXF-6345) Support Logging in JexlClaimMapper
 scripts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CXF-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Bernhardt resolved CXF-6345.
--------------------------------
    Resolution: Fixed

> Support Logging in JexlClaimMapper scripts
> ------------------------------------------
>
>                 Key: CXF-6345
>                 URL: https://issues.apache.org/jira/browse/CXF-6345
>             Project: CXF
>          Issue Type: Improvement
>          Components: STS
>    Affects Versions: 3.0.4, 2.7.15
>            Reporter: Jan Bernhardt
>            Assignee: Jan Bernhardt
>            Priority: Minor
>             Fix For: 3.1.0, 2.7.16, 3.0.5
>
>
> To improve debugging of Jexl scripts it will be helpful to provide a logging util.
> You can create log statements like this:
> {code}
> LOG:fine("Debug message");
> LOG:info("Useful information");
> LOG:warning("This is a warning");
> LOG:severe("Error message");
> {code}
> (on) Note the colon instead of the dot after LOG
> If you don't want to use the {{java.util.logging.Logger}} you can setup for example a SLF4J logger like this:
> {code}
> org.slf4j.Logger logger = org.slf4j.LoggerFactory.getLogger(MyMapperTest.class);
> jcm = new JexlClaimsMapper();
> jcm.getJexlEngine().getFunctions().put("LOG", logger);
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)