The XML problem isn't an error in the taf, but a
problem with IIS seeing the WiTango server.
Make sure you've allowed the web service
extension for the wiis.dll (t4iis.dll Tango 2000).
Otherwise, IIS will deny a taf from
running.
Also, you're using a custom scope. Do you have
the customscope switch enabled in your WiTango server configuation?
And, In your <@FOR> tag, I saw a stop, but
not a start.
Rick Sanders
Hi,
Platform: W2003
Server, IIS 6, Witango 5.0
Has anybody run
into this before:
A simple
<@for...> </@for> metatag pair within a more complex
results action has managed to destroy my day by generating the following
(typical) IIS error output:
_______________________________________________________________________________________________
The XML page
cannot be displayed
Cannot view XML input using XSL style sheet. Please
correct the error and then click the Refresh button, or try again later.
--------------------------------------------------------------------------------
A semi colon character was expected. Error
processing resource
'http://server01/orfeo/OrfeoMA/OrfeoMAHome.taf?_action=list&...
<td
width="60%"><font size="+1"><ul><b><li><a
href=""typical" I mean that more than 90%
of the time this has been the output. The last line (<td
width="60%"><font size... ) has taken different values depending on
changes I have done to the results action, but the text it displays always
generates from totally different results actions within the
taf.
Occasionally
it has also ended with a Witango Server error -615 message and a few times it
has even worked, especially immediately after a refresh of the taf on the
browser client or starting up a new browser
window...
The <@for>
metatag typically (having tried out some million different possibilities)
looked like this:
<@for stop="<@numrows
array='@@request$arrTempGenre'>">
<@addrows array="arrArtistList" scope="user"
value="<@filter array='resultset' scope='request' expr='#GenreID = <@var
name="arrTempGenre[<@currow>,GenreID]"
scope="request">'>">
/@for
The rest of the taf
has worked fine all the time as long as this one results action was not
hit.
I even retyped the whole
results action manually, moved it to a different place in the taf, copied
everything into a new clean taf file, tried to run the <@for>
/@for metatag pair empty, restarted both server and Witango service
etc, but to no help. Commenting out the <@for> metatag pair always
resolved the IIS issue (although not giving me the correct
output).
At the end I just split my
whole results action into 3 separate actions with a "for loop" action in
between two results actions and now it works. And it's not a typing
error, I "cut and pasted" the stuff.
Ok, it now works, but I
really would like to understand the problem I hit.
Jan
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
