Guten Tag Nandan S, am Montag, 24. Februar 2014 um 12:53 schrieben Sie: > Hi ,
Please don't post each of your questions to both the dev and users mailing list, this will only make it unnecessary hard to follow the discussions. Choose one, preferable the users mailing list because it's main purpose is support for our users like you are. :-) > Both the messages were displayed in console. But, i am designing my > application which uses log4cxx, in such a way that it won't have any console > window. In such a case where the messages logged ? The internal logging only uses STDOUT and STDERR, much like a chicken and egg problem. It's hard to provide more if the errors already occur while providing that "more". > This is required for debugging to check what's wrong. Without the > messages it will be difficult to identify what's the error. You can have a look at log4cxx/helpers/loglog.h and it's implementation to see if you may adopt it to use some "more" which better fit your environment. the only thing coming into my mind currently is to redirect STDOUT and STDERR on your own in your application. > Also, does log4cxx throw any exceptions which can be handled in the > application which uses it ? Doesn't like, errors are only logged. Have a look at DOMConfigurator::doConfigure in domconfigurator.cpp. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
