Comments on: Webdynpro for Java or Webdynpro for ABAP? http://www.sapfrontend.com/webdynpro-for-java-or-webdynpro-for-abap/ Accessing SAP in this brave new open world Thu, 28 Aug 2008 12:22:34 +0000 http://wordpress.org/?v=2.5 By: andres http://www.sapfrontend.com/webdynpro-for-java-or-webdynpro-for-abap/#comment-6184 andres Thu, 14 Aug 2008 17:30:20 +0000 http://www.sapfrontend.com/webdynpro-for-java-or-webdynpro-for-abap/#comment-6184 I am a developer and desing iviews between abap and java i developer in java webdynpro and make de rfc in abap and is not very dificult. Only just as we're eager and you can achieve good results. I am a developer and desing iviews between abap and java i developer in java webdynpro and make de rfc in abap and is not very dificult. Only just as we’re eager and you can achieve good results.

]]> By: PH http://www.sapfrontend.com/webdynpro-for-java-or-webdynpro-for-abap/#comment-6168 PH Tue, 05 Aug 2008 15:08:27 +0000 http://www.sapfrontend.com/webdynpro-for-java-or-webdynpro-for-abap/#comment-6168 As a SAP Basis Admin ( > 10 years experience ) its still a mistery to me why SAP ever launched the Java initiative. I mean, the SAP JRE, requires huge maintenance efforts, is hard to configure and tune, and the performance is rediculously slow as compared to an ABAP stack. The Java Development Framework is a study in complexity. Was that perhaps the real reason for Shai Agassi's resignation ? The failure to deliver a fast, scalable and cheap JAVA platform ? Allthough in the ABAP context, the Webdynpro framework doesn't have the freedom that BSP have, it enforces a kind of uniformity in the code and GUI look & feel. The only drawbacks are the cumbersome explicit coding required for the value transport of the screenvariables to/from the context and the fact that you cannot use page frame's as with BSP's. As a SAP Basis Admin ( > 10 years experience ) its still a mistery to me why SAP ever launched the Java initiative. I mean, the SAP JRE, requires huge maintenance efforts, is hard to configure and tune, and the performance is rediculously slow as compared to an ABAP stack. The Java Development Framework is a study in complexity. Was that perhaps the real reason for Shai Agassi’s resignation ? The failure to deliver a fast, scalable and cheap JAVA platform ?
Allthough in the ABAP context, the Webdynpro framework doesn’t have the freedom that BSP have, it enforces a kind of uniformity in the code and GUI look & feel. The only drawbacks are the cumbersome explicit coding required for the value transport of the screenvariables to/from the context and the fact that you cannot use page frame’s as with BSP’s.

]]> By: rj http://www.sapfrontend.com/webdynpro-for-java-or-webdynpro-for-abap/#comment-6166 rj Tue, 03 Jun 2008 06:30:59 +0000 http://www.sapfrontend.com/webdynpro-for-java-or-webdynpro-for-abap/#comment-6166 Both sucks including SAP itself. I've done some client projects and because of limitation of not able to use javascript we could not fulfill simple client requirements. In WDJ the model is still ABAP RFC calls and so if there is need to change something important, you need ABAPERS. They have complicated things so much by including both Enterprise scale language Java and ABAP that as a developer I get frustrated to do what and where ! UI in Java and model in ABAP. Sucks big time :( Both sucks including SAP itself. I’ve done some client projects and because of limitation of not able to use javascript we could not fulfill simple client requirements. In WDJ the model is still ABAP RFC calls and so if there is need to change something important, you need ABAPERS.

They have complicated things so much by including both Enterprise scale language Java and ABAP that as a developer I get frustrated to do what and where ! UI in Java and model in ABAP.
Sucks big time :(

]]> By: Maria http://www.sapfrontend.com/webdynpro-for-java-or-webdynpro-for-abap/#comment-3391 Maria Tue, 09 Oct 2007 23:29:34 +0000 http://www.sapfrontend.com/webdynpro-for-java-or-webdynpro-for-abap/#comment-3391 Well put. What people talked too at teched was how if you speak to someone from Palo Alto labs, they say use WDJ and people from Germany say use WDA. SAP should have given better guidelines. Well put. What people talked too at teched was how if you speak to someone from Palo Alto labs, they say use WDJ and people from Germany say use WDA. SAP should have given better guidelines.

]]>