Recently I had a brief discussion about NetWeaver and OpenSource with Benny Schaich, SAP’s platform evangelist for the Composition Environment. Later Benny posted a tweet on Twitter and we continued the discussion, part of which is reproduced here:
At this point, more people joined the discussion on Twitter and it gained momentum. Two days later, Benny posted a Web Dynpro for Open Source? in which he discussed the topic more thoroughly and explained the different positions towards OpenSource inside SAP. A lively discussion ensued in the comment section, which is a must-read.
One week later, Jochen Guertler, the Product Owner Web Dynpro Java Web Dynpro for Open Source, spawning more interesting responses:
Dear Web Dynpro community,
please have a look to Benny´s blog under Web Dynpro for Open Source? raising the question whether Web Dynpro Java should become Open Source.
It would be very interesting for me to here your opinion about this. What are the benefits in doing this? What are the risks? Would YOU like to actively contribute?
Thanks in advance
Jochen (Product Owner Web Dynpro Java)
To tell you a bit about my background regarding this discussion, my employer is an Independent Software Vendor (ISV) that has been working with SAP and ABAP for over ten years. Recently it has adopted SAP NetWeaver Composition Environment as a development platform and started several CE-based development projects. Now whenever a new project is around the corner, the same discussion begins:
For someone who knows the Composition Tools included in the recent CE releases 7.1 and 7.1 EHP 1, such discussions are painful: You’ve got the best development tools you could ever want, but your customers don’t have the runtime, and maybe your potentials customers don’t want to become SAP customers just because your application is so great.
(In fact, becoming an SAP customer and running NetWeaver is still a huge step if you compare it to having the intern set up a JBoss or LAMP server.)
What does this mean for ISVs? Using NetWeaver tools locks them out of parts of the market. So they use them less than they would like to, because the fear of losing customers is greater than the fear of using only the second-best User Interface design tool.
Web Dynpro is a good example. As SAP Mentor Dagfinn Parnas pointed out in response to Jochen Guertler’s forum post:
[…] Therefore, I am very positive to the open-sourcing of WD for Java ifEvery Java EE developer I have spoken to agrees that Web Dynpro for Java is unique, great to use, and an extremely valuable and impressive tool. (They say the same about other NetWeaver Composition Tools when I demonstrate them.) They understand that it speeds up the development process, adds agility and maintainability, and makes the user interface easy to use through coherence and standardization. But they point out correctly that UIs based on Swing, JSP, JSF, etc. can run everywhere. And that is exactly the future I would like to see for Web Dynpro.
a) it fills a "niche" and provides something more than the open-source solutions which exist today.
b) it provides value back to SAP
The key features which make WD stand out are
1) Model driven
2) Standardized UI
3) Rendering engine independent
I don't know of any open-source solutions which have the same key features, so requirement a) should be fulfilled. […]
[…] Yes, running on any standard Java server.
I can't give you all the details, but lets just say its not a difficult you might imagine it to be. 🙂
Chris W