|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #33411 Problems sending long objects via SOAP
Submitted: 2005-06-20 21:53 UTC Modified: 2005-06-28 01:00 UTC
Avg. Score:5.0 ± 0.0
Reproduced:2 of 2 (100.0%)
Same Version:0 (0.0%)
Same OS:1 (50.0%)
From: abertolli at innovim dot com Assigned:
Status: No Feedback Package: SOAP related
PHP Version: 5.0.4 OS: Linux 2
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2005-06-20 21:53 UTC] abertolli at innovim dot com
When connecting to SOAP services created by another language such as Java, PHP cannot handle Long objects.  The problem is that PHP isn't able to cast to long, and therefore doesn't know how to match up the type in the WSDL.  It ends up trying to send as an int which is rejected on the remote side.

It is important to support long objects because they can be set to NULL unlike primitives.

This is using the SOAP extension.

Reproduce code:
The WSDL would look something like this:

<complexType name="AreaInfo">
<element name="id" type="soap11-enc:long"/>

Expected result:
To get a SOAP response

Actual result:
There is no SOAP response


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2005-06-20 22:40 UTC]
Please try using this CVS snapshot:
For Windows:

 [2005-06-28 01:00 UTC] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat Jul 13 22:01:29 2024 UTC