You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Renzo Tomaselli <re...@tecnotp.it> on 2008/02/12 21:33:40 UTC
[Trinidad] using tr:tree as a tr:table detail
Hi, I tried to use a tr:tree as the detail component of a tr:table - as
well as PPR of the involved row according to tree node selection.
It almost works - at least on FF. On IE - upon clicking any node - I get
a js error such as:
document.forms[...][...] is null or not an object
After some investigations, I noticed that this statement occurs in a js
chunk rendered after tr:tree.
This occurs for a normal tree, but this code is totally missing for the
above tree used as a detail.
Indeed the former is rendered by
org.apache.myfaces.trinidadinternal.ui.laf.base.desktop.TreeRenderer,
while the latter is rendered by
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.TreeRenderer.
Don't ask me why there are two tree renderers.
Anyway even the latter is rendered with onclick attributes (on nodes)
invoking _adfTreeSelector.select() on a selector object never rendered
in the PPR response.
Then (I guess) the js crash after clicking any node.
Any suggestion to have the embedded tree behaving as a normal tree is
welcome.
-- Renzo
Re: [Trinidad] using tr:tree as a tr:table detail
Posted by Matthias Wessendorf <ma...@apache.org>.
Hi Gerhard,
I am fine when you commit your suggested fix/change.
Thanks for paying attention ;-)
-Matthias
On Feb 13, 2008 1:05 AM, Gerhard Petracek <ge...@gmail.com> wrote:
> hello,
>
> i already know - it's the same javascript implementation (within both
> renderers).
> i suggest to change/remove both javascript implementations (@change/remove -
> see [1])
> + a lot of testing.
>
> fact:
> at this point in time there is no object at
> document.forms[this.treeState.getFormName()][this._selectParam]
> -> the "intention" is to deposit a value at a currently blank position.
>
> i found the following statement concerning ie:
> document.forms[...][...].value is a valid statement to access existing
> objects.
> however, ie doesn't support such a statement to deposit a value at a blank
> position.
>
> regards,
> gerhard
>
> [1] http://www.nabble.com/TRINIDAD-935-to15321924.html#a15321924
>
>
>
> 2008/2/12, Renzo Tomaselli <re...@tecnotp.it>:
>
> >
> > Matthias, yes - I believe it's the same issue.
> > But in my opinion the primary source of troubles is the usage of a
> different renderer (don't know why), which doesn't render the needed js code
> after the tree. Ordinary trees work fine, so I guess the construct
> document.forms[][] is ok.
> >
> > -- Renzo
> >
> >
> >
> > Matthias Wessendorf wrote:
> > is this related to this:
> >
> > https://issues.apache.org/jira/browse/TRINIDAD-935
> >
> >
> > On Feb 12, 2008 9:33 PM, Renzo Tomaselli <re...@tecnotp.it>
> wrote:
> >
> >
> > Hi, I tried to use a tr:tree as the detail component of a tr:table - as
> > well as PPR of the involved row according to tree node selection.
> > It almost works - at least on FF. On IE - upon clicking any node - I get
> >
> > a js error such as:
> >
> > document.forms[...][...] is null or not an object
> >
> > After some investigations, I noticed that this statement occurs in a js
> > chunk rendered after tr:tree.
> > This occurs for a normal tree, but this code is totally missing for the
> >
> > above tree used as a detail.
> > Indeed the former is rendered by
> > org.apache.myfaces.trinidadinternal.ui.laf.base.desktop.TreeRenderer,
> > while the latter is rendered by
> > org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.TreeRenderer.
> >
> > Don't ask me why there are two tree renderers.
> > Anyway even the latter is rendered with onclick attributes (on nodes)
> > invoking _adfTreeSelector.select() on a selector object never rendered
> > in the PPR response.
> >
> > Then (I guess) the js crash after clicking any node.
> > Any suggestion to have the embedded tree behaving as a normal tree is
> > welcome.
> >
> > -- Renzo
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
Re: [Trinidad] using tr:tree as a tr:table detail
Posted by Gerhard Petracek <ge...@gmail.com>.
hello,
i already know - it's the same javascript implementation (within both
renderers).
i suggest to change/remove both javascript implementations (@change/remove -
see [1])
+ a lot of testing.
fact:
at this point in time there is no object at
document.forms[this.treeState.getFormName()][this._selectParam]
-> the "intention" is to deposit a value at a currently blank position.
i found the following statement concerning ie:
document.forms[...][...].value is a valid statement to access existing
objects.
however, ie doesn't support such a statement to deposit a value at a blank
position.
regards,
gerhard
[1] http://www.nabble.com/TRINIDAD-935-to15321924.html#a15321924
2008/2/12, Renzo Tomaselli <re...@tecnotp.it>:
>
> Matthias, yes - I believe it's the same issue.
> But in my opinion the primary source of troubles is the usage of a
> different renderer (don't know why), which doesn't render the needed js code
> after the tree. Ordinary trees work fine, so I guess the construct
> document.forms[][] is ok.
>
> -- Renzo
>
>
> Matthias Wessendorf wrote:
>
> is this related to this:
>
> https://issues.apache.org/jira/browse/TRINIDAD-935
>
> On Feb 12, 2008 9:33 PM, Renzo Tomaselli <re...@tecnotp.it> <re...@tecnotp.it> wrote:
>
> Hi, I tried to use a tr:tree as the detail component of a tr:table - as
> well as PPR of the involved row according to tree node selection.
> It almost works - at least on FF. On IE - upon clicking any node - I get
> a js error such as:
>
> document.forms[...][...] is null or not an object
>
> After some investigations, I noticed that this statement occurs in a js
> chunk rendered after tr:tree.
> This occurs for a normal tree, but this code is totally missing for the
> above tree used as a detail.
> Indeed the former is rendered by
> org.apache.myfaces.trinidadinternal.ui.laf.base.desktop.TreeRenderer,
> while the latter is rendered by
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.TreeRenderer.
> Don't ask me why there are two tree renderers.
> Anyway even the latter is rendered with onclick attributes (on nodes)
> invoking _adfTreeSelector.select() on a selector object never rendered
> in the PPR response.
> Then (I guess) the js crash after clicking any node.
> Any suggestion to have the embedded tree behaving as a normal tree is
> welcome.
>
> -- Renzo
>
>
>
>
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: [Trinidad] using tr:tree as a tr:table detail
Posted by Matthias Wessendorf <ma...@apache.org>.
is this related to this:
https://issues.apache.org/jira/browse/TRINIDAD-935
On Feb 12, 2008 9:33 PM, Renzo Tomaselli <re...@tecnotp.it> wrote:
> Hi, I tried to use a tr:tree as the detail component of a tr:table - as
> well as PPR of the involved row according to tree node selection.
> It almost works - at least on FF. On IE - upon clicking any node - I get
> a js error such as:
>
> document.forms[...][...] is null or not an object
>
> After some investigations, I noticed that this statement occurs in a js
> chunk rendered after tr:tree.
> This occurs for a normal tree, but this code is totally missing for the
> above tree used as a detail.
> Indeed the former is rendered by
> org.apache.myfaces.trinidadinternal.ui.laf.base.desktop.TreeRenderer,
> while the latter is rendered by
> org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.TreeRenderer.
> Don't ask me why there are two tree renderers.
> Anyway even the latter is rendered with onclick attributes (on nodes)
> invoking _adfTreeSelector.select() on a selector object never rendered
> in the PPR response.
> Then (I guess) the js crash after clicking any node.
> Any suggestion to have the embedded tree behaving as a normal tree is
> welcome.
>
> -- Renzo
>
>
>
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org