Bug #49169 [Com]: SoapServer calls wrong function, although "SOAP action" header is correct

From: Date: Wed, 24 Oct 2018 21:44:03 +0000
Subject: Bug #49169 [Com]: SoapServer calls wrong function, although "SOAP action" header is correct
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-217674@lists.php.net to get a copy of this message 
Edit report at https://bugs.php.net/bug.php?id=49169&edit=1

 ID:                 49169
 Comment by:         mwintoch at wp dot pl
 Reported by:        jeroen at asystance dot nl
 Summary:            SoapServer calls wrong function, although "SOAP
                     action" header is correct
 Status:             Verified
 Type:               Bug
 Package:            SOAP related
 Operating System:   linux
 PHP Version:        5.3.3
 Block user comment: N
 Private report:     N

 New Comment:

This issue still exists on PHP 7.2, even with Zend\Soap 2.7


Previous Comments:
------------------------------------------------------------------------
[2016-07-28 22:33:27] mail at mailforspam dot com

7 years... I really hate you core team.

------------------------------------------------------------------------
[2016-01-13 18:04:22] ben at redsnapper dot net

Still not fixed. Extremely annoying.

------------------------------------------------------------------------
[2013-04-08 18:06:08] php dot net at exby dot com

I still can't believe this is not fixed. Can we get someone from php.net to respond to this -
whether or not there is any intention to fix this?? I really don't want to use JAVA for setting
up services 
but so far PHP's inability to correctly understand the soapaction header is forcing me in this
direction.

And no, I can't switch to rpc/encoded and it's not a 'fix'. Document Literal is
by far the more used paradigm outside of the PHP world - and web services are often implemented in
the Enterprise space.

Please, somebody fix this.

------------------------------------------------------------------------
[2013-02-24 20:05:03] reto at casserini dot com

Another workaround. 

Instead of

    <message name="getCourses">
        <part name="parameters" type="xsd:int"/>
    </message>
    <message name="getUsers">
        <part name="parameters" type="xsd:int"/>
    </message>

which always leads to a call of the first operation "getCourses", I define two new types:

    <xsd:element name="getCoursesInput" type="xsd:int"/>
    <xsd:element name="getUsersInput" type="xsd:int"/>

and use them for the messages:

    <message name="getCourses">
        <part name="parameters" element="tns:getCoursesInput"/>
    </message>
    <message name="getUsers">
        <part name="parameters" element="tns:getUsersInput"/>
    </message>

works fine for me.

------------------------------------------------------------------------
[2012-10-12 19:30:12] mrice at canarylabs dot com

This bug appears to still be present in 5.3.6.

I need help on how to use the workaround of: “Actually I circumvented the 
problem, by putting all the message definitions in separate files, which I then 
include in the schema-part of the wsdl.
Then PHP can handle the soap:binding style="document" just fine, so the problem 
only occurs if the names are duplicated within the same file.”

We are recreating a web service from an already existing one and existing 
clients need to work.

How do you include the message definitions in separate files as stated above?

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=49169


--
Edit this bug report at https://bugs.php.net/bug.php?id=49169&edit=1

Thread (23 messages)

« previous php.bugs (#217674) next »