axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damitha Kumarage (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2C-1301) Can not change the axis2c logger.
Date Tue, 23 Dec 2008 08:50:44 GMT

     [ https://issues.apache.org/jira/browse/AXIS2C-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Damitha Kumarage resolved AXIS2C-1301.
--------------------------------------

    Resolution: Fixed

This is fixed

> Can not change the axis2c logger.
> ---------------------------------
>
>                 Key: AXIS2C-1301
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1301
>             Project: Axis2-C
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 1.5.0
>         Environment: Linux SuSe 10, Intel Xeon 64 bits, Axis2c 1.5.0
>            Reporter: Leonardo Kausilas
>            Priority: Minor
>             Fix For: 1.6.0
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Can not change the axis2c logger because the macros AXIS2_LOG_DEBUG, AXIS2_LOG_INFO,
etc calls directly to axutil_log_impl_log_debug, axutil_log_impl_log_info, etc and never calls
to axutil_log_ops_t.write function pointer.
> If the macros calls a generic function that calls the axutil_log_ops_t.write function
pointer, everyone who wants to change the logger could create a new axutil_log_ops_t struct
initializing it with your own pointers, like the XML parser, allocator, etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message