BSP or WebDynpro for RF transactions?

Question

For WM RF transactions, tipically, custom transactions are created from scratch (most of the time) in ABAP and seen in the RF devices using SAPConnector (either text based or html (SAPWEBConsole).
For the latter, the SAP transactions are shown in internet explorer. Since a very simple html translation takes place in the SAP Web Console, the display is very simple and customizing is very limited (no icons, no font sizes, etc.).
Have you considered or heard of using BSP or Webdynpro as development tools for RF transactions? I know it sounds like an overkill, but given the fact that probably all transactions will be custom made and these tools give more customizing options, would it be reasonable to consider this development path?
Webdynpro should be simpler than ABAP screen programming.(at least in simple screen processing, the case for RF transactions).
Any comments?

Answer 1

Both webdynpro and BSP call ABAP function modules from HTTP.
The BSP interface does this via programming in SE80, the webdynpro does this via programming in the Java development workbench.
The BSP enters the SAP systenm via the ICM and is 'routed' to ICF where call are then made to executre ABAP (a good example is we use SOAP BSP's). Webdynpro routes via the ICM to the Java engine which then executes the Java to cann the functions via an RFC interface called a JCo connection.
Another difference to note is SAP is now dedicated to using webdynpro as its internet platform of the future. This indicates that it aims to eventually retire such things as ITS and BSP.
if it may be useful rewards points are appreciated