error in AXLSoap.xsd - DirectoryNumber ist not an nonNegativeInteger

Unanswered Question
Mar 26th, 2008
User Badges:


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:element name="blfDirn" type="axlapi:XDirectoryNumber"/>

- <xsd:element name="blfDest" type="xsd:nonNegativeInteger"/>

+ <xsd:element name="blfDest" type="axlapi:XDirectoryNumber"/>


<xsd:element name="label" type="xsd:string" minOccurs="0"/>


@@ -4096,9 +4096,9 @@

PS: axlapi:XDirectoryNumber is just a String with 32 Chars

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
danielchobe Wed, 03/26/2008 - 03:29
User Badges:


but my Problem wasnt the namsespace. It was a wrong Datafielddefinition.

An it only fits if you use busyLampFields with non integer formated blfDest.

simon.ryf Wed, 03/26/2008 - 03:33
User Badges:


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?

danielchobe Wed, 03/26/2008 - 03:45
User Badges:

>Did you generate a AXIS (Java) Proxy or .NET?

I do the Requests with

>Is your getPhone (except busy LampFields) working?

yes, and now also with LampFields ;)


This Discussion