You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Chamikara Jayalath (JIRA)" <ji...@apache.org> on 2006/10/12 04:47:36 UTC
[jira] Commented: (SANDESHA2-2) Enable trace for Sandesha2 Msg
flows
[ http://issues.apache.org/jira/browse/SANDESHA2-2?page=comments#action_12441600 ]
Chamikara Jayalath commented on SANDESHA2-2:
--------------------------------------------
Applied the patch.
Thanks
Chamikara
> Enable trace for Sandesha2 Msg flows
> ------------------------------------
>
> Key: SANDESHA2-2
> URL: http://issues.apache.org/jira/browse/SANDESHA2-2
> Project: Apache Sandesha2
> Issue Type: Improvement
> Reporter: Andrew Gatford
> Priority: Trivial
> Attachments: moretrace.patch, patch.diff, patch2.patch, tracePatch1.txt
>
>
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org