[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-c-dev
Subject:    [jira] Resolved: (AXIS2C-121) Log implementation does not go
From:       "Samisa Abeysinghe (JIRA)" <jira () apache ! org>
Date:       2007-03-29 13:56:25
Message-ID: 6483825.1175176585265.JavaMail.jira () brutus
[Download RAW message or body]


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

Samisa Abeysinghe resolved AXIS2C-121.
--------------------------------------

    Resolution: Fixed
      Assignee: Samisa Abeysinghe  (was: Dinesh Premalal)

It goes through ops. Ops is statically allocated

> Log implementation does not go through ops
> ------------------------------------------
> 
> Key: AXIS2C-121
> URL: https://issues.apache.org/jira/browse/AXIS2C-121
> Project: Axis2-C
> Issue Type: Improvement
> Components: util
> Environment: Linux/Windows
> Reporter: Nabeel Yoosuf
> Assigned To: Samisa Abeysinghe
> Priority: Minor
> Fix For: 1.0.0
> 
> 
> The log implemenation does not go through ops; as a result of that a user cannot \
> plug his/her log implementation to use the engine. It would be better if we can \
> have it aleast for Linux since there's a known problem with accessing fucntions \
> with variable no of arguments through macros in windows.

-- 
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


[prev in list] [next in list] [prev in thread] [next in thread]