Hi all,

Did we added this to ESB 4.9?


On Mon, Oct 14, 2013 at 11:13 AM, Sagara Gunathunga <sag...@wso2.com> wrote:

>
>
>
> On Sat, Oct 12, 2013 at 8:16 AM, Sanjiva Weerawarana <sanj...@wso2.com>
> wrote:
>
>> Great feature but don't slip it into 4.8.0 which is due to release in
>> days!!!!! NOT a good idea to add features last second like this.
>>
>
> Will schedule for 4.9.0 and for the time being I will push this feature to
> Apache Synapse trunk as they planning to have a release soon.
>
> Thanks !
>
>>
>>
>> On Fri, Oct 11, 2013 at 10:50 PM, Sumedha Rubasinghe <sume...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Friday, October 11, 2013, Isuru Udana wrote:
>>>
>>>> Hi Sagara,
>>>>
>>>> This is a very useful feature to have. Please check-in the code to
>>>> synapse so that we can have it for ESB 4.8.0.
>>>>
>>> +1
>>>
>>>>
>>>> Thanks,
>>>>  IsuruU
>>>>
>>>>
>>>> On Fri, Oct 11, 2013 at 8:12 PM, Sagara Gunathunga <sag...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>> Proxy services already support for per service logging configuration,
>>>>> which means though the log4j.properties file it is possible to control
>>>>> logging behavior per proxy services such as create separate log file per
>>>>> proxy, define log category per proxy etc.  But for the moment ESB APIs
>>>>> don't support for per API logging configuration. Since there are some user
>>>>> interest on this feature  I looked into related code and realized this can
>>>>> be supported easily, in fact I end up adding this support. Please find
>>>>> details of this new feature below.
>>>>>
>>>>>
>>>>> (1) Like SERVICE_LOGGER which is common for all (proxy) services there
>>>>> will be a new logger called API_LOGGER which is common for all APIs and it
>>>>> will persist log messages into wso2-esb-api.log file.
>>>>>
>>>>>
>>>>> (2) It is possible to refer each API uniquely on log4j.properties file
>>>>> using API_LOGGER.{API-Name}  category.
>>>>>
>>>>> e.g - log4j.category.API_LOGGER.*TestAPI*=DEBUG,  TestAPI_ APPENDER
>>>>>
>>>>>
>>>>>
>>>>> Thanks !
>>>>>
>>>>> --
>>>>> Sagara Gunathunga
>>>>>
>>>>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>>>>> V.P Apache Web Services;    http://ws.apache.org/
>>>>> Linkedin; http://www.linkedin.com/in/ssagara
>>>>> Blog ;  http://ssagara.blogspot.com
>>>>>
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> Architecture@wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Isuru Udana*
>>>> Senior
>>>> * Software Engineer*
>>>> WSO2 Inc.; http://wso2.com
>>>> email: isu...@wso2.com cell: +94 77 3791887
>>>> blog: http://mytecheye.blogspot.com/
>>>> twitter: http://twitter.com/isudana
>>>>
>>>
>>>
>>> --
>>> /sumedha
>>> m: +94 773017743
>>> b :  bit.ly/sumedha
>>>
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
>> 650 265 8311
>> blog: http://sanjiva.weerawarana.org/
>>
>> Lean . Enterprise . Middleware
>>
>> _______________________________________________
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;    http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>
> _______________________________________________
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Miyuru Wanninayaka
Senior Technical Lead
WSO2 Inc. : http://wso2.com

Mobile : +94 77 209 9788
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to