MDK Development Cycle | MDK Wizard Configuration | Import a .war file into a new project | Export a project into a .war file
When you create a new Mobile Infrastructure (MI) project, you should use this function to start the project. It makes sure, that the class path, source path and output path is set correctly. When the project is created you can create classes or import existing once and use the MDK plug-in to export your application to a .war/.jar file.
![]() |
In case you already have created a MI project by yourself, you should refer to the "Tips and Tricks" document, to adjust the source path and output path so the the MDK plug-in works properly when exporting the project to a .war/.jar file. |
The "Create MI Project" action can be started with the icon
in the toolbar or with the Eclipse command: File > New > Other ... >
MDK Development Tools > MI Project. A dialog window is displayed:
The dialog windows has two input fields:
With the Project Type you define what kind of MI project you want to create. Simply select the project type you need by clicking on to one of the radio buttons. The selection influences which folders and files are generated. See the "Tips and Tricks" document to see the details about the difference of a JSP and a AWT Project.
When the "Generate main classes of application" option is enabled, the "New MI Project" wizard generates basic coding for the new MI project . You can specify the names for the major parts of the new project.
JSP and AWT Project:
JSP Project only:
When all entries are correct the 'Finish' button is enabled. To continue press the 'Finish' button.
The project is generated with a classpath that contains all necessary MI .jar files and the source and output folders are set suitable for the MDK plug-in. The correct setting of the source and output folder is necessary for the export function of the MDK plug-in (for more information on the source and output path settings please refer to the "Tips and Tricks" document). Now you can start to implement the MI classes or import existing classes from the file system.
The code generation for the main classes (AWT and JSP) as well as the JSP,
web.xml and MANIFEST.MF files is controlled by templates that are stored in
the projecttemplates folder of the MDK plug-in (<Eclipse_home>/plugins/
com.sap.ip.me.mdk.developmentTools/projecttemplates). The templates are
separated by the MI runtime in JSP and AWT. The files have the extension
.template and are regular text files which contains "place holders"
for the names specified by the user. The "place holders" start with
${
followed by the key name of the "place holder" and
end with a }
.
You can change the templates so that the generated code suited better to your kind of applications.
![]() |
The templates are overwritten with any update of the MDK plug-in. So make a backup of the templates you changed before installing a MDK plug-in update. |