We all know AXL isn't exactly as great as it's hyped to be and since we're all bound to run into the same issues, why not compile a list of what's wrong. It'll also make pressuring Cisco into fixing AXL once and for all easier.
So I'll go first:
User: the <firstname> and <lastname> element are written <firstName> and <lastName> respectively when you make a getUser despite the documentation saying otherwise. adduser and updateuser use the proper notation.
getPhone: there's no phoneTemplate in the response but a phoneTemplateID.I suppose that applies to other elements as well but in some instances, the name is returned instead of the actual element (if anybody can figure out a logic on that please do let me know)
addPhone: I can't get the interface to stop complaining when I add a element.. I added it just below and the response is: misspelled or out of order.. so I tried before userLocale, and I got the same error. The string is a 1:1 copy from one I got from a getPhone.If I leave out the parameter I have no problem adding a new device.
Hmm.. where's the delete post button? Turns out my DB was buggered and the phone I was using as a template, while working, couldn't be modified anymore.
I'll send you one of my commands when I'm through with testing. Right now I have another one in 4.1.3
The docu says digitDiscardInstruction/digitDiscardInstructionName is a mandatory field in a getRoutePattern response. Yet all my route patterns return neither element.
The same also applies to the routeFilter/routeFilterName element. The funny thing is that if you do a getRoutePattern and do not use the uuid as identifier, the service expects a routePartition or it'll return the usual "expected element not found" error.. so basically I have to give an empty routeFilterName string and then I get back an XML document without any routeFilter* elements.
And the fun just keeps on going when I turn to the addRoutePattern command. Of course, when I use addRoutePattern, it won't work without a digitDiscardInstruction* and routeFilter*. But if I add an empty digitDiscardInstructionName and routeFilterName element, the command succeeds even though neither element is declared as nullable.
SELECT Name FROM Device WHERE LoginTime IS NULL AND fkPhoneTemplate IS NOT NULL AND tkClass = 1 AND LoginUserid = "asve"
(the query would read out any physical devices where the user avse is set as owner id)
This returns an ODBC error saying that "avse" isn't a valid column name.
Do the same but replace " with ', and you get an empty result, instead of the a response containing xsi:nil that you usually get when making a query that returns no results.
Needless to say I use xml encoding on the query, so ' becomes ' - but I tried without and strangely enough, the query still passes, even though it's not valid XML.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
