[ http://issues.apache.org/jira/browse/AXISCPP-100?page=comments#action_58287 ] Samisa Abeysinghe commented on AXISCPP-100: -------------------------------------------
IMHO FFDC is going to be very useful. Because, as of now, it takes whole lot of effort to get to know the real reasons fo failure. More than for client side, this would make lot of sense on server side LOG4C - good idea, but would have to have a POC to evaluate feasibility. Specially thread safety etc. (Going by the experiances with LibWWW :) ) > enable axis c++ (engine) tracing > -------------------------------- > > Key: AXISCPP-100 > URL: http://issues.apache.org/jira/browse/AXISCPP-100 > Project: Axis-C++ > Type: Wish > Versions: future (enh) > Environment: ALL > Reporter: Aleksander Slominski > > i think it would be good to have some kind of tracing/logging compiled into > binary that could be triggered by setting environment variable (for example > AXISCPP_TRACE=engine:ALL). > it would be very useful tool when debugging such problems like wrong > SOAPAction to see if engine received request and see where did it go and why > it was rejected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
