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 "John Hawkins (JIRA)" <ax...@ws.apache.org> on 2005/08/22 15:21:08 UTC

[jira] Closed: (AXISCPP-275) Service information extractor

     [ http://issues.apache.org/jira/browse/AXISCPP-275?page=all ]
     
John Hawkins closed AXISCPP-275:
--------------------------------

    Fix Version: 1.5 Final
     Resolution: Fixed

(Visible to axiscpp-developers)


> Service information extractor
> -----------------------------
>
>          Key: AXISCPP-275
>          URL: http://issues.apache.org/jira/browse/AXISCPP-275
>      Project: Axis-C++
>         Type: New Feature
>   Components: Basic Architecture
>     Reporter: John Hawkins
>      Fix For: 1.5 Final

>
> We should set up both WSDL2Ws and the client and server code to extract information about a users environment.
> For example in WSDL2Ws we could have a -service option that prints out (to a log?) the runtime information. This would show us such things as their classpath, what version (build) of WSDL2Ws they are running, what level of pre-reqs they have etc.
> We can do the same for the client code and server code except that this information should always be output to the trace file when debug is "on". Information can include - which libraries are being called and their build levels, what levels of the pre-reqs are being called etc.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira