Subject:watch doesn't work with variables (100g) Author:David Rees Date:10 Oct 2002 04:15 PM
Watch doesn't seem to work with variables as described. I don't see any values for any xpath expression that uses variables. This happens for built-in or the internal Xalanj. I've attached a screenshot.
Subject:watch doesn't work with variables (100g) Author:David Rees Date:10 Oct 2002 04:43 PM
This seems to be fixed in 100k (I was using 100h). I hadn't realized there was a newer beta version because the "check for newest beta" was not reporting it.
thanks,
d
On 10/10/02 4:15:36 PM, David Rees wrote:
>Watch doesn't seem to work
>with variables as described. I
>don't see any values for any
>xpath expression that uses
>variables. This happens for
>built-in or the internal
>Xalanj. I've attached a
>screenshot.
>
>thanks,
>
>dave
Subject:Re: watch doesn't work with variables (100g) Author:Minollo I. Date:10 Oct 2002 05:16 PM
Build updates don't trigger the new version available communication; we did
that originally to avoid noise, but we should probably revise this policy.
Anyway, 100k may have addressed issues in the XalanJ/Saxon space, but not
in the internal processor. In any case, what Ivan suggested still stands.
If you type $myVar, the watch window will display the value of the myVar
variable. If you type myVar, the watch window will display the result of
the 'myVar' XPath expression in the current context, which in most cases
won't be what you would expect.
Subject:RE: watch doesn't work with variables (100g) Author:Ivan Pedruzzi Date:10 Oct 2002 04:48 PM
Dave,
Looking to the picture it seems to me you forgot the $ prefix.
You should type $current, $oldStartElement and so for.
Ivan
> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager]
> Sent: Thursday, October 10, 2002 4:31 PM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: watch doesn't work with variables (100g)
>
>
> From: "David Rees"
>
> Watch doesn't seem to work with variables as described. I
> don't see any values for any xpath expression that uses
> variables. This happens for built-in or the internal Xalanj.
> I've attached a screenshot.
>
> thanks,
>
> dave
>
>
>
> To reply: mailto:stylus-studio-tech.5763@edn.exln.com
> To start a new topic: mailto:stylus-studio-tech@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>
>