14.01.2013 Views

Oracle JHeadstart Developer's Guide - Downloads - Oracle

Oracle JHeadstart Developer's Guide - Downloads - Oracle

Oracle JHeadstart Developer's Guide - Downloads - Oracle

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

13.3.5. Processing the Selected Forms<br />

• Application Module Class Extends: The name of the superclass of each<br />

application module object that will be created by the JFG. You can create your<br />

own superclass that extends from<br />

oracle.jheadstart.model.adfbc.v2.JhsApplicationModuleImpl<br />

class to implement common behavior across all your application modules. If you<br />

use CDM RuleFrame to implement your business rules in the database, you<br />

should select the<br />

oracle.jheadstart.model.adfbc.v2.RuleFrameApplicationModuleI<br />

mpl class, or your own subclass of this class. By extending from the<br />

RuleFrameApplicationModuleImpl class, your application will nicely<br />

display CDM RuleFrame errors in the web user interface.<br />

• Extract PL/SQL Logic?: If this checkbox is checked, the PL/SQL program units,<br />

and the form-, block- and item-level triggers will be visible in the <strong>JHeadstart</strong><br />

Application Definition. This is helpful in assessing the additional functionality<br />

that was implemented in the original form using PL/SQL that might need to be<br />

implemented as well in the web pages generated by the JFG/JAG.<br />

When you click the Finish button on the Summary panel, the JFG will start processing<br />

the forms.<br />

The processing consists of the following steps:<br />

• Conversion: Each selected .fmb form is converted to XML format using the<br />

FRMF2XML utility. This step is skipped when you already selected xmlformatted<br />

form files.<br />

• Extraction: For each data block in the form, the underlying table or view<br />

definition, including all primary keys, unique key and foreign key constraints<br />

are queried from the data dictionary tables. This information is added to the<br />

XML representation of the form, and the combined information is written to the<br />

file system, in the Java source root directory, in a file named<br />

_extracted.xml<br />

13 - 10 Forms2ADF Generator <strong>JHeadstart</strong> Developer’s <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!