Copy the file "log4j.properties" from "misc\Log4j Sample Configuration" to your classes directory and debugging will probably be enabled.
On Feb 12, 4:38 pm, KJ <[email protected]> wrote: > Actually, no idea how to do that. I've tried using -Dsmslib.debug > (using Apache log4j, have the .properties file in the same folder as > all the classes), but that didn't change the screen output at all. At > some point, it even broke the ReadMessages example (which now doesn't > work, and only throws two NullPointerExceptions - at app.doIt (main) > and ths.srv.stopService() (doIt). I can't even recover the program to > "work" the same way it was previously >< Any idea what causes this? By > the way, I'm not using an IDE - using Notepad++ and command line java/ > javac, with a .bat to plug in custom libraries using -classpath. > > On Feb 12, 4:20 am, Thanasis <[email protected]> wrote: > > > > > Please increase the logging level to DEBUG. The trace you are showing > > me is minimal. > > (You can redirect the error output to a file and grab it).- Hide quoted > > text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "SMSLib User Group" 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/smslib?hl=en.
