Retrieving Bean Classes from Source Directories 

Prerequisites

●      You have started the JavaBean Model Importer for a locally or centrally versioned Web Dynpro project.

●      The complete JavaBean project has been imported using the function Import → File System. It is therefore displayed in the Web Dynpro Explorer view and is available in the current Web Dynpro project: When you import the JavaBean project, choose the highest project directory and confirm the dialog querying whether the class path entries should be overwritten. With this import, the entire content of the JavaBean project become part of the /src/packages folder in the Web Dynpro project. If you are not already in the Navigator view, switch to it now (Window → Show View → Navigator).

Procedure

To use a project source directory as an import source, proceed as follows:

       1.      Choose the option Project(source folder) in the Importer window. If you check the option Include archives and projects defined by the class path, the wizard will then allow you to reuse the JavaBean project objects that have already been placed, plus all classes and interfaces in the assigned projects – for example, from the Web Dynpro runtime (_webdynpro_clientserver.jar, _webdynpro_services.jar) or the Java runtime environment (rt.jar in java.util.jar in the JDK directory) in the current installation. Choose Next >.

       2.      Select all of the classes that you need and choose Add -->. After a few seconds, the classes are displayed in the right column for the model objects. Choose Next > again, in order to set the properties of the model classes.

       3.      In the default tab ModelClass View, select one of the classes to be imported and choose  Add. In this dialog box, you can select properties from other JavaBeans and add them to your imported class.

       4.      In the tab ModelRelation View in the same wizard window, you can check the relations of the classes again before import.. It is especially important to specify the target model classes for model relations flagged with a warning and thus prevent the occurrence of import conflicts. Dissolve the relations as required. The wizard provides helps you, for example, when dissolving relations of type java.util.Collection. The model import cannot start until all relations have been broken down or marked as non-relevant by the importer.

If there are design time errors in the import definitions, the import cannot be started. In this case, choose Back to return to the preceding wizard windows and make the necessary corrections.

       5.      The next window displays an import log  Choose Finish to trigger the final import step.