How does WDA compare to other technologies?

	Web Dynpro for ABAP	Web Dynpro for JAVA	Business Server Pages (BSP)	JAVA Server Pages (JSP)	Interactive Forms (Adobe based)	HTML Business for Java (HTMLB )	Mobile Infrastructure
Presentation within SAP GUI	very limited, not officially supported
Presentation within SAP NetWeaver Portal	X	X	X	X	X	X
Presentation on Mobile Devices (staying online)		X	X	X	X	X
Presentation on Mobile Devices (loosing connection to the server)					X		X
Integration of JavaScript Programs			X	X
Usage of Web Services	X	X	X	X	X	X
Development Environment	ABAP Workbench (SE80)	SAP NetWeaver Developer Studio (Web Dynpro Perspective)	ABAP Workbench (SE80)	SAP NetWeaver Developer Studio (J2EE Perspective)	SAP NetWeaver Developer Studio (Web Dynpro Perspective)	SAP NetWeaver Developer Studio (Enterprise Portal Perspective)
Available since	SAP NetWeaver 2004s (Web Application Server 7.0)	SAP NetWeaver 04 (Web Application Server 6.40)	Web Application Server 6.10	Web Application Server 6.20	SAP NetWeaver 2004s (Web Application Server 7.0)	Web Application Server 6.20
Advantage	- integrated in SE80 - good chance to standard development technology - close to ABAP functionality - no separate development environment needed - no SAP NetWeaver Portal needed - quick development - ALV Lists can be used	- usage of JAVA-Know in SAP world - device recognition adapts interface automatically - many different technologies available (Beans, Web Services, XMI, ...)	- integrated in SE80 - no separate development environment needed - better performance than Web Dynpro	- usage of JAVA-Know in SAP world - vast set of control elements for SAP NetWeaver Portal / Browser	-enables user interaction and user integration to business processes, without having an SAP System installed or being connected to a SAP System - easy to develop	- usage of JAVA-Know in SAP world - vast set of control elements for SAP NetWeaver Portal / Browser	- enables connecting mobile devices which are occasionally offline
Disadvantage	- JavaScript  cannot be used - no support of Mobile Devices - no device recognition yet - some GUI elements are not supported yet	-  JavaScript  cannot be used - connects to ABAP function only via RFC (wrapper needed) - suffering stability problems -separate development environment & 3?tier landscape needed	- development more complex than Web Dynpro	- development more complex than Web Dynpro and BSP - problems with debugging, testing, error-handling -separate development environment & 3?tier landscape needed		- Most of the features have been integrated in Web Dynpro for JAVA	- separate installation, customization & administration of the Mobile Infrastructure component needed

Especially concerning the disadvantages of Web Dynpro for ABAP there are lot of enhancements expected with the introduction of SAP NetWeaver Business Client, the new GUI for SAP (e.g. support of mobile devices, at least online support