Ok, that explains that; ? I thought the console was displaying a truncated version of the parameter I was passing to the xpathSearch function, but I don't think that that is the case; it's cutting off the xpath at the comma in the contains() function call. ? pmc.showallnext "(descendant::*|following::*)[contains(@arch," ? should be: ? pmc.showallnext "(descendant::*|following::*)[contains(@arch, 'HyPHY20G')]" ? The Xpath works from the command window, but not when passed as a parameter within a config file ? <itemlabel="Show HyPHY20G"command="pmc.showall"parameter="(descendant::*|following::*)[contains(@arch, 'HyPHY20G')]"></item> ? I've fixed it by moving the xpath to the place where the xpathSearch command is actually called and just passing the HyPHY20G as the parameter instead of the full path (as I should have done in the first, place, I'd say). ? Jeff.
----- Original Message ---- > From: Hussein Shafie <hussein at xmlmind.com> > To: Jeff Hooker <jeff at itwriting.ca> > Cc: "xmleditor-support at xmlmind.com" <xmleditor-support at xmlmind.com> > Sent: Thursday, July 30, 2009 11:43:53 AM > Subject: Re: [XXE] xpath/setProperty oddity > > Jeff Hooker wrote: > > > > I've got an established way of finding all of the nodes in a document and > apply a property to it. It basically takes the following command: > > > > > > > > > > > > > > > messages in the console for the selectNode and setProperty commands. > >? > > > > > > -- > XMLmind XML Editor Support List > xmleditor-support at xmlmind.com > http://www.xmlmind.com/mailman/listinfo/xmleditor-support
