I get that when I don't include a correct xmlns declaration for my template. Does your namespace declaration match what's expected exactly?
On Wed, Jun 3, 2009 at 3:43 PM, Cassie <[email protected]> wrote: > I have a gadget that is doing server side data pipelining and has a request > that looks like this: > > <os:DataRequest key="settings" method="extensions.get" > command="getSettings" > ... /> > > This is alongside an os:PeopleRequest, os:ViewerRequest etc. The normal > people and viewer requests are working fine for me, but the datarequest is > failing because on PipelinedData line 365 inside of createDataRequest the > method uses the call attrNode.getLocalName(). > > getLocalName() continually returns null for all of the attributes on that > datarequest on my box. getNodeName() however returns the right thing - > "command", "key" etc > > So, I'm wondering if anyone else has seen this problem and if it would be > an > issue to switch from getLocalName to getNodeName. (Note the other request > parsing calls know what the names of the attributes are so they call > getAttribute(name) which isn't affected here) > > Thanks! > - Cassie >
