!--a11y-->
A
Simple Input Form 
The Web Dynpro runtime environment provides generic UI services with which application developers can easily display messages of different types in the Web browser. Using the example of a simple input form, we would like to demonstrate how you can support the user with the task of correcting faulty input values or help the user if he has left out mandatory inputs. In addition, the application example will contain messages that serve the user as a confirmation for successful actions or as a warning. Here it is possible that the application user is shown several messages at the same time, and these may even include error messages. The messages are displayed as a link so that the user can select the link and automatically receive an input recommendation to correct the error in the corresponding UI element. If the input error occurs in a table, for example, the system automatically navigates to the appropriate line, which may not even be visible.
At the Web Dynpro component level, messages can be defined using a special Message Editor that is provided by the Web Dynpro tools. A Java class with the name IMessage<ComponentName> is generated from the messages entered there. This class can be used in different controller implementations to access the message texts contained therein. The message editor supports all three message types: error, warning, and standard message. Messages of the standard type are merely of informative character.
Errors and other messages can be displayed to the user in the Web browser through different method calls of the Message Manager, which is represented by the interface com.sap.tc.webdynpro.progmodel.api.IWDMessageManager. The Message Manager provides application development with different method types. In the simplest case, errors, warnings, or purely informative messages can be displayed on the user interface by passing a single parameter of the type String. A different type of IWDMessageManager methods displays messages that are based on invalid value attributes. In addition, there are IWDMessageManager methods, which use parameters of the type IWDMessage. Such messages are entered using the Message Editor and displayed at runtime, language-dependent, in the Web browser. For more information on this topic, refer to Error Handling and Messages.
· You define messages of the type IWDMessage in the Message Editor of the Web Dynpro tools.
· You perform various input checks within the controller implementation of a view.
· You display messages using the interface IWDMessageManager in the Web Browser.
· You use a non-validating action to delete or reset all possibly incorrect user inputs within a single view at runtime..
· You set a value transfer between two views by declaring an additional parameter of the type String for inbound and outbound plug instead of using the context mapping function.
Web Dynpro programming model: views, controller
contexts and data binding, navigation transitions, actions, Java
Dictionary
If you do not have the required basic knowledge, work through the sections
Creating a Simple Web Dynpro
Applicationand Creating an Extended Web Dynpro
Application.
Basic knowledge of the Java programming language.
· The SAP NetWeaver Developer Studio is installed on your PC.
· You have access to the SAP J2EE Engine (Release 6.30)
· You have a connection to a database instance of the SAP DB.
The development process described is divided into the following sections:
Application example for displaying messages
Specifying the project structure
Declarative development of a view
Defining simple types in the Java Dictionary
Creating a Form View and EMailEditor View
In each case, define the controller context of a view, view layout, actions, and binding of events to actions
Defining a navigation structure
Defining messages in the Message Editor
Controller implementation for Form and EmailEditor view (these contain methods for input check)
First
look at the application
example for displaying the error behavior and the message within a Web
Dynpro application. The application scenario should be implemented in the Web
Dynpro project presented here.
