Java Web Dynpro (Enhanced)
Function is |
Enhanced |
For Release |
Software Component Component: SAP NetWeaver Release: CE Support Package 3 |
Country Setting |
Valid for all countries |
Some new functions and features were added to Web Dynpro for Java. The following sections list the improvements made to Web Dynpro technology in the Web Dynpro runtime of the NetWeaver Application Server and in the design time in form of the Web Dynpro tools of the Developer Studio.
Using a print button in the application, or via the print entry in the iView menu, the assigned iView is rendered in a new browser window in a print preview mode. This screen then can be printed without scroll bars and without IFrames. Currently, there are a few restrictions when using the new print option:
● Internal scroll containers are not dissolved in browser print
● When printing tables only those lines are printed that are part of the displayed application screen
● Printing background graphics needs to be triggered manually
● Page breaks are not always considered correctly
Partial Screen Updates in Page Builder
The Page Builder API which supports controlling the page size, refreshing the page and paging personalization now also provides the new feature of displaying partial screen updates.
iView Splitting Application Property
A content administrator can create individual iViews from each view in an application, in order to rearrange the layout of the application and to incorporate non-Web Dynpro iViews among the Web Dynpro iViews. To do this, the application must be developed to be split up into different iViews. Enabling a Web Dynpro application for iView splitting is done within the application properties wizard in Web Dynpro tools.
Application developers can set the application mode to “dirty” by using the setApplicationDirty() method via wdDoPostProcessing().
The destroy() method of the IApplicationProxy returns an instance of IResponseResult to enable the application to unsubcribe for an portal event in the wdDoExit() hook method.
The Resource service allows you to create context attributes of type Resource to bring files to context.
Methods which take the deployableObject as input parameter to access a deployed application resource have been deprecated. The deprecated methods have been replaced by corresponding methods which take an IWDWebModule as input. The deploy SAL service has been extended by IWDWebModule and methods to access an IWDWebModule.
A Web Dynpro source migration tool removes legacy usage of internal classes.
The new interface com.sap.tc.webdynpro.progmodel.api.IWDUIWindow with method void setTitle(String title) supports setting a title for the application unit Window.
Defining exceptions for single controller methods can be done with wizard support now. The wizard is available for all controller/context types and started via the Methods tab.
There is a new design attribute which offers the possibility to render a ToggleLink without underline.
ToolBarButton spacing is computed automatically depending on item type. UI designers only need to place separators between item groups.
As of now, the Admin P13n standard is supported when the application is started via object-based navigation (OBN).
From the adminstrative tool Web Dynpro Console, invalidation of metadata caches is supported. This is useful if the application is using data from an SAP backend system where several caches are involved to keep the backend data values. This feature encreases adaptability of backend data.
Domain relaxation code is required for cross-frame JavaScript; this is particularly important for Portal integration. Developers assign the application property domainRelaxation from the Web Dynpro tools environment.
In addition to the error page, also a Help Center is started and displayed to support users in case of dumps and fatal errors. Furthermore, embedded support data from the application is shown.