Oracle® Application Development Framework Developer's Guide For Forms/4GL Developers 10g Release 3 (10.1.3.0) Part Number B25947-02 |
|
|
View PDF |
This appendix provides a quick summary of how basic tasks performed using the most common Oracle Forms triggers are accomplished using Oracle ADF.
This appendix contains the following sections:
Table C-1 ADF Equivalents for Oracle Forms Validation and Defaulting Triggers
Forms Trigger | ADF Equivalent |
---|---|
Execute validation code at the record level |
In the custom EntityImpl class for your entity object, write a public method returning |
Execute validation code at the field level |
In the custom EntityImpl class for your entity object, write a public method returning |
Execute code when a row in the datablock is marked for INSERT or UPDATE |
Override the |
Execute code to populate complex default values when a new record in the data block is created, without changing the modification status of the record. |
Override the |
Execute code whenever a row is removed from the data block. |
Override the |
Table C-2 ADF Equivalents for Oracle Forms Query Processing Triggers
Forms Trigger | ADF Equivalent |
---|---|
Execute logic before executing a query in a Data Block, typically to setup values for query-by-example criteria in the "example record". |
Override |
Override default behavior to count the query hits for a Data Block |
Override |
Execute logic after retrieving each row from the datasource for a data block. |
Generally instead of using a |
Override default behavior to attempt to acquire lock on the current row in the data block. |
Override the |
Table C-3 ADF Equivalents for Oracle Forms Database Connection Triggers
Forms Trigger | ADF Equivalent |
---|---|
Execute logic after logging onto the Database |
Override |
Execute logic before logging off from the Database |
Override |
Table C-4 ADF Equivalents for Oracle Forms Transactional Triggers
Forms Trigger | ADF Equivalent |
---|---|
Execute code before commencing processing of the changed rows in all data blocks in the transaction. |
Override Note: See this article for an overview of creating and using a custom DBTransaction implementation. |
Execute code before NEW row in the datablock is INSERTed into the database during "post" processing. |
Override |
Override default processing for INSERTing a NEW row into the database during "post" processing. |
Override |
Execute code after NEW row in the datablock is INSERTed into the database during "post" processing. |
Override |
Execute code before row removed from the datablock is DELETEd from the database during "post" processing. |
Override |
Override default processing for DELETE-ing a row removed from the datablock from the database during "post" processing. |
Override |
Execute code after row removed from the datablock is DELETEd from the database during "post" processing. |
Override |
Execute code before row changed in the datablock is UPDATEd in the database during "post" processing. |
Override |
Override default processing for UPDATE-ing a row changed in the datablock from the database during "post" processing. |
Override |
Execute code after row changed in the datablock is UPDATEd in the database during "post" processing. |
Override |
Execute code after Forms has "posted" all necessary rows to the database, but before issuing the data COMMIT to end the transaction. |
If you want a single block of code for the whole transaction, you can override the |
Execute code after database transaction has been committed. |
Override |