: But I am now hitting the similar problem with XSLT. The : following XSLT code can't retrieve the value of "hl.fl" : parameter even though the similar code for other parameter : works. : : <xsl:variable name="hlfl" : select="response/responseHeader/[EMAIL PROTECTED]'params']/[EMAIL PROTECTED]'hl.fl']" : />
i just added that snipped to the example.xsl, and then echoed the value of $hlfl later in the page and it worked fine for me -- but only when using the "version=2.1" param since the XmlResponseWriter format version change from 2.1 to 2.2 chnges the responseHeader format to be a named list like everything else, perhaps this will work better for you... <xsl:variable name="hlfl" select="//response/[EMAIL PROTECTED]'responseHeader']/[EMAIL PROTECTED]'params']/[EMAIL PROTECTED]'hl.fl']" ..that will match the XML version=2.2 format (which is the default in the trunk) : I really don't think using a dot in variable names : is a good idea. thinking of it as a variable name is a bad idea, becuase it is not a variable name, it's a URL querystring/CGI paramater name. when modeling a URL (regardless of language) param names should never be treated as "variables" they should be treated as string keys in "map" like data structures -- any character is legal: periods, spaces, ampersands, equals signs ... they are all fair game, so languages that have any sane concept of a URL know better then to treat them as variable names. -Hoss
