The navigation results could be considered a repository of navigational links used on a page, or accross a project, allowing the assignment of symbolic names to such links. For this the two important attributes are the id and path. The id would be unique globally, and could be used to refer to the URL destinations.

Some frameworks include navigational rules configurations, which could be used to determine destination paths based on page of origin (from page), the preceding action or its result.

This could also be used document page flow.

dWebSpec navigation-path descriptor is designed to capture all these possibilities as well as access security roles and ?request options.

Example event descriptors entries are shown in the table below.

The destination of the data captured by the navigation result descriptor is the navigation-rule element inside the face configuration XML.

This configuration allows specifying navigation rules for a page or set of pages. It uses wild card for specification of pages or subset of pages within a directory. The absence of a from page would imply that the rule applies to all pages.

	<navigation-rule>
		<from-view-id>pages/*</from-view-id>
		<navigation case>
		.
		.

	</navigation-rule>

Within the navigation rule are navigation cases, which allow specifying actions and results to match, in following a navigation path.

	<navigation case>
		<description>Next page presented on successful entry</description>
		<from-action>#{wizard.nextPage}</from-action>
		<from-outcome>success</from-outcome>
		<to-view-id>/Confirm.jsp</to-view-id>
  <redirect/>
	</navigation case>

There are correspondences between dWebSpec descriptor attributes and these configuration entries, as shown below.

For further discussion follow the links for the descriptor attributes listed above.