Declarative Component State

If I define a decl component the docs indicate the associated bean should have backingBean scope so that if there
are multiple instances of the component on the same page requests are routed correctly. backingBean scope
appears to be request scope for decl components.
If a decl component contains adf components such as a menu that has state that must be saved across requests
what strategies are available to get/set this state when there are multiple decl components on a page?
Thanks,
-Dave

Hi Venkat, thanks for your response.
I have tried jsff. It is useful if I have only one address component on the page. but in my case we have two address components (mailing & permanent) on my page. In this case, I wanted to change the value attribute bindings for both the components and not LOV modal attributes for country and state.
Thanks,
Viswa.

Similar Messages

Declaring skin states in an MXML component?

From the docs, you can declare skin states in a .as file before the class declaration, like this:
[SkinState("up")]
[SkinState("over")]
[SkinState("down")]
[SkinState("disabled")]
public class Button extends Component { .. }
But how do declare states in a .mxml file? There is no "public class ..." statement to precede.

So maybe this isn't possible? I have had such a hard time finding docs on the component side of the skinning contract.

Declarative component stops working after taskflow-call-in-popup

Hi!
JDev 11.1.1.3.0
I need a component, much like the commandToolbarButton, but I have the requirement that the user should still be able to select from the popup even if the button is disabled.
So I created a declarative component, combining two buttons and a popup with a menu in a panelGroupLayout. The one button, the mainButton, actually executes the action, the other (with an icon only) opens a menu in a popup.
The user selects an item from the popup, the component then PPRs the main button in code to display the user's choice in the main buttons text.
    <af:panelGroupLayout layout="horizontal" id="${component.id}_layout">
      <af:commandToolbarButton id="mainButton" text="#{component.mainButtonText}"
                               clientComponent="true" disabled="#{!component.enabled}"
                               partialSubmit="true"
                               actionListener="#{component.mainButtonPressed}"/>
      <af:commandToolbarButton id="menuButton" icon="/images/arrowDownComboBox.png"
                               partialSubmit="true" disabled="#{!component.enabled}">
        <af:showPopupBehavior alignId="mainButton" align="afterStart" popupId="commandPopup"/>
      </af:commandToolbarButton>
      <af:facetRef facetName="extensionButton"/>
      <af:popup id="commandPopup" contentDelivery="lazyUncached" childCreation="immediate"
                clientComponent="true">
        <af:menu id="commandMenu" clientComponent="true" binding="#{component.commandMenu}"/>
      </af:popup>
    </af:panelGroupLayout>That works fine ... until the user opens a taskflow in a popup.
I have a bounded taskflow, jspx-based, opened by a button with an action that navigates to a taskflow-call activity in a modal dialog. The user opens the taskflow, does what needs to be done, then closes the dialog.
Still fine.
But, after the dialog has closed, when the user selects an item from the popup menu of my declarative component, I suddenly get an NPE:
<26.04.2011 19:07 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <<RegistrationConfigurator><handleError> Server Exception during PPR, #1
java.lang.NullPointerException: UIComponent is null
     at org.apache.myfaces.trinidad.component.UIXComponent.addPartialTarget(UIXComponent.java:498)
     at org.apache.myfaces.trinidadinternal.context.RequestContextImpl.addPartialTarget(RequestContextImpl.java:513)
     at com.ge.med.web.components.button.CommandComboButton.refreshMainButton(CommandComboButton.java:213)
     at com.ge.med.web.components.button.CommandComboButton.setSelectedCommand(CommandComboButton.java:177)
     at com.ge.med.web.components.button.CommandComboButton.commandItemPressed(CommandComboButton.java:243)
     at com.ge.med.web.components.button.CommandComboButton.processAction(CommandComboButton.java:129)
     at javax.faces.event.ActionEvent.processListener(ActionEvent.java:88)To track the problem down, I have pointed the binding attribute of the declarative component to a property in a session-scoped bean, to see what the component looks like that is set, what the children and grand children are, and who the parent is.
This prints:
<26.04.2011 19:07 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <Setter called: DemoComboButtonComponent[oracle.adf.view.rich.component.fragment.UIXInclude$ContextualFacesBeanWrapper@1762a87, id=demoAdd]>
<26.04.2011 19:07 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <Parent: RichPanelGroupLayout[UIXFacesBeanImpl, id=cbll1]>
<26.04.2011 19:07 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <Children: [RichPanelGroupLayout[UIXFacesBeanImpl, id=demoAdd_layout]]>
<26.04.2011 19:07 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <Grand kids: [RichCommandToolbarButton[UIXFacesBeanImpl, id=mainButton], RichCommandToolbarButton[UIXFacesBeanImpl, id=menuButton], RichPopup[UIXFacesBeanImpl, id=commandPopup]]> That's fine. But when I add the same debug code to my setSelectedCommand() method (which is called when the user selects an item from the popup's menu), I get:
<26.04.2011 19:07 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <I am: DemoComboButtonComponent[oracle.adf.view.rich.component.fragment.UIXInclude$ContextualFacesBeanWrapper@ba2b1c, id=demoAdd]>
<26.04.2011 19:07 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <My Parent: null>
<26.04.2011 19:07 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <My Children: []> The empty children property explains the NPE. This NPE only happens when the user selects an item from the popup after the dialog has closed.
Debugging showed that the new DemoComboButtonComponent is created during the restoration of (tree) state after the closing of the modal dialog. But why has it no parent? And where are the kids?
Could the binding of the declaratice component to a session-scoped bean be the problem? Somehow prevent the state mechanism from re-building the UI component tree correctly?
I am at the end of my wits.
Any help is appreciated!
Sascha

Hi Frank,
no, not yet. I had the feeling that it's me who is doing something wrong. Declarative components are pretty common, right? So are taskflow calls in dialogs. Someone should have noticed if there's a bug in the framework, right?!
But I changed the scope of the bean (to backing scope and request scope) that the declarative component is bound to and I still get the error.
I will try to create a simpler test case, and if I can reproduce with that, then I will file a bug, if there's no one that can explain the phenomenon.
Sascha

SkinState vs. component state

I wrote some Gumbo prototypes recently and found it confusing that skinStates are independent of component states (currentState). I tried to imagine scenario when host component state should be different than its skin state but I cant find any.
I have found that component states are used in item renderes, which in my opinion violates of skinning concept (see ARB http://opensource.adobe.com/wiki/display/flexsdk/Gumbo+Updated+Item+Renderer )
What do you think about syncing surrentState with skinState?
In such a case it would be easier for developer to migrate from MXML inline item renderer to fully skinnable one as states of both, inline MXML component and MXML skin, will be the same.

You write your state implementations the same way. SkinStates is just a formal mechanism for saying that your skin should support those states.   But since your skin is just like an MXML component, what you end up writing is the same. For your application components you’re simply declaring them to meet “business” rules, while in skins you’re doing it more for interaction rules.
Matt
On 3/24/09 7:37 AM, "Haykel Ben Jemia" <
[email protected]> wrote:
A new message was posted by Haykel Ben Jemia in
Developers --
  skinState vs. component state
I have used skin states and thought it was the new way of using states. I was not aware that the 'old' component states are still available and can be used. Some examples on using both would probably help understand how both state types can be used together. I'll see if I can find some interesting use cases.
Haykel Ben Jemia
Allmas
Web & RIA Development
http://www.allmas-tn.com
On Mon, Mar 23, 2009 at 5:20 PM, Greenfield Eliot <
[email protected]> wrote:
A new message was posted by Greenfield Eliot in
Developers --
  skinState vs. component state
We had them coupled originally. Surprisingly, if you’ve written a Spark app, you’ve already run into this. Any time you use a skinned spark component as the root tag of your MXML file (including FxApplication), and add your own states, you’re creating component states that are separate from any skin states.
Ely.
On 3/23/09 3:50 AM, "Tom Chiverton" <
[email protected] <
http://[email protected]> > wrote:
A new message was posted by Tom Chiverton in
Developers --
  skinState vs. component state
On Friday 20 Mar 2009, Iwo Banas wrote:
> What do you think about syncing surrentState with skinState?
I'm trying to think of use cases where the internal state of the component may
be detached from the showing of that state, and I've come up with one:
Suppose a component has two skin states - OK and FAIL, and it has to call an
external service to check something to computer the state (i.e. state
transitions are asynchronous). There might be OK, UNKNOWN and FAIL states,
but only two skins (UNKNOWN being the same as FAIL).
View/reply at skinState vs. component state <
http://www.adobeforums.com/webx?13@@.59b85be2/1>
Replies by email are OK.
Use the unsubscribe <
http://www.adobeforums.com/webx?280@@.59b85be2%21folder=.3c060fa3> form to cancel your email subscription.
View/reply at skinState vs. component state <
http://www.adobeforums.com/webx?13@@.59b85be2/4>
Replies by email are OK.
Use the unsubscribe <
http://www.adobeforums.com/webx?280@@.59b85be2!folder=.3c060fa3> form to cancel your email subscription.

11.1.2: Declarative-component problem!

Hi!
We're just evaluating 11.1.2. I converted some declarative components to 11.1.2/Facelets style, but I am running into problems.
As a test, I created some new components from scratch, confirming the issue.
I create a declarative component and choose "Facelets" and choose "Use custom component class".
JDeveloper then creates an entry in the jsf:
        <afc:component>
            <afc:display-name>testComponent</afc:display-name>
            <afc:component-class>component.TestComponent</afc:component-class>
            <afc:facet>
....After deployment, I just get an error. Facelets is reporting that there is no tag for "component-class", and examining component.taglib.xml in adf-richclient-impl-11.jar shows: Facelets is right! There is none!
Now, I cannot just remove the component-class entry. If I do that, then deployment works, but then JDeveloper creates during compilation a wrong "TestComponentComponent" class (which should extend TestComponent but doesn't!).
It just extends RichDeclarativeComponent, just like my original TestComponent class. All code in TestComponent is not available at runtime.
RichDeclarativeComponent
   |
   |
TestComponent    <---- This class is now for the birdsand
RichDeclarativeComponent
   |
   |
TestComponentComponent      <----- That class is used by the handlerIf I leave the component-class entry in, then - as expected - I get the correct hierarchy:
RichDeclarativeComponent
   |
   |
TestComponent
   |
   |
TestComponentComponentbut the component doesn't run.
So, now what? This cannot be the way it's supposed to work, can it. Manually edit the "component-class" stuff out of the jsf in the jar after deployment!?
Edit: Created SR 3-3856944401: Facelets-based declarative component with custom component class not working
Sascha
Edited by: Sascha Herrmann on Jun 17, 2011 6:41 PM

This is bug 12717940.
Sascha

Using a different default component state within each page state

I am using a custom component in multiple page states but would like to have a different default state (for the same custom component) within each page state.
Is there anyway to use a different default component state within each page state .
When I change the default state at a component level it seems to go across all my page states. Any solutions?
Thank you

I guess I can just add that interaction for that component!
I think my brain is just catching up

Error while saving changes of declarative component to MDS

Hi,
Using ADF Faces 11gR1PS1.
I am trying to create a declarative component where user can close a panel box (not just minimize) by setting rendered property to false. It works fine.
Next I tried to save the attribute change to MDS so that user settings are preserved across sessions. However I got the following error:
<FilteredPersistenceChangeManager><_getQualifiedTagName> WebAppDesignContext is not available at application scope. Please ensure that your application is built as a 'Fusion Web Application (ADF)', and that taglib.jar and facesconfigmodel.jar are in class path.
<FilteredPersistenceChangeManager><_isChangeAllowedThroughPersistentChangeManager> Could not obtain tag name for the component being changed. Component ref: RichPanelBox[UIXFacesBeanImpl, id=dc_pb2]
<FilteredPersistenceChangeManager><_addDocumentChangeImpl> The DocumentChange is not configured to be allowed for the component: RichPanelBox[UIXFacesBeanImpl, id=dc_pb2]Following is the page code:
          <af:panelBox text="#{attrs.p2Header}" id="dc_pb2"
                       rendered="#{attrs.p2Header ne null and dashboardXBean.portletRendered.dc_pb2}"
                       showDisclosure="false">
            <af:componentDragSource discriminant="portlet"/>
            <f:facet name="toolbar">
              <af:commandImageLink id="p_cil2"
                                   icon="/images/removeselected_dwn.png"
                                   hoverIcon="/images/removeselected_ovr.png"
                                   depressedIcon="/images/removeselected_ena.png"
                                   actionListener="#{dashboardXBean.handleHideEvent}"
                                   rendered="#{attrs.sideNavRendered}">
                <f:attribute name="portletId" value="dc_pb2"/>
              </af:commandImageLink>
            </f:facet>
            <af:facetRef facetName="p2"/>
          </af:panelBox>Following is the code in the managed bean to persist changes:
    private void saveShowHideChange(String portletId, boolean isRendered) {
        FacesContext fc = FacesContext.getCurrentInstance();
        ChangeManager cm = RequestContext.getCurrentInstance().getChangeManager();
        //ChangeManager pcm = AdfFacesContext.getCurrentInstance().getPersistentChangeManager();
        UIComponent puc = boundedDashboard.findComponent(portletId);
        ComponentChange pcc = new AttributeComponentChange("rendered", Boolean.toString(isRendered));
        cm.addComponentChange(fc, puc, pcc);
    }I am not really sure if the above code needs to be in the component managed bean or in the bean of the page that uses this declarative component.
Any pointers are appreciated.
Thanks,
Husain

Thanks for the reply Frank.
For declarative components do we have separate renderer?
The [Developers Guide|http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/ad_persist.htm#BABBGCJA] didnt seem very helpful on this topic.
Can you point me to some reference material if available.
Thanks,
Husain

JDeveloper 11.1.2.3, ADF Faces: need declarative component idea for table

Some background:
I'm trying to create a reusable toolbar for standard af:table behavior, see screen shot
http://wesfang.files.wordpress.com/2013/05/dc.jpg
I got the idea from the from using documentation Frank has published in the past
1. http://www.oracle.com/technetwork/developer-tools/adf/learnmore/001-access-declarative-comp-attr-169113.pdf
2. Adding a new row programatically
The consuming subsystem's page passes in a "MyPageBean" which is a subclass of a "ArchBean" where all actionlistener operations are defined. The idea here is to minimize developer customization when using this component.
... <f:facet name="toolbar">             <af:toolbar id="t2">                 <mskcc:basicTransactionToolbar id="btt1" pageBean="#{MyPageBean}" tableId="t1"/>             </af:toolbar> </f:facet> ...
The table within the consuming page is by default dropped off as a "editable" table. The developer needs to further modify the "disable" attribute to true for all the input fields and command components within the table. I would like to remove this developer step and instead have it in an architectural component. All ideas are welcome.

Ok, finally got it working (sort of)
Using the following method as you suggested:
public void encodeChildren(FacesContext fc){
        try {
            super.encodeChildren(fc);
            RichTable table =
                (RichTable)ADFFacesUtil.findComponentInRoot((String)this.getAttributes().get("tableId"));
            lockUnlockTable(table); //method for toggling disable attribute for all command and input components
        } catch (IOException e) {
            e.printStackTrace();
}Now the strange problem I encountered is that the encode methods are not called if the declarative component is defined within a panelCollection's f:facet-toolbar like below:
<f:facet name="toolbar">
                    <mskcc:basicTransactionToolbar id="btt1" tableId="t1" pageBean="#{TestBean}"/>
</f:facet>Also the above code has to be manually created because the design time editor does not allow me to drop off the dc within the toolbar facet (even though the dc is a toolbar!)
Instead, If I move the dc outside the panelcollection, then the encode methods are invoked and the desired enable/disable behavior is correctly displayed.

JDeveloper 11.1.2.3, ADF Faces: declarative component does not support af:clientListener?

I am trying to create a declarative component with the following code:
<?xml version='1.0' encoding='UTF-8'?>
<af:componentDef xmlns:af="http://xmlns.oracle.com/adf/faces/rich" var="attrs" componentVar="comp" definition="private"
                 xmlns:afc="http://xmlns.oracle.com/adf/faces/rich/component">
    <af:xmlContent>
        <afc:component>
            <afc:display-name>DoubleClickTableDialogClientServerListener</afc:display-name>
            <afc:component-extension>
                <afc:component-tag-namespace>org.mskcc.crdb.common.declarativecomponent</afc:component-tag-namespace>
                <afc:component-taglib-uri>http://www.mskcc.org</afc:component-taglib-uri>
            </afc:component-extension>
        </afc:component>
            <af:clientAttribute name="serverListenerType" value="TableDoubleClickEvent"/>
            <af:clientListener method="handleTableDoubleClick" type="dblClick"/>
            <af:serverListener type="TableDoubleClickEvent"
                               method="#{EditAddDialogTemplateBean.handleTableDoubleClick}"/>
    </af:xmlContent>
</af:componentDef>
At runtime I recieve the following error:
javax.faces.view.facelets.FaceletException: ADF_FACES-60023:Component: DoubleClickTableDialogClientServerListenerComponent[oracle.adf.view.rich.component.fragment.UIXInclude$ContextualFacesBeanWrapper@7170a7, id=dctdcsl1] does not support client listeners.
at oracle.adfinternal.view.faces.facelets.rich.BaseClientListenerHandler.apply(BaseClientListenerHandler.java:53)
This component was intended to be dropped off within an af:table component. I would like to hear suggestions on workarounds, one other way I thought about was to create a code template for the three tags, however, the con to this approach is each developer would need to configure this template within jdeveloper. Ideas are appreciated.
Also a side question, how can I embed code properly with the new forum? [code] tag does not seem to work now.

Wes, can't help with the real question, but can tell you how to format code
Change to the advanced editor (top right over the editor field), then you get more options. The one you are looking for is behind the blue '>>'. Here you select the language you want to insert and you get nice code formatting and color.
Timo

Error in accessing attributes of a declarative component in BackinBeanScope

Hello,
I'm using JDeveloper 11.1.1.4.0.
For pagination we have created a declarative component. It's bean when in request scope works fine when the dec.comp. is used in page only once.
In order to use it multiple times in the same page, I changed the scope to BackingBeanScope. It works fine the first time bean's method gets called. However on the next request, I'm getting NullPointerException when it tries to access the dec. comp's attribute.
Why am I getting this error and how to correct it?
As an alternative, we can store the attribute value received first time in a hidden form field and retrieve it every subsequent time. But this would be my last alternative.
Appreciate a reason and a better way to resolve this.
Regards,
Amar

Hi,
Yes. The bean is declared in the dec. comp.
Following is the code in my bean's c'tor:
FacesContext fc                    = FacesContext.getCurrentInstance();
ELContext elctx                    = fc.getELContext();
ExpressionFactory elFactory    = fc.getApplication().getExpressionFactory();
ValueExpression valueExpr      = elFactory.createValueExpression(elctx, "#{component}", UIXDeclarativeComponent.class);
UIXDeclarativeComponent currDeclarativeComp            = (UIXDeclarativeComponent)   valueExpr.getValue(elctx);
String currVOObjectName                                         = currDeclarativeComp.getAttributes().get("VOObject").toString();"VOObject" is the attribute name for the dec. comp. It's getting correct value the first time. Every subsequent time,the last line throws null pointer exception.
Regards,
Amar

Embedding a declarative component written in JSF 1.2 in a jsf page

Hi ,
I have a declarative component written in JSF 1.2 . I want to embed this declarative component in an ADF application which is using JSF 2.0.
On creating a jspx page in JSF 2.0 & embedding decalrative component it just works fine but I have to embed it in a JSF page instead , which is not working.
Any suggestions ?
Thanks
Vinit

Hi,
for JDeveloper 11g R2 you will need to know before whether the application you build uses JSPX page documents or Facelets. The technologies are different (introduced with JSF 2) and declarative components thus need to be build for the document type used by teh application
Frank

Creating Declarative Component problem.

Dear all
I use Jdeveloper 11.1.1.4.0.
I am planing to create an ADF declarative Component.The component will be a panel collection layout which contains menu (Action>Export to excel) and command button (Add new record).
The scenario will be like this:
1- The developer will drag my new component (myCustomPanel) to his page and will drag the data control inside this comonent to create ADF Read only table.
2- at runtime the table should appear surrounded by (myCustomPanel) and the user can use the "Action" menu to export the content to Excel, and can click on "Add new Record"to navigate to another page to add record.
The solution I made is:
in my "myCustomPanel" I created two attributes , the first one is "tableID" and the second is "targetPage" represents the outcome of the navigation to the "Add new record" page.
The developer must provide these two attributes when using "myCustomPanel".
The problem is:
at runtime when the user click on "Add new record" button an error is raised .
The error in this line:
<af:commandToolbarButton text="Add" id="dc_ctb1" action="#{attr.targetPage}"/>
the action property of the command button expects a managed bean. But i proved it with page attribute.
I want to dynamicly provides the naviation outcome to the button using attribute name. Is this possible?
regards

Thank you so much for you replying.
Your solution is helpful
I tried to do the following :
1- in my "customcomponent" project I removed the attribute "taregtPage"
2- I added a method attribute
name: targetPage
method-signature: java.lang.String method()
<af:componentDef var="attrs" componentVar="component">
    <af:panelCollection id="collection">
      <f:facet name="menus">
        <af:menu text="Action" id="dc_m1">
          <af:commandMenuItem text="Export To excel" id="dc_cmi1"/>
        </af:menu>
      </f:facet>
      <f:facet name="toolbar">
        <af:toolbar id="dc_t1">
          <af:commandToolbarButton text="Add" id="dc_add"
                                   action="#{attrs.targetPage}"/>
        </af:toolbar>
      </f:facet>
      <f:facet name="statusbar"/>
      <af:facetRef facetName="tableContent"/>
    </af:panelCollection>
    <af:xmlContent>
      <component xmlns="http://xmlns.oracle.com/adf/faces/rich/component">
        <display-name>dhamanTable</display-name>
        <facet>
          <facet-name>tableContent</facet-name>
        </facet>
        <attribute>
          <attribute-name>tableID</attribute-name>
          <attribute-class>java.lang.String</attribute-class>
          <required>true</required>
        </attribute>
        <component-extension>
          <component-tag-namespace>dhaman.custom</component-tag-namespace>
          <component-taglib-uri>/componentLib</component-taglib-uri>
          <method-attribute>
            <attribute-name>targetPage</attribute-name>
            <method-attribute>
              <attribute-name>targetPage</attribute-name>
              <method-signature>java.lang.String method()</method-signature>
            </method-attribute>
            <required>false</required>
          </method-attribute>
        </component-extension>
      </component>now My question is how to use it?
I do not understand this
action="#{component.handleTargetPage}" Do you mean that i will create amanaged bean "component" and add a methos "handleTargetPage"??
Edited by: ta**** on Mar 9, 2011 1:58 PM
Edited by: ta**** on Mar 9, 2011 2:00 PM
Edited by: ta**** on Mar 9, 2011 2:01 PM

Access InputText Value in Declarative Component

Hi,
I have created a declarative component that contains an inputText component:
<af:inputText label="#{attrs.ucitLabelText}" id="dc_it1" contentStyle="text-transform:uppercase;" converter="StringAsUppercase"/>
When I use the declarative component on a page, is there any way to easily access the value of its inputText through the page backing bean? The declarative component is bound to the page, but what method can I use to access the inputText value?
Thanks,
Brad

Thanks.
I also figured out that I can simply do the following:
When creating the declarative component...
- Add an attribute to the declarative component (let's call it "inputValue")
- Assign the inputValue attribute to the inputText value.
When using the declarative component on a page...
- Create a String property in the page's backing bean
- Assign that property to the declarative component's inputValue attribute
Then I can access the backing bean property to get the inputText value.
Brad

ADF:LOV declarative component not working inside table component.

Hi,
I have created a custome LOV control,I am using this custom LOV control inside the table component,I am passing the below values as the parameter
KeyValue="#{row.bindings.Value.inputValue}"
LovModel="#{row.bindings.Value.listOfValuesModel}"
Value- is the list of value attribute.
When i click on the LOV search icon, the popup displays the Query model(it displays the list name at the top in the search page.so it is able to recognise the LOVmodel) but it is not able to retrive the list values.I am getting Query page with no values
in the jspx page it is giving warning as "reference not found for row.bindings.Value.listOfValuesModel"
Please can anyone help me on this?
Thanks,
Harish

Hi Frank,
below is my actual requirement and the solution i tried till now.
I have a table and it has two columns let’s say “Columns” and “Values”. The first column i.e. “Columns” will be a dropdown and it will have predefined values, the other column “Values” will be a “List of value” control or similar kind of control in which the user can search and select multiple values from the popup list, and that list should dynamically bounded to the first column selected value.
For Ex: if I select a value “Product” from the dropdown of the first column “Columns” , the control in the other column “Values” should bound to “product” list and I should be able to search and select multiple values from the pop up. And the popup should return the multiple selected values as a comma separated string to the textbox.
In my requirement I have to use only VO’s to create the list and the control in the “Values” column should switch between these VO’s depending on the value selected in the first column.
The solution we tried till now.
I used a LOV switcher to achieve the above requirement. But we have a limitation in this approach as we could not do the multi select. Then we created a declarative LOV component in which we can select multiple values as a comma separated string from the popup.
I retained the LOV switch model , instead of binding LOV switch model to the basic “Input List of Value” control in the JSPX page ,I used the LOV declarative component. Below is the code snippet which calls the declarative LOV component from JSPX page.
<af:panelFormLayout id="pfl2">
<af:selectOneChoice value="#{bindings.Columns.inputValue}"
label="#{bindings.Columns.label}"
required="#{bindings.Columns.hints.mandatory}"
shortDesc="#{bindings.Columns.hints.tooltip}"
id="soc3" autoSubmit="true">
<f:selectItems value="#{bindings.Columns.items}" id="si5"/>
</af:selectOneChoice>
<mc:OraMultiSelect
KeyValue="#{bindings.Value.inputValue}"
LovModel="#{bindings.Value.listOfValuesModel}"
id="oms2"/>
</af:panelFormLayout>
Where Value attribute is having LOVModel.
The above code perfectly fine as I used it inside the “Form layout” and with the parameters passed as KeyValue="#{bindings.Value.inputValue}"
LovModel="#{bindings.Value.listOfValuesModel}"
The problem I am facing:
The actual problem comes when I use this control inside the table which I required in my implementation.
I called the declarative LOV control as shown below inside the table as I used to call the basic “Input List of value” control which works fine inside the table.
. <af:column sortProperty="Value" sortable="false"
headerText="#{bindings.OpPlanning1.hints.Value.label}"
id="c1" width="133">
<mc:OraMultiSelect KeyValue="#{row.bindings.Value.inputValue}"
LovModel="#{row.bindings.Value.listOfValuesModel}"
id="oms1"/>
</af:column>
Above code doesn’t works fine when I select value from the “Column” dropdown it displays the corresponding list model in the pop up but not able to retrieve the value of the list in the popup .
If I pass the parameters as
. <af:column sortProperty="Value" sortable="false"
headerText="#{bindings.OpPlanning1.hints.Value.label}"
id="c1" width="133">
<mc:OraMultiSelect KeyValue="#{bindings.Value.inputValue}" --instead of ="#{row.bindings.Value.inputValue}"
LovModel="#{bindings.Value.listOfValuesModel}"--}" --instead of ="#{row.bindings.Value.inputValue}"
id="oms1"/>
</af:column>
It works fine for the first row.The subsequent rows refers the value selected in the first row dropdown.
Thanks For the help,
Harish
Edited by: 886523 on Nov 3, 2011 8:04 AM

Component level message are not coming up for the declarative component.

Hie
i am using ADF faces with jdev 11g.
i have created a declarative component and dropped it in my web application.
This component provides an action listener to write some app specific code.
in the listener i wrote a component level error message.
on running the app i can see that it is going to that error but it is not showing it up on the ui. same code works for other adf faces components that comes by default in the component pellete.
I tried setting the clientComponent attribute to true as well but no luck.
any idea if something wrong with declarative components?

Frank,
My declarative component is dropped on my jsff. In this pages i have dropped a af:messages as well.
There is a small button in my component on which i have bound an action listner.
In the action listener i have a validation on the failure condition of which i have the code like:
if(bean == null || bean.isAuthenticated() == false){
FacesMessage msg = new FacesMessage(FacesMessage.SEVERITY_ERROR, null, "You must be logged in to vote up");
FacesContext context = FacesContext.getCurrentInstance();
context.addMessage(getVotingQuesComponent().getClientId(context), msg);
AdfFacesContext.getCurrentInstance().addPartialTarget(getVotingQuesComponent());
return;
So, i m sure my flow is going in this part of code but i dont see the message coming up marking my declarative component.
However, if i replace this message by a page level error message then that comes up fine.

Declarative Component State

Similar Messages

Maybe you are looking for