Hi Jan, I'm impressed with your work - using XHTML :-)
My first reaction was just the same as Rick's - that IIS and Witango were erroring somehow and sending raw XML from an unprocessed TAF file. But with XHTML, you are supposed to send XML. So in fact the error is not with IIS or Witango, but how you form your XHTML. Like I mentioned, XHTML is XML - so like any XML document the ampersand '&' is a reserved character which represents character encoding/escaping for entities. When MSIE began reading your output, it encountered that ampersand in the URL you have, but like any XML/HTML encoded character, it expects a semi-colon to end the entity. http://213.243.183.11/orfeo/OrfeoMA/OrfeoMAHome.taf?_action=list&_genre=13&_static=0 So what you have to do is escape the ampersands in the URLs that you display on your XHTML webpage. The default escape/encoding/entity sequence for an ampersand is & In your Witango code, where you are writing the ampersand, hardcode them so your URL should look something like the following: http://213.243.183.11/orfeo/OrfeoMA/OrfeoMAHome.taf?_action=list&_genre=13&_static=0 There are few different ways to handle this, but try hardcoding first because it's the simpliest to implement. Hope this helps. Cheers....... Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community --------------------- XML-Extranet - http://xmlx.ca 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) --------------------- -----Original Message----- From: "Jan Magnusson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Date: Fri, 17 Oct 2003 03:07:22 +0300 Subject: RE: Witango-Talk: <@for> metatag generating an IIS error > Thank you Rick for the time spent on investigating this. > > I think you are right regarding the WiTango/IIS relationship. Something > makes WiTango put out some xml or whatever it might be not > understandable to > IIS. > > The problem with that IIS error message is that the information in it > relates to a totally different action within the taf not related to the > output of the action run. I started naturally at first searching for > the > problem based on this IIS error output part of the taf. It so happens > that > that error points to a results action that is in fact working all the > time > each time you list Artists from within the Classic or Entertainment > main > menu options. > > But if I do some editing within the results action containing this > <@for> > metatag then the IIS error output (the row you are referring to) will > change > !?! So then I'm looking in a new place.... > > The results action screwing things up is basically only retrieving and > sorting a resultset into an array. And the IIS error is generated > regardless > if any more actions are processed or not (even tried that too when > trying to > isolate the code causing the problem). > > And this is confusing me. Like there would be some memory > overrun/leakage or > something. How do I get in between WiTango and IIS to see what there > really > is being sent from WiTango to IIS ??? (I wouldn't really care to get > there > in between at all spending the next week digging...) > > Yes, those javascripts are also dynamic, but they work just fine (see > for > yourself on the rest of the site). > > Please explain this "custom scope" issue. There is now obviously > something > I've missed. I thought the "request" scope was equal to the old "local" > scope. At least according to the programmers manual page 97 (I think, > if I > havn't misunderstood it all....). > > Jan > -----Original Message----- > From: Rick Sanders [mailto:[EMAIL PROTECTED] > Sent: Friday, October 17, 2003 02:19 > To: [EMAIL PROTECTED] > Subject: Re: Witango-Talk: <@for> metatag generating an IIS error > > > Hey Jan, > > Firstly, did you check this out: > > Line 98, Position 109 > > It seems that it's an error that WiTango doesn't understand, and > causes a > general fault. So, IIS takes over. > > Looking at the error, it's bringing back the line, and points to the > position where the error is supposed to be: > > > 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://213.243.183.11/orfeo/OrfeoMA/OrfeoMAHome.taf?_action=list&_genr > e=13& > _static=0'. Line 98, Position 109 > > <td width="60%"><font size="+1"><ul><b><li><a > href="/orfeo/OrfeoMA/OrfeoMAHome.taf?_action=detail&_row=1">Krakow > Chamber > Orchestra</a></li></b></ul></font></td> > ----------------------------------------------------------------------- > ----- > --------------------------------^For some reason, it's pointing to the > "=" > sign in the URL. There's a closing tag missing, or an incomplete > javascript > argument somewhere in the page.Since I don't know your taf, if you have > javascript within the <@FOR> tags, make sure the javascript is also > dynamic:Non-dynamic:onMouseDown="MM_dragLayer('Prod1','',0,0,0,0,true,f > alse, > -1,-1,-1,-1,830,1155,500,'MM_goToURL(\'self\',\'test.taf?_function=add& > ProdI > D=<@COLUMN 'hp procuve.hp pt' > encoding=URL>&<@USERREFERENCEARGUMENT>\')',false,'')"> Dynamic: > onMouseDown="MM_dragLayer('Prod<@CURROW>','',0,0,0,0,true,false,-1,-1,- > 1,-1, > 830,1155,500,'MM_goToURL(\'self\',\'<@CGI><@APPFILE>?_function=add&Prod > ID=<@ > COLUMN 'hp procuve.hp pt' > encoding=URL>&<@USERREFERENCEARGUMENT>\')',false,'')"> Notice the > <@CURROW> > in the defination of the field value name. Also, the custom scope is > "request". @@request$arrTempGenre I hope this helps! Rick > > > ----- Original Message ----- > From: Jan Magnusson > To: [EMAIL PROTECTED] > Sent: Thursday, October 16, 2003 6:43 PM > Subject: RE: Witango-Talk: <@for> metatag generating an IIS error > > > Rick, > > 1. The iis/witango service is not the issue. Otherways it would not > run > at all, but everything else of the taf works. I can't just now check it > since I'm inside the firewall, but I think that if you try the > following > address you might be able to get into the application in question and > use > and try it out for yourself: > > http://213.243.183.11/orfeo > > Choose "New Artists / Classical" or "Entertainment" from the menu > and > you will see IIS stop with your own eyes. All the rest of the site > showing > up in the main frame is all the same taf but works. It's in debug mode > so > please feel free to check the variables/scopes. > > There are also some 10-15 other <@for> metatags in that same taf > all > within results actions (as I just can't stand those separate actions), > some > nested, some not, but they all work. > > 2. Do I use a custom scope ? Wasn't my intention, please let me > know > where ? > > > 3. Please see later posting on the subject and the results action > in > whole, there is for sure an ending tag and besides the lack of it > should for > sure generate an error within Witango, not IIS. > > > Jan > > -----Original Message----- > From: Rick Sanders [mailto:[EMAIL PROTECTED] > Sent: Friday, October 17, 2003 01:08 > To: [EMAIL PROTECTED] > Subject: Re: Witango-Talk: <@for> metatag generating an IIS error > > > Jan, > 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="/orfeo/OrfeoMA/OrfeoMAHome.taf?_a... > > _______________________________________________________________________ > _____ > ____________________ > > > When saying "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 > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
