suggestion: have the oam... functions in a JS include

[Ernst Fastl <er...@gmail.com>]

Hi!

At the moment the JavaScript function which are starting
with oam (e.g. oamSetHiddenInput, oamSubmit, ...)
are rendered at the first commandLink or commandButton.

Is there a special reason for not having those in, for instance
commons.js

The PPR JavaScript for instance uses the oamSetHiddenInput function
and therefore only works if there is at least one commandLink or button
in the page.

some users which are developing custom components would also
like to have these functions permanently available.

thoughts?

kind regards

Ernst

Re: suggestion: have the oam... functions in a JS include

[Martin Marinschek <ma...@gmail.com>]

for me - not a problem.

but:

this function is only available then if you use MyFaces as an
implementation, not the RI. So it's not a good idea to rely on this
function being there beforehand!

regards,

Martin

On 5/21/07, Ernst Fastl <er...@gmail.com> wrote:
> Hi!
>
> At the moment the JavaScript function which are starting
> with oam (e.g. oamSetHiddenInput, oamSubmit, ...)
> are rendered at the first commandLink or commandButton.
>
> Is there a special reason for not having those in, for instance
> commons.js
>
> The PPR JavaScript for instance uses the oamSetHiddenInput function
> and therefore only works if there is at least one commandLink or button
> in the page.
>
> some users which are developing custom components would also
> like to have these functions permanently available.
>
> thoughts?
>
> kind regards
>
> Ernst
>


-- 

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces