This is not critical, but I think it's better if we can upgrade log4j in
next major release, i.e. Carbon 4.3.0

As I mentioned, with Log4j 2 [1] "Thread Context" support, we should be
able avoid classes like TenantAwarePatternLayout [2].

[1] http://logging.apache.org/log4j/2.x/
[2]
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0009/core/org.wso2.carbon.utils/4.2.0/src/main/java/org/wso2/carbon/utils/logging/TenantAwarePatternLayout.java

On Tue, Sep 23, 2014 at 10:17 PM, Afkham Azeez <[email protected]> wrote:

> If this is something critical, we should get it into the next major
> release rather than wait for C5.
>
> On Thu, Jun 19, 2014 at 10:03 PM, Isuru Perera <[email protected]> wrote:
>
>> Hi,
>>
>> Can we look at $subject for tenant information etc? I think this is
>> better than implementing custom appenders, pattern layouts etc.
>>
>> In Log4j 2, this is part of "Thread Context" [1].
>>
>> Also, are we planning to use Log4j 2 in Carbon 5?
>>
>> Thanks!
>>
>> Best Regards,
>>
>> [1] http://logging.apache.org/log4j/2.x/manual/thread-context.html
>>
>> --
>> Isuru Perera
>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>*
> *email: **[email protected]* <[email protected]>
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* <http://blog.afkham.org>
> *twitter: **http://twitter.com/afkham_azeez*
> <http://twitter.com/afkham_azeez>
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> <http://lk.linkedin.com/in/afkhamazeez>*
>
> *Lean . Enterprise . Middleware*
>



-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to