Table SelectionEvent not fired after filtering

Question

Hi,
consider the following scenario (ADF 11g Dec. 2008 build): a filterable af:table with 3 rows and RowSelection="single".
Row 1, the first one, starts as current and is highlighted in the table.
Now, apply a query-by-example so that only rows 2 and 3 are visible. The af:table thus highlights row 2 because it's the first of the two remaining rows... however, no SelectionEvent is fired in that case so no MakeCurrent takes place, and the user thinks the current row is row 2 but instead the underlying iterator isn't updated. User is forced to click on row 3 and then on row 2 again to make row 2 current (= fire a SelectionEvent). This also completely defies all the logic we put in our custom SelectionListener (it does MakeCurrent then updates a region in the page according to the selected row in the table).
An even bigger problem in the scenario above is that if you filter so that only row 3 is shown, it gets automatically highlighted and then there's no way to make it current at all, since the af:table in your browser won't let you "select" a row which is already highlighted. That is, the SelectionEvent only fires if a user manually clicks on a row which is not currently highlighted in the table.
This happens for all af:tables no matter the properties set, even after straight drag-and-drop of a VO to the .jspx page.
This behaviour seems just broken, if the af:table does highlight/select a row automatically client-side, it should send a SelectionEvent to the server so that a MakeCurrent can be performed, keeping the iterator's current position in sync with what the user sees.
Is there a way to workaround this issue? I'd say "fix af:table" would be the solution, but if these problems are still here I guess it's been designed this way? (...why?)
Any help would be appreciated.
thanks,
Riccardo

Answer 1

this is my php connection file
<?php
  $username = "kependudukan";
  $password = "kependudukan";
  $dbname = "localhost/XE";
  $c = oci_connect ($username, $password, $dbname);
  if (!$c) {
  echo "Koneksi ke server database gagal dilakukan";}
  //else {
  //echo "Konekasi ke server database sukses";}
?>
Everything works fine except the trigger..
I use Windows 7 Professional 32-bit
intel core i-3
RAM 2GB