|
Oct 18 2008, 2:56 PM EDT
|
|
|
edit |
10 words added
195 words deleted
|
|
Change: Define enterprise-wide look and feel through ADF Faces RC Templates and Skins Receive requests for enhancements from other stacks Deploy as JAR file Reusable Application Portfolio Stack - requires little Java coding Receive requests for reusable applications from Final Application Stack Create entity objects for reusable application Create view
View changes from previous version.
(Word count: 1330)
|
|
Sep 22 2008, 9:20 AM EDT
|
|
|
edit |
9 words added
1 word deleted
|
|
Change: RC, see for example Swing or JavaServer Faces) Skills fit of existing staff to ADF (ie. Java programmers, or PL/SQL programmers) Training costs? For the remainder of the methodology ADF BC and ADF Faces RC have
View changes from previous version.
(Word count: 1516)
|
|
Sep 11 2008, 11:07 PM EDT
|
|
|
edit |
197 words added
1 word deleted
|
|
Change: Define enterprise-wide look and feel through ADF Faces RC Templates and Skins Receive requests for enhancements from other stacks Deploy as JAR file Reusable Application Portfolio Stack - requires little Java coding Receive requests for reusable applications from Final Application Stack Create entity objects for reusable application Create view
View changes from previous version.
(Word count: 1509)
|
|
Sep 5 2008, 4:41 AM EDT
|
|
|
edit |
9 words added
|
|
Change: How to convince others to adopt ADF & JDeveloper If ADF is adopted, why and when should I pick ADF BC, Toplink, JPA or EJB's for the ORM? ADF Business Components ADF BC is particular suited to ex-Oracle Forms and PL/SQL programmers It was written with
View changes from previous version.
(Word count: 1313)
|
|
Aug 7 2008, 3:51 PM EDT
|
|
|
edit |
178 words added
5 words deleted
|
|
Change: What's available out-of-the-box (validation framework, event handling, data binding, error handling, transaction handling) when using a specific technology, e.g; JSF or ADF Faces, ADF Security, ... Decompose design into identified reusable components for ADF, including ADF BC entity
View changes from previous version.
(Word count: 1305)
|
|
Aug 5 2008, 2:38 PM EDT
|
|
|
edit |
9 words added
|
|
Change: How many of these already exist in reusable format? How to define and manage security, what are the options and what’s best practice? How to install and configure ADF applications using SSO. What are the pitfalls and best practices? How to enable automatic deployment through release management processes? How
View changes from previous version.
(Word count: 1122)
|
|
Jul 17 2008, 8:38 PM EDT
|
|
|
edit |
131 words added
4 words deleted
|
|
Change: Structures are relationally organised, with components that map to "Tables", "Columns" and based on standard SQL to interact with the database. Toplink tba (CM note: ...suited to Java programmers ...?) JPA tba (CM note: ...suited to Java programmers ...?) (CM note:... this is essentially EJB 3 isn't it.... I forget....?)
View changes from previous version.
(Word count: 1113)
|
|
Jul 14 2008, 3:00 AM EDT
|
|
|
edit |
117 words added
2 words deleted
|
|
Change: Is there a need to override the existing validation framework, what are the boundaries of the ADF Framework concerning validation? What can and can’t be refactored when using BC4J and ADF, pageDefinition-files, implementation files, watch-outs. Examples of standard development steps: Create custom ADF BC framework Create sub-top-level
View changes from previous version.
(Word count: 984)
|
|
Jul 13 2008, 11:08 PM EDT
|
|
|
edit |
68 words added
|
|
Change: Create reusable ADF BC application modules (e.g., nestable app modules for common tasks) Define application look and feel through ADF Faces RC Templates and Skins Create custom ADF Faces-friendly utilities (e.g., utilities for working with EL) Create custom ADF Faces framework (e.g., error handling, lifecycle modifications) Create reusable ADF
View changes from previous version.
(Word count: 861)
|
|
Jul 10 2008, 10:30 PM EDT
|
|
|
edit |
25 words added
|
|
Change: The common JEE problem on how to minimize redeployment to the app server (or is it even possible) (as per Chris Muir's blog post) Support & maintenance What should be considered to aid in the ongoing support and maintenance of an ADF application? Examples: Automated regression testing? Future
View changes from previous version.
(Word count: 787)
|
|
Jul 10 2008, 9:59 AM EDT
|
|
|
edit |
21 words added
|
|
Change: JSF backing beans: to inject the binding container, use ADFUtils or JSFUtils, or annotations (as per Simon Lessard's detailed discussion) Examples of standard development steps: Create custom ADF BC framework Create reusable ADF BC entity objects Create reusable ADF BC view objects (eg. lookups) Create reusable ADF BC domains
View changes from previous version.
(Word count: 762)
|
|
Jul 7 2008, 1:29 AM EDT
|
|
|
edit |
7 words added
15 words deleted
|
|
Change: If the end solution is a web application, what browsers and versions must be supported? Skills fit of existing staff to ADF (ie. Java programmers, or PL/SQL programmers) Training costs? Once ADF has been selected as the technology of choice, the following sections only consider ADF. Technical system requirements
View changes from previous version.
(Word count: 741)
|
|
Jul 7 2008, 1:28 AM EDT
|
|
|
edit |
78 words added
|
|
Change: Decompose design into identified reusable components for ADF, including ADF BC entity objects, view objects, domains, and ADF Faces RC declarative components, and page fragments. Development What are best practices for development, what will need to be created? Example best practices questions: Define ADF BC package structures/naming conventions Define
View changes from previous version.
(Word count: 749)
|
|
Jul 5 2008, 1:44 AM EDT
|
|
|
edit |
|
|
Change: There were only format changes (bold, italics, etc.) in this version. See this version for details.
(Word count: 671)
|
|
Jul 5 2008, 1:15 AM EDT
|
|
|
edit |
441 words added
36 words deleted
|
|
Change: Consideration of the end technical and architectual solution. For instance one organisation may only need to support 5 users, while another 1000 users, which will
View changes from previous version.
(Word count: 671)
|
|
Jun 24 2008, 9:17 AM EDT
|
|
|
edit |
260 words added
|
|
Change: As an initial brainstorm, the points below show some example issues and concepts that maybe appropriate to capture in the ADF methodology as material to assist future discussions:System requirements gathering (decision points)Are open source frameworks required or are proprietary frameworks
View changes from previous version.
(Word count: 262)
|
|
Jun 24 2008, 9:14 AM EDT
|
|
|
create |
No content added or deleted. |
|
Change: Created by Jun 24 2008, 9:14 AM EDT for: no reason given
|