Anyone?
Tomasz Pasierb napisał(a):
Hey Guys,
have anyone of you used Tomahawk's panelNavigation2 component with
clay successfully? I put commandNavigation2 tags inside that render
links. This is all static defined in a html component.
I'm actually having some problems with this.
I have the component defined in one of the tiles. It appears the
component's state is not retrieved correctly after the action is
invoked on the menu and a new page is loaded (defined as a clay
component). The menu appears with all the menu options closed while it
should render with all the options containing the one that was clicked
opened. Additionally marking options (commandNavigation2) as disabled
doesn't seem to have any effect.
I have tried this component without clay - basically I copied the jsp
fragment to a "clean" myfaces application - and it works as expected.
When the new view is rendered the last option clicked is highlighted
as it should. Disabled options are rendered as text not links so this
works fine here too.
The message I get from myfaces when invoking an action that loads a
new view (when using clay) goes like this:
INFO-WARNING: Component _id0 just got an automatic id, because there
was no id assigned yet. If this component was created dynamically
(i.e. not by a JSP tag) you should assign it an explicit static id
or assign it the id you get from the createUniqueId from the current
UIViewRoot component right after creation!
I guess clay renders or assigns this component a new id when a new
view is invoked/rendered and that's why the state isn't retrieved
correctly. Assigning ids statically (in jsp) to panelNavigation2 and
all the commandNavigation2 components/elements doesn't help.
Is there any solution to this or is it a bug?
Regards,
Tom Pasierb
----------------------------------------------------------------------
Jestes kierowca? To poczytaj! >>> http://link.interia.pl/f199e
