But why would you want to use the memory scope as a prefix? If you reference an attribute in memory scope, then the search goes from smallest scope to broader scope, which means that if – by accident – there exist two objects with the same name and you wanted to access the object in the broader scope, chances are you access the wrong object. So prefixing the expression puts you on the save side. This however is only good to use when you access objects that already exist in memory (wich could be a previously instantiated managed bean – of course)

Managed beans must be instantiated before they become available in the memory scope, which means they need to be accessed through JSF. Luckily, JSF does not allow to configure two managed beans with the same name in different scopes. So even without a scope prefix, there is no risk that application code accidentally accesses the wrong object.

Note however that using ADFc specific scope like viewScope and pageFlowScope, a prefix of “pageFlowScope” or “viewScope” is required in the EL reference.

Frank

Chapter 30 of the Oracle® Fusion Middleware Fusion Developer’s Guide for Oracle Application Development Framework 11g Release 1 explains the JAAS protection mechanism for ADF pages and Task Flows. In here it is recommended that you reduce the number of JSF pages in the adfc-config.xml file to the absolute minimum and only give ADF Security permissions to those documents that need to be accessible from a browser request.

All other pages should be located in bounded task flows, which you can protect declaratively against GET requests, as they are issued from a browser URL. Bounded task flows need to be ganted to users through application roles to be accessible.

The discussion on OTN is about protecting the phyical JSPX files. If you are an authenticated and authorized user, then you could directly access the JSPX page, e.g. calling localhost:7101/myapp/faces/Departments.jspx. This then serves the page – though it may not be fully functional because it is not launched within the controller context.

The recommendation therefore is to store JSPX documents under the WEB-INF directory of the public_html folder. This solves the problem of users accessing physical files directly

Frank

Ps.: Note that if moving JSPX documents into the WEB-INF folder is not an option for you, you can write a servlet filter that checks the incoming request URL for the resource it accesses. If a jspx file is accessed you would return a http 403 error.

Note: If your trigger component is an inputLov or an inputComboBoxLov, and the target component is an input component set to required, then a validation error will be thrown for the input component when the LOV popup is displayed. To avoid this, you must use programmatic partial page rendering.

Note: In some cases, you may want a component to be rerendered only when a particular event is fired, not for every event associated with the trigger component, or you may want some logic to determine whether a component is to be rerendered. In these cases, you can programatically enable PPR.

Excellent !

Frank

Want to dig your own nuggets? here is the documentation: Looking forward to read your blogs and tweets with your favorite quotes.

• Making a bounded task flow URL accessible
• Launching a new browser window from a managed bean
• Defining the bounded task flow request URL in Java
• Passing input parameters to a task flow using a HashMap
• Use the hierarchical tree context menu to invoke an action on right mouse click
• Adding JavaScript to a managed bean response

[Read More] [Get More]

Frank

[Read More] [Get More] [Follow ADF Code Corner on Twitter]

• you are worried about missing bits of information about Oracle JDeveloper and ADF
• you feel uncomfortable saying “If I had known this before it would have saved me …”
• you don’t have time to frequently browse OTN
• you enjoy technical stuff more than knowing what Paris Hilton did last week
• you want to know more than others do

ADF Code Corner “twitters” interesting updates and information about Oracle JDeveloper, ADF and related topics.

Get More, Learn More: http://twitter.com/fnimphiu

Frank

1. Create a Java class that extends AdfcExceptionHandler
2. Create a textfile with the name “oracle.adf.view.rich.context.Exceptionhandler” (without the quotes) and store it in .adf\META-DATA\services (you need to create the “services” folder)
3. In the file, add the absolute name of your custom exception handler class (package name and class name without the “.class” extension)

For the expiry example, in the handleException method, you check throwable.getMessage() for “ADF_FACES-30108″ which indicates the expiry message. Don’t forget to pass exceptions your custom class doesn’t handle to the super class not to break any default functionality.

However, You should always try and use declarative exception handling when possible. For example, a router activity that is marked as the exception handler can access a managed bean method, which then accesses the ControllerContext.getCurrentInstance(), and in here the ViewPort, for determining the Exception type and message. So keep the hint of how to extend the the ADFc controller class as an exception to the rule of using declarative excpetion handler and use it only if you can’t find out how to handle an exception it otherwise.

Configuring the ADFc custom exception handling class is not yet part of the product doumentation but will be added the next JDev 11g Patch Set as part of the task flow content.

The above hint is a brief summary excerpt taken from the Oracle Fusion Developer Guide book that Lynn Munsinger and I wrote for McGraw Hill. I am blogging this in response to a question on the JDeveloper OTN forum.

Frank

[Read More] [Get More]

Frank

[Read More] [Get More on ADF Code Corner]

Frank

The closer we got to Christmas, the more exiting it was for me to see if McGraw Hill would make it publishing the book before Cristmas. Not that this makes a difference, but Lyn and I worked hard on meeting our schedules and though the book was announced for January 2010 I like it to be ahead of schedule. So I can call this a year and enjoy Christmas and new year eve with my family – no thinking of Java (possibly)

Thanks to McGraw Hill.

Merry Christmas to everyone.

Frank