You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Mark Whitlock (JIRA)" <ax...@ws.apache.org> on 2005/07/04 16:58:09 UTC
[jira] Created: (AXISCPP-728) Trace: better multiline output
Trace: better multiline output
------------------------------
Key: AXISCPP-728
URL: http://issues.apache.org/jira/browse/AXISCPP-728
Project: Axis-C++
Type: Bug
Components: Trace Utility
Reporter: Mark Whitlock
Assigned to: Mark Whitlock
Priority: Minor
The trace analyzer tool shows the first line of a multiline trace statement in the trace window and subsequent lines are shown in the detail window. It would be more readable to output a parameter summary in the first line of each trace statement, and a fuller output in subsequent lines. This should be done for character strings that contain newline characters (which are currently split over several lines in the trace). This could also be done where the trace needs to dump a large amount of data (bug hex dumps).
This problem was originally described in AXISCPP-406, which also contained a variety of other problems. AXISCPP-406 has now been closed and separate JIRAs raised for the remaining problems.
--
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
[jira] Updated: (AXISCPP-728) Trace: better multiline output
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-728?page=all ]
Fred Preston updated AXISCPP-728:
---------------------------------
Assign To: (was: Mark Whitlock)
> Trace: better multiline output
> ------------------------------
>
> Key: AXISCPP-728
> URL: http://issues.apache.org/jira/browse/AXISCPP-728
> Project: Axis-C++
> Type: Bug
> Components: Trace Utility
> Reporter: Mark Whitlock
> Priority: Minor
>
> The trace analyzer tool shows the first line of a multiline trace statement in the trace window and subsequent lines are shown in the detail window. It would be more readable to output a parameter summary in the first line of each trace statement, and a fuller output in subsequent lines. This should be done for character strings that contain newline characters (which are currently split over several lines in the trace). This could also be done where the trace needs to dump a large amount of data (bug hex dumps).
> This problem was originally described in AXISCPP-406, which also contained a variety of other problems. AXISCPP-406 has now been closed and separate JIRAs raised for the remaining problems.
--
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
[jira] Closed: (AXISCPP-728) Trace: better multiline output
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nadir amra closed AXISCPP-728.
------------------------------
Resolution: Won't Fix
> Trace: better multiline output
> ------------------------------
>
> Key: AXISCPP-728
> URL: https://issues.apache.org/jira/browse/AXISCPP-728
> Project: Axis-C++
> Issue Type: Bug
> Components: Trace Utility
> Reporter: Mark Whitlock
> Priority: Minor
>
> The trace analyzer tool shows the first line of a multiline trace statement in the trace window and subsequent lines are shown in the detail window. It would be more readable to output a parameter summary in the first line of each trace statement, and a fuller output in subsequent lines. This should be done for character strings that contain newline characters (which are currently split over several lines in the trace). This could also be done where the trace needs to dump a large amount of data (bug hex dumps).
> This problem was originally described in AXISCPP-406, which also contained a variety of other problems. AXISCPP-406 has now been closed and separate JIRAs raised for the remaining problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org