Ed Burns wrote:
>>>>>>On Fri, 22 Oct 2004 11:16:02 -0700, Adam Winer <adam.winer_at_oracle.com> said:
> AW> FWIW, what we (Oracle UIX) did for this category of problem
> AW> was to take *all* the "NeededHiddenFields" and explicitly
> AW> null them all out in Javascript before continuing with the
> AW> code that sets parameters and then submits.
>
> That's what I want to do. However, where do you hang the javascript?
> On the form? If so, how do you make it so the nulling out happens
> BEFORE the parameter setting code?
We cheat (slightly). Instead of allowing calls to form.submit(),
we direct everything through a submitForm() call that handles;
(1) Running client-side validation logic
(2) Clearing old parameters
(3) Setting the new parameters
(4) Submitting the form
... in that order.
-- Adam
>
>>>>>>On Fri, 22 Oct 2004 14:30:53 -0500, Jacob Hookom <jacob_at_hookom.net> said:
>
>
> JH> One thing I could suggest in for areas where we generate Javascript, if
> JH> the attribute already has a value, prepend our script to the existing
> JH> value. I'm not sure if the renderkits already works that way?
>
> JH> onClick="alert('Developer debugging');"
>
> JH> becomes
>
> JH> onClick="injectedScript(); alert('Developer debugging');"
>
> That's a good idea to address Adam's initial concern, but it seems like
> there would be some cases where we would break user code.
>
> Ed
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_javaserverfaces.dev.java.net
For additional commands, e-mail: dev-help_at_javaserverfaces.dev.java.net