You will loose some of the benefits of Log4cxx that way, e.g. you can't
use the efficient LOG4CXX_*-macros and will loose things like line
numbers and function names where the logging occurred because those
are inserted by the pre processor. The latter will always be the
methods of your wrapper unless the wrapper is entirely implemented as
macros itself.
I am still thinking of this and not sure, how can i achieve filename and
line number to be printed correctly.
Sounds like you need to debug your wrapper, the filename surely gets
lost somewhere. I don't see how we can help with that.
Even if i pass a hard coded path like
DOMConfigurator::Configure("c:\properties.xml"), file name is not accepted.
Not sure, what's going wrong here.
--
View this message in context:
http://apache-logging.6191.n7.nabble.com/using-log4cxx-from-sca-component-tp44065p44161.html
Sent from the Log4cxx - Dev mailing list archive at Nabble.com.
