Tarek Fathy

This example assumes that you work have UIShell template as a template for your page  1- After creating the tree that contains a tree hierarchy  of the system menus , in  jsf page click on the tree component then open the property inspector for the tree 2- on the selection listener property of the tree , cut the selection listener value , for example #{bindings.UserAppMenu.treeModel.makeCurrent}" and create new selection listener on the managed bean , name it for example #{menuBean.onTreeMenuSelection} 3- make sure that the selectedRowKey property of the tree is null 4- the jsf code should be like this    <af:tree value="#{bindings.MenuTreeVo.treeModel}" var="node"                                              selectionListener="#{menuBean.onTreeMenuSelection}" rowSelection="single" binding = "#{menuBean.menuTree}"   ...

Hi, In 12.1.3 when you drag and drop a view object as a graph, the bindings created are not a type graph anymore, they are a normal tree, which raises the following question; how do you access again the wizard for the graph in case you want to change something on it or even further; how would you now implement a drill down graph? I wrote a post for the previous release which seems to be not applicable for this new realease. Am I missing something? Regards. The fact that the new Charts now use a standard tree binding instead of a custom Graph binding allows for more flexible tag structure and usage of stamping. For example, to achieve the feature where each bar is colored differently even though they all belong to the first series, we recommend to use attribute groups to specify that the bars should be colored by group. To to this, you would insert the following code into the <dvt:chartDataItem> tag, instead of swapping the series and group bindings: <dvt:a...

https://www.youtube.com/watch?v=0ghJ3CUjI_Y

in the web.xml add /or modify UPLOAD_MAX_MEMORY and UPLOAD_MAX_DISK_SPACE  <context-param>         <!-- Maximum memory per request (in bytes) -->         <param-name>org.apache.myfaces.trinidad.UPLOAD_MAX_MEMORY</param-name>         <!-- Use 500K -->         <param-value>512000</param-value>     </context-param>     <context-param>         <!-- Maximum disk space per request (in bytes) -->         <param-name>org.apache.myfaces.trinidad.UPLOAD_MAX_DISK_SPACE</param-name>         <!-- Use 5,000K -->         <param-value>10240000</param-value>     </context-param>

First You need to download the extension   http://download.oracle.com/otn-pub/jdeveloper/12.1.3.0.0/extensions/junit.zip

oracle.jbo.ExprSecurityException JDeveloper 12.1.3 and ADF has introduced a tightening security model for ADF BC Groovy expressions as a stepping stone for upcoming Oracle products. Oracle is progressively introducing this feature to reduce the burden on customers. For any new ADF application, customers must set via the property inspector trustMode="true" for any ADF BC attributes or similar using a Groovy expression. Otherwise at runtime JBO-25152 will be raised. For customers porting applications from previous releases of JDeveloper the trustMode will be set to true for existing Groovy expressions, though any new expressions still require developers explicitly set the trustMode.  follow these steps 1- Select the attribute of Entity or view object 2- click on Source tab to navigate to the XML source 3- change trustMode to be trusted