Normally when autoUpdate="true" any action will lead to an update. The
actions include navigation, sorting or even filtering. Sometimes this is not
the intended effect I disable it by putting autoUpdate="false" so that the
user can only update by explicitly invoking the update event.
It's possible if you do three things (hacks at this point):
1) alter the source in EventEnging. generateSecundaryEvents
from if (ParseUtil.getParameter(request, param).equalsIgnoreCase("true"))
toif (ParseUtil.getParameter(request, param).equalsIgnoreCase("true")||(ParseUtil.getParameter(request, param).equalsIgnoreCase("OnUpdateOnly")&&exclude.getType().equals("update")))
2) set autoUpdate="OnUpdateOnly" in your tag
3) set overrideFieldCheck="true" in your tag --- this will call an update if you hit the update button even when no data has changed. So really there will be no effect unless you interceptors would do something in that case. I don't know why at this point and haven't the time just now to go further, but unless this is set as so, you will get a null pointer when onUpate="true" and then using a navigation event (not an update event)
If you want to toy with it and figure it out further we could get that change committed. Unfortunately I have used up all my short free time to get this far.
--
Shawn
Happily using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
