on 12-29-2005 8:36 PM
In the past I made programs using BSP and ABAP. I read a lot of webdynpros and know about the advantages comparing to BSP. But are there also disadvantes?
And what's about the Java technology? I read a lot about the Java technology using SAP. But now a customer asked me to explain why he should use Netweaver with the J2EE-engine.
Is it possible to give me some pros and cons for
a) Java
b) Webdynpro
comparing to the development of BSP-pages with ABAP(Objects)?
Webdynpro is the new user interface model for SAP. It is web based, so it runs in a brower. The development environment allows you to design your application using the Model, View, Controller paradigm. You can drag and drop the UI elements into the layout instead of having to code them in BSP or JSP. Web Dynpro is available in two flavors, Java(currently available), and ABAP(will be released in the spring). Now you have a choice for developing robust web applications. If you have mainly a java shop, then use java, if you have an ABAP shop, then use ABAP. If you have both, then make a choice. Personally I preferr WDA over WDJ. The reason is because I am very comfortable with ABAP, more so than java. And I feel that the development environment is stronger then NWDI, at the moment. SAP is doing a very good job of bringing the java side up to the ABAP standard. One disadvantage of using Web Dynpro over BSP, or JSPs, is that you have no control over the UI, it is standard, you can't change the look and feel of the UI elements, no scripting, no custom HTML, nothing. This is good, if you want a standard look and feel across all applications, internal and external. This is bad if you want to be able to develop business applications with a pretty face.
Regards,
Rich Heilman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First of all another major "difference" between Webdynpro and BSP/JSP beside the UI control is the fact that Webdynpro is always stateful. BSP/JSP have the advantage of being able to program stateful/stateless (or switch between the two). Stateless applications can be very useful when creating internet facing highly scalable applications. However when creating business transactions for a smaller group of users, stateful is acceptable.
Now to ABAP vs. Java. One real world advantage that ABAP has over Java currently is that nearly all the backend business data and logic is contained on the ABAP side of the world. Although you can access this logic and data with Java, ABAP obviously has an easier time doing so. Look at ABAP WebDynpro for instance. If you are creating a WDA component on ECC 6.0 you excellent built in functionality for Value Help. You also can just use Open SQL in your Model Class and avoid any complications that might come from Adaptive RFC. I'm not saying that there is anything wrong with the Java tools. Adaptive RFC is actually quite impressive. However ABAP has the simple advantage of being closer to the application data/logic. Although SAP is working hard to bring the java Development and Transport environment up to the same level as the ABAP world, it is hard to ignore the close relationship between ABAP and the underlying Busines Logic. ESA enablement will help fill that gap in the future, but can't close it all together.
However none of the gaps that I discussed are insurmountable. I think the final decision does come back to what programming language are you and your group most comfortable working in and supporting. In the long term you will create better applications by leveraging the skills sets that you have than trying to force yourself into a environment that you/your group isn't comfortable with.
Hello,
generally speaking I agree with the statements of Armin. But related to SDN you can usually trust most things said here(especially those ones of Thomas and Rich). So I think the remark of Armin is note related to the two answers made by Thomas and Rich in this forum post
For myself I believe what Thomas and Rich are saying...
Regards
Juergen
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.