Enable trace for Sandesha2 Msg flows
------------------------------------

         Key: SANDESHA2-2
         URL: http://issues.apache.org/jira/browse/SANDESHA2-2
     Project: Apache Sandesha2
        Type: Improvement

    Reporter: Andrew Gatford
    Priority: Trivial


To enable quicker debuging of problems encountered it would be good to trace 
the entry/exit of key methods so that people can quickly see the flow of 
messages through Sandesha2.

For example when creating a new Bean Manager implementation and encountering 
problems it would be good to know what Sandesha was trying to do at the time 
the failure occured



-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to