Tag Archive

ADF Faces provides strong support for Accessibility and 508 Compliance. Most ADF Faces components have attributes that will translate to tags that screen readers can interpret. For example, <af:input>has an attribute shortDesc for a short description; this translates to an html alt tag, which is readable by most screen readers. You can find Oracle’s Accessibility guidelines for ADF Faces here: http://www.oracle.com/webapps/online-help/jdeveloper/10.1.3/state?navSetId=_&navId=4&vtTopicFile=jsf_apps/adfcreate/af_aacessible.html&vtTopicId

Oracle ADF Faces 10g: How to pass data between pages Do you have the need to pass data between pages, e.g. for a new customer signup page flow that spans multiple pages? In ADF Faces, when you have a form that spans multiple pages, you have options on how to pass and maintain the data between pages, e.g. cache the data in the middle tier, re-write the data into hidden fields on the page, or store the state in session. Caching and storing data in session have the drawback of not being back-button or new-window safe. Often frameworks have a … Read More

Did you know ADF Faces allows you to submit only part of a page? This can be useful when you have a search box on a page and only want to submit that one component when the user clicks the search button. The ADF Faces af:subForm component represents an independently submittable region of a page. When used within an af:form tag or within an JSF HTML h:form tag, af:subForm lets you control which components should be validated and pushed into the model without having to use multiple forms on a page. See the following for more information on ADF subForms.