Page History

...

Naming Conventions for Artifacts and controller entries

Controller

A controller file contains lotTODO: controller's of request-map and view-map. To help the reader, set a blank line between request-map or view-map element only when you change the functionnal group (entity, workflow or IHM treatment).

Request without event

Most of case the request name is the same that the view-map called. For the request-name use java naming conventions object (ex : "FindParty"), and declare all in one line.

     <request-map uri="FindParty"><security https="true" auth="true"/><response name="success" type="view" value="FindParty"/></request-map>

Request with event

For the request-name use java naming conventions field (ex : "editParty"), and declare each xml element on separate line

   <request-map uri="createPerson">
        <security https="true" auth="true"/>
        <event type="service" invoke="createPerson"/>
        <response name="success" type="view" value="EditPerson"/>
        <response name="error" type="view" value="EditPerson"/>
    </request-map>

View

For the view-name use java naming conventions object (ex : "FindParty"), and declare all in one line.

    <view-map name="FindParty" type="screen" page="component://mycomponent/widget/PartyScreens.xml#FindParty"/>

widget screens

TODO: conventions for screen names (top-level screens, included screens, decorators)

...