[
https://issues.apache.org/jira/browse/AXIS2C-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646518#action_12646518
]
Damitha Kumarage commented on AXIS2C-1286:
------------------------------------------
However my small change to your patch wont' change the idea. If you provide the
log structure and implement your own write function then whether critical log
message is always written or not is under your control.
> Improve the logging facilities to let the client specify their own logging
> mechanism
> ------------------------------------------------------------------------------------
>
> Key: AXIS2C-1286
> URL: https://issues.apache.org/jira/browse/AXIS2C-1286
> Project: Axis2-C
> Issue Type: Improvement
> Components: util
> Affects Versions: 1.5.0
> Reporter: Dmitry Goncharov
> Attachments: axis2_log.patch, axis2_log_test.patch
>
>
> The current logging mechanism implemented in util/src/log.c makes the client
> to provide a file for the library to output logging info to.
> This mechnism can be improved in such a way the the client can provide their
> own struct axutil_log_t.
> By the means of a custom axutil_log_t the client can make the library do the
> logging the way the client needs.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
