axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Commented: (AXISCPP-100) enable axis c++ (engine) tracing
Date Thu, 27 Jan 2005 13:08:17 GMT
     [ http://issues.apache.org/jira/browse/AXISCPP-100?page=comments#action_58150 ]
     
Samisa Abeysinghe commented on AXISCPP-100:
-------------------------------------------

Are we happy with the current level of tracing available with Axis C++?

Do we have any plans to implement the said level of tracing? 

Do we have this kind of feature with Axis Java?

Personally I do feel that this level of tracing would help; however would make the code too
clumsy, unless otherwise we use AOP, which is far too much. Hence I do not think we should
go for this.

> 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


Mime
View raw message