Databases Reference
In-Depth Information
Listing 12-2
. Example APEX Page Template Snippet
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="&BROWSER LANGUAGE." xmlns="http://www.w3.org/1999/xhtml"
xmlns:htmldb="http://htmldb.oracle.com" xmlns:apex="http://apex.oracle.com">
<head><title>#TITLE#</title>
…
The discussion so far illustrates page rendering; however, each page can also define page
processing, or the events to be invoked when a page is posted. Figure 12-3 illustrates that application
attributes for rendering and processing are differentiated within the Application Builder.
Figure 12-3
. Application Builder page edit example
When a page is posted, the architecture is similar to page rendering. When APEX pages are posted
they are submitted directly to the
WWV FLOW.ACCEPT
procedure using syntax similar to
<form action="wwv flow.accept" method="post" name="wwv flow" id="wwvFlowForm">
Page accept processing is similar to page show processing, except that no user interface is
generated. On page accept, application page metadata is fetched from tables and the corresponding
page validations, processing, and branching are processed.
Page branch metadata defines the URL that is to be displayed after successful processing of the
current page, typically another page in the application. Figure 12-4 shows how page 10 branches to
page 8.
