Part(I) : Naming
-------------------------
01. Class name : FirstSecondThird..........example(SayHello)
02. Package name : firstsecond.......example(roviews)
03. Method name : firstSecondThird ....... example (addApplicantEval())
04. Updatable view : FirstSecondThirdUPView ....example(ApplicantUPView)
05. Read only view : FirstSecondThirdROView ........example(EvalItemRuleROView)
06. Link : FirstSecondThirdLink .....example(ApplicantEvalLink)
07. Application Module : FirstSecondThirdAM.......example(ApplicantAM)
08. Entity : FirstSecondThird ....as table name without suffix
09. Association : FirstSecondThirdAssoc......example (PerLoanPayFkAssoc)
10. Bean : firstSecondThird ....... example (addApplicantEval)
11. Backing Bean : Same as bean name standards but it takes the same name of the page ...... example (Page name : AddApplicantFrag - Backing Bean name : addApplicantFrag)
12.Class of backing bean : same as class standards but take the same name of page ....example (Page name : AddApplicantFrag - class name : AddApplicantFrag)
13.Transient Attribute :TFirstSecond ......example (TExitDate)
14.Bind Variable :BindFirstSecond .........example(BindProjectNumber)
15.Task Flow : FirstSecondTask............example(ApplicantEvaluationTask)
16.
17.
18.
20.
Part(II) : Formats
-------------------------
01.Date Format : dd-MM-yyyy .......example(25-01-1989)
Part(III) : General
-------------------------
01.All our pages will be .jspx instead of .jsp
Oracle recommends that when creating an ADF application, you create an XML-based JSP document, which uses the extension .jspx, rather than creating a .jsp file. Using an XML-based document provides the following benefits:
•Treats your page as a well-formed tree of UI component tags
•Discourages you from mixing Java code and component tags
•Enables you to easily parse the page to create documentation or audit reports
•Enables the page to be used as metadata
|
02.All our pages will be .jspx instead of .jsp
No comments:
Post a Comment