03-26-2008 03:02 AM - edited 03-13-2019 05:06 PM
Hello,
I found the following error in AXLSoap.xsd. While I use getPhone I got an Parser error.
The reason is simply: an blfDst is not only an nonNegativeInteger because of two reasons
1. the number can start with a zero, an Integer not
2. the number can stop with a # to dial, an Integer not
--- wsdl/AXLSoap.xsd 20 Feb 2008 09:25:18 -0000 1.2
+++ wsdl/AXLSoap.xsd 26 Mar 2008 09:55:20 -0000
@@ -820,7 +820,7 @@
<xsd:sequence>
<xsd:choice>
<xsd:element name="blfDirn" type="axlapi:XDirectoryNumber"/>
- <xsd:element name="blfDest" type="xsd:nonNegativeInteger"/>
+ <xsd:element name="blfDest" type="axlapi:XDirectoryNumber"/>
</xsd:choice>
<xsd:element name="label" type="xsd:string" minOccurs="0"/>
</xsd:sequence>
@@ -4096,9 +4096,9 @@
PS: axlapi:XDirectoryNumber is just a String with 32 Chars
03-26-2008 03:20 AM
Hello,
I wrote a Message a few weeks ago, aber a similar issue.
Have you managed to get a User successfully?
Here is my old post:
03-26-2008 03:29 AM
Hello,
but my Problem wasnt the namsespace. It was a wrong Datafielddefinition.
An it only fits if you use busyLampFields with non integer formated blfDest.
03-26-2008 03:33 AM
Hello,
Sorry for bothering...
I'm not sure if its namespace problem (my issue).
Did you generate a AXIS (Java) Proxy or .NET?
Is your getPhone (except busy LampFields) working?
03-26-2008 03:45 AM
>Did you generate a AXIS (Java) Proxy or .NET?
I do the Requests with http://de.php.net/soap
>Is your getPhone (except busy LampFields) working?
yes, and now also with LampFields ;)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide