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 ji...@apache.org on 2004/04/29 07:06:53 UTC
[jira] Created: (AXISCPP-70) client side log handling
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-70
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-70
Summary: client side log handling
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-C++
Components:
Transport (Client)
Versions:
1.1 Final
Assignee:
Reporter: Sevwandi Abeysinghe
Created: Wed, 28 Apr 2004 10:06 PM
Updated: Wed, 28 Apr 2004 10:06 PM
Environment: All Platforms
Description:
According to current Axis architecture, the location of the log file is read from axiscpp.conf by the axis engine. This is conceptionally wrong on the client side: the client must have a valid config (also
specifying location of a server.wsdd) to avoid segfaults (Zolyomi Istvan previously has sent a bug report about this).
This should be changed: the client should not have such a
config file since it does not have an Axis deployment directory at all. Maybe the best solution would be to specify the logfile in a parameter of the client programs. As an alternative, it could be stored in an environment variable.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXISCPP-70) client side log handling
Posted by ax...@ws.apache.org.
Message:
The following issue has been closed.
Resolver: John Hawkins
Date: Fri, 15 Oct 2004 3:05 AM
No response so closing
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-70
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-70
Summary: client side log handling
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Axis-C++
Components:
Transport (Client)
Versions:
1.1 Final
Assignee:
Reporter: Sevwandi Abeysinghe
Created: Wed, 28 Apr 2004 10:06 PM
Updated: Fri, 15 Oct 2004 3:05 AM
Environment: All Platforms
Description:
According to current Axis architecture, the location of the log file is read from axiscpp.conf by the axis engine. This is conceptionally wrong on the client side: the client must have a valid config (also
specifying location of a server.wsdd) to avoid segfaults (Zolyomi Istvan previously has sent a bug report about this).
This should be changed: the client should not have such a
config file since it does not have an Axis deployment directory at all. Maybe the best solution would be to specify the logfile in a parameter of the client programs. As an alternative, it could be stored in an environment variable.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira