CODEWITHSUNDEEP
javajavascriptjsforacle-adfjdeveloper
Flattit82
Flattit82

Reputation: 63

ADF Web Application: how to add and modify UI components on page loading (before it's displayed)?

I would like to know which are the different available approaches to add, modify and delete UI components before a page loaded.

A practical example that I should handle is the following:

In my ADF Fusion Web Application (developed with JDev12.1.3) there are the pages login.jspx and main.jspx: if the user logs in correctly navigation to main.jspx happens.

In main.jspx there is an empty menu bar that at runtime I would like to fill with menus and menu items when the page loads, in function of the logged in user.

In the same page, in function of the logged in user, I also would like to add at runtime some UI components (output texts, buttons, ...) whith the chance to set their properties.

Could you kindly advice me which approaches I can follow to accomplish these duties?

Thanks, Federico

Upvotes: 0

Views: 2334

Answers (3)

Joe
Joe

Reputation: 3347

I see two approaches. Use addChild() and related methods to physically add/remove menu items, or have the menu pre-built and use the visible property to show hide items. As far as making this happen in custom code, you can use a Backing Bean (Managed Bean) that contains the code to determine what items to add/remove or make visible based on whatever criteria you choose. To call this code, you can 1) use the Invoke action in the rebinding layer - have it call the desired backing bean method - make sure to drag the Invoke action the TOP of the executables list. This is the older, less preferred method. The newer, more preferred method is to add the backing bean method to the Task flow and have it navigate to the deserted page. This method can be part of the navigation form another page. Ex: After successful Login, navigate to your method an chav sit navigate to the Main page. The method will execute before the page loads and will set values to have the items added or visible or not.

RichSelectOneChoice choiceList;
       List child = choiceList.getChildren();
       child.clear();
       for (int i = 0; i < child.size(); i++){
           child.remove(i);
       }

       if ("1..1".equalsIgnoreCase(ccCode)){
           UISelectItem addChild = new UISelectItem();
           addChild.setItemLabel("1..1");
           addChild.setItemValue("1..1");
           child.add(addChild);

       } else if ("0..1".equalsIgnoreCase(ccCode)){
           UISelectItem addChild1 = new UISelectItem();
           addChild1.setItemLabel("0..1");
           addChild1.setItemValue("0..1");
           child.add(addChild1);
           UISelectItem addChild2 = new UISelectItem();
           addChild2.setItemLabel("1..1");
           addChild2.setItemValue("1..1");
           child.add(addChild2);

       }

Have you posted this question to he ADF forum, here?

Upvotes: 1

Endrik
Endrik

Reputation: 2258

Personally the two approaches i've used on my works where:
1. Using the beforePhaseListener on the f:view component. Example: Before Phase on JSF page. But it might cause you some problems when taking account of adf lifecycle, especially if you have integrated parts (or even some simple jQuery components...).
2. And i think this would just do fine in your case, use a f:event component of type "preRenderComponent". Example: How to use prerendercomponent. I suggest this second option
Note: It's true that these aren't ADF Faces components, but since it's built on top of JSF, they work as they should. I can assure you they do work on 11g and don't expect any problems on 12c.

Upvotes: 1

Sydney
Sydney

Reputation: 12212

Why not using the rendered attribute? Based on the condition the components will be rendered or not.

Upvotes: 1

Related Questions