Once you create a
template project for your HTML plug-in, you must be familiar with the folder
structure of the project and the purpose of each file inside the project. This
knowledge will help you to easily create your custom plug-ins for the
vSphere
Client.
The following tables contain
detailed information about the structure of the UI and Java service components
of the HTML plug-in project template.
UI Project
Template Structure
■
|
■
|
|
app/
|
Main source files
for the plug-in user interface, including Javascript and Typescript files.
|
|
■
|
■
|
|
css/
|
CSS files used
in the plug-in. The
css folder contains
the
plugin-icons.css file
that you can use to define the external icons.
|
|
■
|
|
i18n/
|
Localized
resources used in the plug-in.
|
|
■
|
|
images/
|
Images used in
the plug-in.
|
|
|
■
|
■
|
|
plugin.xml
|
Manifest file
of the plug-in. Defines extensions and resources.
|
|
■
|
■
|
|
MANIFEST.MF
|
Manifest
file of the WAR bundle.
|
|
|
■
|
|
■
|
|
bundle-context.xml
|
Declares the
service that this UI bundle uses.
|
|
|
|
Java Service Project Template
Structure
■
|
■
|
|
build-java.bat
|
Windows script to
generate the Java service bundle.
|
|
build-java.sh
|
MacOS script to
generate the Java service bundle.
|
|
build-java.xml
|
ant script to
generate the Java service bundle.
|
|
■
|
■
|
■
|
|
MANIFEST.MF
|
The
bundle manifest file.
|
|
■
|
|
spring/
|
Spring
configuration files.
|
|
|
■
|
|
java/com/mycompany/myplugin/
|
|
■
|
|
services/
|
Interfaces
and implementations for plug-in services.
|
|
■
|
|
model/
|
Data
models for plug-in services.
|
|
■
|
|
controllers/
|
Controllers for plug-in services.
|
|
|
|
|