Hi
2010/5/11 Jakob Korherr
> Hi,
>
> However this also means that custom component libraries (e.g. Trinidad)
> that have ClientBehaviorHolder-components have to implement the logic to
> detect and render jsf.js on their renderers too, right?
>
> Can we do something better here or is this a spec
Hi,
However this also means that custom component libraries (e.g. Trinidad) that
have ClientBehaviorHolder-components have to implement the logic to detect
and render jsf.js on their renderers too, right?
Can we do something better here or is this a spec problem/issue?
Regards,
Jakob
2010/5/10
Wow, thank you for the clarification.
Leonardo Uribe schrieb:
Hi
2010/5/10 Ganesh mailto:gan...@j4fry.org>>
Hi Leo,
I'm not sure we're talking about the same thing: The point Andrew
and me where making is that it could be good to render jsf.js inline
for f:ajax and and custom
Hi
2010/5/10 Ganesh
> Hi Leo,
>
> I'm not sure we're talking about the same thing: The point Andrew and me
> where making is that it could be good to render jsf.js inline for f:ajax and
> and custom behaviours if no h:head is present. Was this what you where
> talking about?
>
>
Yes, the conditi
Hi Leo,
I'm not sure we're talking about the same thing: The point Andrew and me where
making is that it could be good to render jsf.js inline for f:ajax and and
custom behaviours if no h:head is present. Was this what you where talking
about?
Best regards,
Ganesh
Leonardo Uribe schrieb:
H
Hi
2010/5/9 Jakob Korherr
> Hi Leo, Ganesh,
>
> Yes, good approach, Leo :)
>
> However I think we should do what Ganesh proposed, that means we should
> fall back to an inline rendering of jsf.js if h:head is not present in
> addition to adding a FacesMessage and/or log entry.
>
>
The algorithm
Hi
2010/5/9 Ganesh
> Hi Leo,
>
> +1, good approach!
>
> 1 question: Why do 1.+2. require a h:head to be present while 3.-5. render
> jsf.js inline? Wouldn't it be possible to *always* try and push it to h:head
> and if h:head is not defined *always* fall back to inline?
>
>
That's the idea. In f
Hi Leo, Ganesh,
Yes, good approach, Leo :)
However I think we should do what Ganesh proposed, that means we should fall
back to an inline rendering of jsf.js if h:head is not present in addition
to adding a FacesMessage and/or log entry.
The problem, Ganesh, with pushing it to h:head is, that th
Hi Leo,
+1, good approach!
1 question: Why do 1.+2. require a h:head to be present while 3.-5. render
jsf.js inline? Wouldn't it be possible to *always* try and push it to h:head
and if h:head is not defined *always* fall back to inline?
Best regards,
Ganesh
Leonardo Uribe schrieb:
Hi
Chec
Hi
Checking some code related to client behavior api, I notice that it is not
very clear the conditions to render jsf.js script on a page.
Right now we have an open issue (see MYFACES-2687) but we need to discuss
this one first before solve it.
In few words, myfaces is doing the following:
1. I
10 matches
Mail list logo