[
https://issues.apache.org/jira/browse/AXIS2C-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841437#action_12841437
]
Olivier Mengué commented on AXIS2C-1455:
----------------------------------------
The discussion continued on the mailing list, however I'm not sure there is an
archive as the mailing list changed of address.
Anyway, it was a misunderstanding of the API on my part. Trying to reuse
axutil_log_create with my custom implementation was my mistake.
The conclusion is that the API has already all the flexibility needed. I'll
post some sample code that demonstrates it.
> More flexibility in the logging subsystem
> -----------------------------------------
>
> Key: AXIS2C-1455
> URL: https://issues.apache.org/jira/browse/AXIS2C-1455
> Project: Axis2-C
> Issue Type: New Feature
> Components: util
> Affects Versions: 1.6.0, 1.7.0, Current (Nightly)
> Reporter: Olivier Mengué
>
> I am integrating Axis2/C in a bigger application that has its own logging
> system. I would like to redirect Axis2/C logging operation to that logging
> system instead of files.
> In 1.6.0, Axis2/C is only able to log to files. Logging to files using the
> stdlib is hardcoded in the logging internal structures, and avoiding file
> opening is not possible.
> It should be possible to completely replace the logging operations, not just
> "write" and "free". The base API should be more abstract, and the file
> handles should be in the default logging implementation, not embeded in the
> base API.
--
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]
