Change (or create) your log4j.properties and add: log4j.category.org.apache.axis.transport.http.HTTPSender=DEBUG,Console log4j.additivity.org.apache.axis.transport.http.HTTPSender=false
On Oct 9, 7:20 am, LeTic <[EMAIL PROTECTED]> wrote: > Hi again, > > When trying to enable the logging to debug our issue I couldn't make > it work anymore... > > I know I used this functionality a lot when I first developed our > synchronisation class and from what I could see in our svn we were > already using log4j at the time which seems to rule it out. I even try > reverting to the log4j.xml from that time with no success. > > I checked the source code and it seems the adwords java api is using > java.util.logging on org.apache.axis.transport.http.httpsender which > in turns use commons logging to log it's stuff. I downloaded all these > libraries source code and trace the issue but it does go into if > (log.isDebugEnabled()) and run log.debug functions. I could even have > the messages there in debug mode but they are just nor printed into > the console. > > I tried adding stuff to my log4j configuration like : > <category name="org.apache.axis"> > <priority value="DEBUG"/> > </category> > > with no more success... > > Is anybody encountering the same issue ? Anybody has a clue on how to > configure this ? > > My versions : > - adwords java api 2.1.0 > - Axis 1.4 > - commons-logging 1.0.4 > - log4j 1.2.14 > > Thanks in advance > Cheers > LeTic --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
