SelectInputText With AutoSubmit, does not submit when used with LOV.

Question

Hi,
I am using ADF with ADFBC (Jdeveloper 10.1.3.3). I have a selectinputText (With AutoSubmit = true and immediate = true) component that links to a LOV dialog. When I enter values by hand and navigate out of SelectInputText, it submits the form and everything works well. But When I choose to use LOV, although its value is changed, it does not submit the form. I tried on Return Listener to set its value with no avail. I tried field.setSubmittedValue(null) and field.setValue, field.resetValue, But I couldn't get the same behaviour when I enter values by hand. So my problem is When return from LOV selectinputText does not submit the form. How can I have the form submitted when returned from LOV? Any help is appreciated.
Best Regards,
Salim

Answer 1

Well I was a bit to impatient to create a test case and wait what might come out. So I investigated a bit and found out:
The code in my managed bean for the value change listener is executed, when I change the field content directly. There is code placed like this:
public void invoiceAddressPartnerNrChange(ValueChangeEvent valueChangeEvent) {
int no = (Integer)this.getEditInvoiceAddressPartnerNo().getValue();
//valueChangeEvent.getNewValue() maybe use this in future...
this.getEditInvoiceAddressPartnerId().resetValue();
AttributeBinding ab =
(AttributeBinding)getBindings().getControlBinding("AllPartnersInvoiceAddressId");
int id;
// 1. Access the FacesContext
FacesContext fc = FacesContext.getCurrentInstance();
// 2. Create value binding for the #{data} EL expression
ValueBinding vb = fc.getApplication().createValueBinding("#{data}");
// 3. Evaluate the value binding, casting the result to BindingContext
BindingContext bc = (BindingContext)vb.getValue(fc);
// 4. Find the data control by name from the binding context
DCDataControl dc = bc.findDataControl("HdsServiceDataControl");
// 5. Access the application module data provider
ApplicationModule am = (ApplicationModule)dc.getDataProvider();
// 6. Cast the ApplicationModule to its client interface
HdsServiceImpl service = (HdsServiceImpl)am;
// 7. Call a method on the client interface
id = service.getPartnerId(no);
//return "SomeNavigationRule";
ab.setInputValue(id);
this.getEditInvoiceAddressPartnerId().setValue(id);
But this method will NOT be executed when the field content is changed by the LOV's returning value.
So I searched for another method and found the return listener of the field to be adequate. There I placed similar code by use of the return value:
public void test(ReturnEvent returnEvent) {
Object o = returnEvent.getReturnValue();
int no = Integer.parseInt(o.toString());
this.getEditInvoiceAddressPartnerId().resetValue();
this.getEditInvoiceAddressPartnerNo().resetValue();
AttributeBinding ab = (AttributeBinding)getBindings().getControlBinding("AllPartnersInvoiceAddressId");
int id;
// 1. Access the FacesContext
FacesContext fc = FacesContext.getCurrentInstance();
// 2. Create value binding for the #{data} EL expression
ValueBinding vb = fc.getApplication().createValueBinding("#{data}");
// 3. Evaluate the value binding, casting the result to BindingContext
BindingContext bc = (BindingContext)vb.getValue(fc);
// 4. Find the data control by name from the binding context
DCDataControl dc = bc.findDataControl("HdsServiceDataControl");
// 5. Access the application module data provider
ApplicationModule am = (ApplicationModule)dc.getDataProvider();
// 6. Cast the ApplicationModule to its client interface
HdsServiceImpl service = (HdsServiceImpl)am;
// 7. Call a method on the client interface
id = service.getPartnerId(no);
//return "SomeNavigationRule";
ab.setInputValue(id);
this.getEditInvoiceAddressPartnerId().setValue(id);
Since this method is executed, my calulation works both ways: Directly entered values and values coming back from the LOV.
Maybe this is kind of trivial and my code is a bit crappy, but it is a solution.
What I don't like is the redundance in the code I needed to implement twice..