In accordance with the Resource Model, you should add a new APS type and a respective service for the APS type.
In this document:
To meet the Scenario and the Resource Model, set requirements for the developer, such as the following:
Continue the demo project started in the previous step.
In the project workspace, for example, in the event-mgmt/
folder, edit
the APP-META.xml
file as follows:
In the UX1 navigation tree, declare one more item, events
, that must be presented as one more sub-item
in the application navigation tree.
In the new item, add a view with the ui/events.js
source file,
which name corresponds to the view ID - events
. The view will print out the list of event notifications.
Also declare the events
variable to be used in the UI view.
<item id="events" label="Event Notifications">
<view id="events" label="Event Notification Log" src="ui/events.js">
<var type-id="http://aps-standard.org/samples/event-mgmt/event/1.0" name="events" />
</view>
</item>
Declare one more singular service, events
that will be responsible for the following operations:
<service id="events">
<code engine="php" path="scripts/events.php"/>
<presentation>
<name>Event Processing</name>
<summary>Processing event notifications</summary>
</presentation>
</service>
The modified metadata updates the navigation tree in UX1 by adding one more view to show event notifications and adds the declaration of the new service the application will expose to process event notifications.
The APP-META.xml
file you have created is similar to the respective file in the
sample package
.