Tableview navigation

Question

Hi,
I am trying to implement navigation event for my table view. For some reason, the event is not being captured.
I am trying to print a test message in the event implementation which is not printing, which means the event is not being captured.
Here is my Dynpage code:
     public void onMyOnNavigate(Event event) throws PageException {
          IPortalComponentResponse response = (IPortalComponentResponse) this.getResponse();
          response.write("Navigate Event ");     
          TableNavigationEvent tne = (TableNavigationEvent) event;
          if (myBean != null) {
               myBean.setVisibleFirstRow(new Integer(tne.getFirstVisibleRowAfter()).toString());
here is the JSP tableview declaration:
            <hbj:tableView
              id="myTableView1"
              model="myBean.model"
              design="ALTERNATING"
              headerVisible="true"
              footerVisible="true"
              fillUpEmptyRows="true"
              navigationMode="BYLINE"
              selectionMode="MULTISELECT"
              headerText="Compitency History"
              onNavigate="myOnNavigate"
              visibleFirstRow="1"
              visibleRowCount="4"
              width="500 px">
          </hbj:tableView>
And here is the bean code:
     public void setVisibleFirstRow(String visibleFirstRow) {
          this.visibleFirstRow = visibleFirstRow;
     public String getVisibleFirstRow() {
          return visibleFirstRow;
Can anyone tell me where am I going wrong..
(I even tried changing the event name to myOnNavigate
from onMyOnNavigate, but still it didn't work)
-Sudheer

Answer 1

result sounds like a very common name, likely this and similiar words are already used ...
In general, it is a good ides to maybe prefix your IDs, this avoids problems with existing IDs or functions:
For example, <b>tv_</b>result (tv for tableview).
In our current application I have a 60kb+ javascript file, lots of functions and variables in there, all are prefixed the one way or another, didn't run into any duplicate-name problems yet.