During the SAP Teched 2010, SAP has caused some commotion when it gave Java Web Dynpro the so called ‘kiss of death’. Basically, active development on the Java Web Dynpro technology will be stopped and the next edition of NetWeaver will be the last major enhancement for Web Dynpro Java. The implicit message from SAP seems to be: the future of Web Dynpro lies in ABAP.
Since a few years, SAP maintains two branches of UI technology, built on totally different technical foundations: ABAP Web Dynpro and Java Web Dynpro. This situation exists for historical reasons, but for me it always made little sense to build and support the same technology twice in different stacks.
Impact on Netweaver BPM
Now that the dust has settled a bit, what does the ‘death’ of Java Web Dynpro mean for Netweaver BPM technology which is just starting to mature?
Hello World! 