Importing a JavaBean Model 

The model tools of the SAP NetWeaver Developer Studio provide design time support for the use of JavaBeans for a Java Web Dynpro application. The following support is provided when using JavaBean for a Web Dynpro application:

·        Interface support

·        Support for the inheritance of JavaBean classes

·        Support for abstract JavaBean classes (in addition to the interfaces)

·        Enhanced support for multiple JavaBean sources

¡        Project

For the Web Dynpro application, you can specify either the source folder of the project or the entire class path as the source to be used for the JavaBean import.

¡        Local .jar file

Web Dynpro developers can decide whether a design time or deploy time dependency is to be set up.

¡        Public parts of used development components (DCs)

The DC is responsible for the usage modality with regard to any runtime support.

After the bean classes have been imported to the Web Dynpro project using the logical Web Dynpro application entity model, it is possible to develop a user interface with the help of the Web Dynpro tools. Furthermore, the NetWeaver development infrastructure (NWDI) is available for the JavaBean.

Installation Prerequisites

You are using the SAP NetWeaver 04 Developer Workplace, Support Package 10 or higher.

Supported Import Objects from a JavaBean

Interfaces and Abstract JavaBean Classes

In addition to the interface import support, it is also possible to reuse abstract JavaBean classes. When you select a JavaBean class to be imported, you can automatically add the corresponding superclass and the interface classes. This import behavior is optional: If you do not select Add Corresponding SuperClass and Interfaces, only the specified classes are imported. No duplication of model properties and model relations takes place. The superclasses and interface settings are assigned to the relevant model class (modelClass.setSuperClass(), modelClass.addInterface()).

Enhanced Support for Multiple JavaBean Sources

You have the following options when importing a JavaBean:

       1.      From a project

                            a.      Option Project (source folder)

You can only import JavaBeans that were implemented within the Web Dynpro project.

                            b.      Option Include associated projects

Here there are extended project import options:

                                                  i.       Project source folder

                                                ii.       External internal.jar files

                                               iii.       Referenced projects with their source folders and .jarfiles (recursive)

       2.      From a local.jar file

Option Local JAR file

Here we differentiate between locally available Web Dynpro projects and development component projects of the type “Web Dynpro” that are part of the infrastructure.

                            a.      Local Web Dynpro project

With this project type, you can select any locally available .jar file for import. You can also specify whether the .jar file is to be part of a deployable unit or solely available for design time support..

                                                  i.       If the .jar file is to be part of a deployable unit, the file is placed in the \lib folder of the project as a “shared reference“ for the project (method addSharingReference).

                                                ii.       If the .jar file is not to be part of a deployable unit, it is merely added to the class path. To be able to use the .jar file for design time support, it must have been deployed with a different application entity; there is only one dependency at compile time.

                            b.      DC project of the type “Web Dynpro”

You can select from all public parts. The remaining procedure during the import is very similar to that for the .jarimport option for local Web Dynpro projects. The only difference is that no separate step is required for specifying whether the .jar file is to be used for design time support or runtime support. The DC carries out this step itself by taking the public part property Assembly or Compilation into account accordingly: In the case of a public part of the type Provides an API for developing/compiling other DCs, the object “.jarfile” is visible to the other development components; if the public part is of the type Can be packaged into other build results, it cannot be used for compiling the component.

Additional Information

The following sections provide a description of the import wizard and information on naming conventions, for example:

Importing a WD Model of the Type JavaBean for a Local WD Project

JavaBean Model in a Development Component Project

Conditions and Naming Conventions for an Import Bean