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 "Fred Preston (JIRA)" <ax...@ws.apache.org> on 2006/04/05 15:04:59 UTC

[jira] Closed: (AXISCPP-29) WSDDDocument::ParseDocument doesn't error check

     [ http://issues.apache.org/jira/browse/AXISCPP-29?page=all ]
     
Fred Preston closed AXISCPP-29:
-------------------------------


> WSDDDocument::ParseDocument doesn't error check
> -----------------------------------------------
>
>          Key: AXISCPP-29
>          URL: http://issues.apache.org/jira/browse/AXISCPP-29
>      Project: Axis-C++
>         Type: Bug

>   Components: Deployment / Registries
>     Versions: current (nightly)
>  Environment: Operating System: Other
> Platform: Other
>     Reporter: Sam Lang
>     Assignee: Axis Developers Mailing List

>
> WSDDDocument::ParseDocument(const AxisChar* sWSDD)
> This function won't return FAIL if the wsdd file has formatting errors 
> (missing begin/end element tags) or even if the sWSDD pathname string 
> is invalid (the wsdd file doesn't exist).  
> This could all be easily fixed if the WSDDDocument:fatalError callback
> did something useful (its currently empty).  Also, ::warning and ::error
> should probably also do something useful.  
> Given that there's no way to pass the exception back to the user function 
> (in this case ParseDocument), there will probably need to be some kind
> of error member in WSDDDocument that can be set in fatalError, and then
> checked later (something like in XMLStreamHandler).

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