Summary | SOAP interface returns incomplete/wrong return values |
Queue | Horde Framework Packages |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | chuck (at) horde (dot) org |
Requester | meyer (at) mesw (dot) de |
Created | 02/27/2007 (6713 days ago) |
Due | |
Updated | 02/11/2008 (6364 days ago) |
Assigned | 02/11/2008 (6364 days ago) |
Resolved | 02/11/2008 (6364 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
Assigned to Chuck Hagenbuch
Taken from Jan Schneider
State ⇒ Resolved
got it working flawlessly with SoapServer, I guess it's a PEAR SOAP
issue.
State ⇒ Assigned
you know of that are in our code instead of PEAR SOAP...
tried a new PHP 5 SoapServer backend. If you're using PHP 5, could
you give it a shot? listCalendars, for example, works perfectly for
me with it:
http://lists.horde.org/archives/cvs/Week-of-Mon-20080204/074710.html
sorry, but at the moment I don't run Horde anymore at all, so I won't
be of much help here. But thanks for looking at the bug!
Best regards
Markus
State ⇒ Feedback
tried a new PHP 5 SoapServer backend. If you're using PHP 5, could you
give it a shot? listCalendars, for example, works perfectly for me
with it:
http://lists.horde.org/archives/cvs/Week-of-Mon-20080204/074710.html
State ⇒ Assigned
Priority ⇒ 1. Low
State ⇒ Unconfirmed
New Attachment: soap_exchange.txt
Queue ⇒ Horde Framework Packages
Summary ⇒ SOAP interface returns incomplete/wrong return values
Type ⇒ Bug
APIs while e.g. XML/RPC works fine for those APIs.
Example 1: when calling "calendar.listCalendars()" always an empty
list is returned though there actually are calendars which can be
accessed by this user (the same call works fine using the XML/RPC API).
Example 2: when calling "calendar.exportCalendar()" on a calendar
which has special chars in the events (e.g. umlauts), the special
chars are returned in a codepage charset although the XML response
generated by Horde designates the encoding as "UTF-8". XML validators
trying to interpret Horde's response then reject the XML as invalid.
See the attachment for protocol dumps for the two examples.