Aftermath: Kiss of death for Webdynpro Java
SAP mentor Thorsten Franz published a blog on SDN to discuss & share the future of Webdynpro Java. Kiss of death for Webdynpro Java as he has named the blog, explains SAP’s view on using Java as a UI development technology for future applications. A lot of heat has been generated and I have seen people exchanging blog links to everyone in the team. Blog has scared WDJ developer community and forced them to think about the future development road-map.
As he writes “At SAP TechED 2010, SAP announced very discreetly that Web Dynpro Java had reached the state of maturity“. Though SAP will continue to support and respond to OSS message, no further improvements or version release will be done to the existing WDJ framework. What does this means to developers and people employed in the skill set? Answer is simple, move on and learn something new.
SAP would certainly try to push other UI development tools such as Webdynpro ABAP. Many business packages are getting released in WD ABAP instead of WD Java.
Wait! don’t think SAP is discontinuing with Java. Yet another blog from John Reed in discussion with SAP mentor Yariv Zur says that SAP is neither trying to back-off from Java nor WDJ is dead at SAP. Neither is true.
However, for Business Suit applications, SAP will only use ABAP. SAP is not developing many Java-based UIs. Also Visual Composer and Webdynpro Java applications will be supported until 2018. Even if we use Netweaver 7.3 for WDJ development, it will certainly be supported until 2018. This means there’s no call for urgency as of now. However, it’s good time that we start investing time into other UI development technologies like WD ABAP, Advanced scripts like jQuery and lightweight technologies like Ajax.
Major disadvantage of using WD ABAP is its lack of support for mobile applications. Where as on the other hand, WD Java is stable and proven for mobile applications and extensions. However, it seems SAP has decided to take another approach to solve this problem. They have entered into a strategic partnership with Sybase for developing and extending its Business Suit applications across the mobile platforms. Let’s see if this really transforms SAP’s vision and road-map of mobility.
On ending note, SAP will only stop any further modifications and enhancements in WD Java framework. However, as NW 7.3 is just about to release, they will continue to support WD Java until 2018.
More UIs developed in WD ABAP should not mean that SAP’s backing off from Java. But it certainly gives indication that WD Java is matured and developers should start acquiring new age technologies.
Filed Under: Latest in SAP
Good that you pick this up outside SAP. Why do you expect an SAP Mentor “explains SAP’s view on using Java as a UI development technology for future applications”? A blog of an SAP mentor is a personal expression of opinion, in this case – as e.g. the comment by Yariv shows – the blog might not be the result of thorough investigation of facts.
If you want to look at SAP’s view, go to http://www.virtualsapteched.com, watch session amd sheets “CD201″. Nothing done discreet and nothing kissed, but a consequent evolution from this Java 1.4 code generation tool that shows its age towards up-to-date technology.
If Thorsten’s blog makes more WD Java developers to learn the current standards in the Java world like JSF (and to try out WD Java on other Web Servers), he has done a good job.
Like or Dislike:
1 
0
@javainsel:
One thing I’d certainly agree is that, it’s an opinion expressed by SAP mentor and we cannot plan a road map based on a blog. However, Thorsten as effectively connected with developer community’s views and what’s that SAP eyeing on.
Though there’s no harm in continuing with WDJ, but it’d be great to have different skill sets like JSF, Ajax, WDA & other advance scripting. SAP, without any doubt,is trying to make UIs more flexible, easy to implement and lightweight. On top of that, they certainly want a customer to leverage existing investments & infrastructure. Perhaps that’s why SAP is pushing WD ABAP big time.
Thanks for stopping by and adding value to the discussion.
Ameya
Like or Dislike:
1 
0
I think all this Java cautiousness is due the Oracle pressing patents against Google. Even Apple has stopped contributing the jvm/jdk. The JCP and the JSR members are also very cautious because they have no clue what Oracle is actually planning to do. Oracle might even ask for a licensing fee for every jvm implementation.
That’s why SAP, which as far has I know has loads code invested in Java (ME/SE/EE) might be looking for more open alternatives.
Like or Dislike:
1 
0
@Rohan
Yes, SAP does have loads of investments done into Java developments. Thay want to reduce the dependency on any third party software for their Netweaver infrastructure. As exactly pointed by you that oracle is trying to patent and may also ask for license fee from current users. This could be driving factor for this decision.
However, this situation should not be misinterpreted. Java is there to stay on SAP’s road-map. At least till 2018.
Ameya
Like or Dislike:
1 
0