Error when starting WD-Application without active scripting

Question

Hello together,
at the moment I am writing a thesis about web dynpro and time is nearly gone...
In the article:
The Basic Facts About Web Dynpro - What Does It Do and How Does It Work?
by Dr. Peter Tillert,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/91b8c890-0201-0010-c787-be96f6fade89
I´ve read about server-side rendering and  client-side rendering ( text under figure 6 ).
Now I´ve got the following problem:
Usually I use IE7 for testing my WD-Applications with enabled active scripting.
Now I thought I disable active scripting on my client in order to test server-side rendering
of plain html...
I only get the error: WebDynpro Exception: Client Does Not Support JavaScript
What´s wrong? I expected an other result... Thought WD is sooo flexible ???
Many greetings,
Oliver

Answer 1

The article that you have chosen is rather old and represented some of the design goals of Web Dynpro back in 2004 before the project was completed.  I see other items in the article (like the Dynpro/Web Dynpro integration for ABAP) that were dropped before the final release of the product as well.
I believe that quote you focused in on was:
"While smart browsers (Internet Explorer as of version 5.5 and Netscape Navigator as of version 7.0) can run our client-side JavaScript, future versions of the Web Dynpro runtime will send server-side generated HTML without any scripting to every other browser."
What you need to understand is that the idea of having a clear separation between the CSF and the SSF was an original design aspect of Web Dynpro that was elimated before the final product was delivered to market.  Part of the reasoning is that mainstream browser usage advanced to the point where the need to support non-JavaScript browsers was largely a moot point by the time Web Dynpro was released.  Therefore producing a rendering engine that has no scripting no longer had much value.  So deactiving scripting support in Web Dynpro today, does result in the error message that you received by design.  You can always check the latest supported browser versions for Web Dynpro by viewing the Platform Availability Matrix on the Service Marketplace.
Using certain Application and URL parameters there certain features of the client side scritping that can be turned off:
http://help.sap.com/saphelp_nw70/helpdata/EN/7b/fb57412df8091de10000000a155106/frameset.htm
For instance you can deactivate the Delta Rendering (DOM Infusion of UI elements). 
Web Dynpro rendering is still abstracted and very flexible.  Today we focus this multi-client rendering approach on vastly different rendering technologies.  We can output to the HTML with JavaScript and AJAX, to Adobe Flex and to the NetWeaver Business Client (.Net 3.0 runtime). Here are some screenshots that show the same WD application running in these three very different environments.
NWBC:
http://www.flickr.com/photos/tjung/2685619882/
Flex:
http://www.flickr.com/photos/tjung/2684804211/
HTML/JavaScript:
http://www.flickr.com/photos/tjung/2685619854/