airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Marru <>
Subject Re: Issues with slf4j with axis2
Date Fri, 19 Oct 2012 18:59:33 GMT
Hi Lahiru,

It is important that we have one logging across all of Airavata modules. I agree axis2 compatibility
is an important one, but we should also be forward looking. 

Looks like you are contradicting yourself - [1] :)

I see log4j is superseded by logback [2]? any insights on if we will run into class loading
issues or other complaints on log4J?  

Here is a trace of previous changes [3].


[1] -
[2] -
[3] -

On Oct 19, 2012, at 2:31 PM, Lahiru Gunathilake <> wrote:

> Hi Devs,
> I have seen some issues with slf4j when using with axis2 logging, and I
> have seen some people complaining about this. I think its very important
> that we have proper logging and put them in to a separate file rather
> putting in to catalina.out when we deploy on tomcat.
> I think it would be great if we can have separate logs per services (we
> have mainly 4 services) and things will be very nice forthe administrator.
> If we want to do this we should go ahead with axis2 friendly logging
> implementation.
> I just tested with log4j and things works fine, if there are no objections
> I dn't mind moving airavata logging to log4j.
> Lahiru
> -- 
> System Analyst Programmer
> PTI Lab
> Indiana University

View raw message