John,
The XML Parser (DOM implementation) has been completely replaced in Witango
5.5. This is separate to the DOM manipulation technologies XPointer and
XPath that have nothing to do with the parsing of the XML at all and are in
the next layer out from the DOM implementation and XML parsing.
We
Hi,
I think I found the answer. I replaced the Search
Action with a Direct DBMS action and the data now appears on the page. The
code's the same in the Result html.
Is there a bug in the Search action? Or a limitation?
But I can't get it to fail on another server.
Ted
From: Ted Wolfl
I Agree,
I ran into another long term issue recently where I needed to update
Attributes on the Root tag, can't do it using XPOINTER in Witango 5 or 5.5,
I had to create the root tag manually and fillin the guts.
It looks like they put there energies into implementing XPATH and kept
XPOINTER the
Because the code I'm writing has to run on 5 now and on 5.5 later.
Having it fixed in 5.5 wouldn't have changed my approach that much,
because it still wouldn't work now. I'm just diappointed that the new
server doesn't have better support. I thought that all the XML stuff
was redone. But t
Well if you are going to 5.5 why not just go with XPATH ;-) and drop
XPOINTER
Ben Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller
Available for Witango Developement
-Original Message-
From: John McGowan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 27, 200
Thank you Mike... That's not what I was hoping for...
/John
Mike Scally wrote:
Hi John,
We are running Witango 5.5.003 Liquorice (Win32) and I get the same
results.
id=
othertag=Y
Mike.
-Original Message-
From: John McGowan [mailto:[EMAIL PROTECTED]
Sent: 27 October 2004 15:39
To: [EMAIL
Hi John,
We are running Witango 5.5.003 Liquorice (Win32) and I get the same
results.
id=
othertag=Y
Mike.
-Original Message-
From: John McGowan [mailto:[EMAIL PROTECTED]
Sent: 27 October 2004 15:39
To: [EMAIL PROTECTED]
Subject: Witango-Talk: Old Witango XML Bug
Could someone on thi
Could someone on this side of the globe help me out with something.
There is a bug that exists up to Witango 5.0. For some reason the DOM
parser can't seem to find elements named "id"
For example, the following code
<@assign Name="domvar" Scope="Local"
Value=<@Dom Value="XY">
>
id=<@ELEMENTVALU
Hi,
I have a search
action in a taf that is working off and on. Webserver is Win2003 with
Witango 5.5, sql server database is on another Win2003 server. Both
servers are up-to-date. The search action is using dynamic data
source. When the data source is switched to sql server database
