This content has been marked as final. Show 4 replies
I am supposing that Table2 is already defined as a partial target of Table1 (as far as you said that it was refreshed whenever you changed the selected row in Table1). If it is not so, then mark Table2 as a partial target of Table1 (e.g. set Table2's "partialTriggers" attribute to reference Table1).
Mark then the standalone input field as a partial target of the Table1 in order to be submitted whenever Table1 causes a partial submit (e.g. set input field's "partialTriggers" attribute to reference the Table1).
If you have to do some special processing (e.g. not only standard data submit and validation) during a partial submit from Table1, then you may have to implement your own selection listener for Table1 (use the table tag's attribute "selectionListener").
What you are describing (i.e. values entered/modified in TABLE2 are not submitted/validated when the user navigates to another row in TABLE1) may happen only if TABLE1 is configured with <tt>immediate="true"</tt>. I created a simple test case in JDev 18.104.22.168 and checked that. This is not a bug but it is expected behavior. Please, have a look here in the documentation for an explanation:
[url http://docs.oracle.com/cd/E23943_01/web.1111/b31973/af_lifecycle.htm#CIACBJCJ]Using the Immediate Attribute
If <tt>immediate="true"</tt> at TABLE1, then a row selection event at TABLE1 is processed early at APPLY_REQUEST_VALUES phase and then processing goes directly to RENDER_RESPONSE phase, thus skipping data submission/validation from other components (e.g. from TABLE2).
If <tt>immediate="false"</tt> (or if it this attribute is not set at all), then everything works fine (i.e. values entered in TABLE2 are submitted and validated by the corresponding business component when the user navigates to another row in TABLE1 and the navigation does not succeed if there are some problems with the values entered/modified in TABLE2).
If you have set <tt>immediate="true"</tt> to TABLE1, please remove it and try the page again. However, if your problem is not related to the "immediate" attribute (e.g. you have not set <tt>immediate="true"</tt> to TABLE1, but you still experience the problem), then post your version of JDeveloper/ADF and post the start tags of both tables for further investigation.