This content has been marked as final.
Show 3 replies
-
1. Re: Richfaces + Seam + JPDL problem
sebasfiorent Oct 17, 2007 2:40 PM (in response to sebasfiorent)Another thing that doesn't work is the rich:include componente. If you use faces-config (uggg) navigation rules, it works as expected, but if you use jpdl navigation simply it doesn't work.
Regards
Sebastian -
2. Re: Richfaces + Seam + JPDL problem
alexsmirnov Oct 17, 2007 3:06 PM (in response to sebasfiorent)First - jpdl navigation in Seam, in case of the no transision to other state, really perform JSF navigation to same viewId. ajax4jsf framework detect it as real navigation, and switch rendering to the non-ajax. This is a difference with JSF navigation case, where is "null" action mean "continue to processing current page".
Second - really, this is difference in the navigation processing in the Seam and a4j:include. This is a known issue, don't solved yet. -
3. Re: Richfaces + Seam + JPDL problem
sebasfiorent Oct 17, 2007 3:30 PM (in response to sebasfiorent)"alexsmirnov" wrote:
First - jpdl navigation in Seam, in case of the no transision to other state, really perform JSF navigation to same viewId. ajax4jsf framework detect it as real navigation, and switch rendering to the non-ajax. This is a difference with JSF navigation case, where is "null" action mean "continue to processing current page".
Second - really, this is difference in the navigation processing in the Seam and a4j:include. This is a known issue, don't solved yet.
Thanks. I'll look into seam forums to see how to issue a "null" transition within jpdl pageflow.