ADF framework knowledge
Everybody on the team will need basic knowledge of the ADF framework. This includes project managers, testers, graphics designers, and usability experts too. Having a common understanding of what the framework can and cannot do will make communication within the team much easier.
The programmers will, of course, need a deeper understanding of the framework, but not everybody has to be an expert. An experienced programmer should just need a basic one-week training class and a couple of weeks work under experienced supervision in order to be productive with ADF.
Finally, you need at least one person with a deep understanding of how ADF works. This person will define project standards and provide guidelines for how to use ADF effectively. The same functionality can be implemented in many ways in ADF. It is the task of the ADF expert to ensure that you use the framework as much as possible and do not code things that ADF can handle declaratively.
XML
The ADF framework is meta-data driven. This means that most of the application is not actually programmed in a programming language like Java, but is instead defined through JDeveloper. These definitions are stored in the form of XML files. You will notice that, for example, business components have a Source tab, allowing you to see the raw XML file.
You do not have to write XML files to use ADF, but it will be an advantage to know a little bit about XML so you can read the files JDeveloper builds.
The ADF framework is meta-data driven. This means that most of the application is not actually programmed in a programming language like Java, but is instead defined through JDeveloper. These definitions are stored in the form of XML files. You will notice that, for example, business components have a Source tab, allowing you to see the raw XML file.
You do not have to write XML files to use ADF, but it will be an advantage to know a little bit about XML so you can read the files JDeveloper builds.
Web technologies
When your ADF application is running. the end user is interacting with a web page in a browser. This means that your application must use the web technologies the browser understands: HTML. Cascading Style Sheets (CSS), and JavaScript. The ADF framework takes care of most of the details for you. but it is good to have someone on your team that understands these technologies. That person can both help you understand any limitations you might encounter and how to work around them.
Regular expressions
JDeveloper allows you to use regular expressions to define validation rules. Regular expressions are arcane. almost magical constructs that can express complex requirements in very compact form. For example, the following regular expression can be used to validate an e-mail address:
[A-Z0-9. -]+@[A-Z0-9.-]+\.[A-Z](2,4}
Everybody on the team will need basic knowledge of the ADF framework. This includes project managers, testers, graphics designers, and usability experts too. Having a common understanding of what the framework can and cannot do will make communication within the team much easier.
The programmers will, of course, need a deeper understanding of the framework, but not everybody has to be an expert. An experienced programmer should just need a basic one-week training class and a couple of weeks work under experienced supervision in order to be productive with ADF.
Finally, you need at least one person with a deep understanding of how ADF works. This person will define project standards and provide guidelines for how to use ADF effectively. The same functionality can be implemented in many ways in ADF. It is the task of the ADF expert to ensure that you use the framework as much as possible and do not code things that ADF can handle declaratively.
XML
The ADF framework is meta-data driven. This means that most of the application is not actually programmed in a programming language like Java, but is instead defined through JDeveloper. These definitions are stored in the form of XML files. You will notice that, for example, business components have a Source tab, allowing you to see the raw XML file.
You do not have to write XML files to use ADF, but it will be an advantage to know a little bit about XML so you can read the files JDeveloper builds.
The ADF framework is meta-data driven. This means that most of the application is not actually programmed in a programming language like Java, but is instead defined through JDeveloper. These definitions are stored in the form of XML files. You will notice that, for example, business components have a Source tab, allowing you to see the raw XML file.
You do not have to write XML files to use ADF, but it will be an advantage to know a little bit about XML so you can read the files JDeveloper builds.
Web technologies
When your ADF application is running. the end user is interacting with a web page in a browser. This means that your application must use the web technologies the browser understands: HTML. Cascading Style Sheets (CSS), and JavaScript. The ADF framework takes care of most of the details for you. but it is good to have someone on your team that understands these technologies. That person can both help you understand any limitations you might encounter and how to work around them.
Regular expressions
JDeveloper allows you to use regular expressions to define validation rules. Regular expressions are arcane. almost magical constructs that can express complex requirements in very compact form. For example, the following regular expression can be used to validate an e-mail address:
[A-Z0-9. -]+@[A-Z0-9.-]+\.[A-Z](2,4}
No comments:
Post a Comment