[jira] Closed: (AXISCPP-791) Handling missing operationRequestMap correctly

["Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXISCPP-791?page=all ]
     
Samisa Abeysinghe closed AXISCPP-791:
-------------------------------------

    Fix Version: 1.6 Alpha
     Resolution: Fixed

Fixed the problem by throwing an exception if the operationRequestMap is missing.

> Handling missing operationRequestMap correctly
> ----------------------------------------------
>
>          Key: AXISCPP-791
>          URL: http://issues.apache.org/jira/browse/AXISCPP-791
>      Project: Axis-C++
>         Type: Improvement
>   Components: WSDD Processing
>     Versions: current (nightly)
>     Reporter: Henrik Nordberg
>     Assignee: Samisa Abeysinghe
>      Fix For: 1.6 Alpha

>
> Currently if you are missing the operationRequestMap entry in the WSDD file, the call to
>         const char* WSDDService::getOperationForRequest(const char* request) const (wsddservice.cpp)
> returns 0. This causes a crash on this line
>         AxisString operationToInvoke = m_pService->getOperationForRequest(sOperation.c_str());
> in int ServerAxisEngine::process(SOAPTransport* pStream) (serveraxisengine.cpp), because you cannot create a std::string from 0.
> I suggest that getOperationForRequest() throws an exception that explains that this situation may be caused by a missing or incorrect operationRequestMap entry in the wsdd file (including as much information as possible, but certainly the path to the wsdd file and the name of the service in question). This question is then (hopfully?) caught and an error is reported in the log.

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