axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Preston (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Resolved: (AXISCPP-417) setTransportProperty( SOAPACTION_HEADER, "name") and service name=".." in WSDD incompatibility
Date Wed, 16 Feb 2005 09:34:44 GMT
     [ http://issues.apache.org/jira/browse/AXISCPP-417?page=history ]
     
Fred Preston resolved AXISCPP-417:
----------------------------------

    Resolution: Fixed

Update complete

> setTransportProperty( SOAPACTION_HEADER, "name") and service name=".." in WSDD incompatibility
> ----------------------------------------------------------------------------------------------
>
>          Key: AXISCPP-417
>          URL: http://issues.apache.org/jira/browse/AXISCPP-417
>      Project: Axis-C++
>         Type: Bug
>  Environment: n/a
>     Reporter: Fred Preston
>     Assignee: Fred Preston

>
> This is all about handlers.  To use a handler, you have to make sure that the name that
it was given in setTransportPorperty( SOAPACTION_HEADER, "<name>") is the same as the
<service name="<name>"... in the WSDD file.  The problem is that the name that is
saved when using setTransportProperty() is surrounded with quotes, so it becomes "<name>"
and not just <name>.  When in ClientAxisEngine::process (ClientAxisEngine.cpp line 67
onwards), if the "<name>" does not have a # embedded then the pchService still has the
quotes around it when it is passed to g_pWSDDDeployment->getService() and so can never
be found in the list.  If however, the name was set with a # in setTransportPorperty(), then
when in ClientAxisEngine::process, the name is processed differently and the initial quote
is removed prior to calling g_pWSDDDeployment->getService(), which can then find the service
name and so pService is set correctly.  I would suggest, for consistent behaviour, if the
name does not have a #, the quotes should be removed before calling g_pWSDDDeployment->getService().

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


Mime
View raw message