-
1. Re: JSFClientSession.submit not working with h:commandButton
ssilvert Jun 12, 2008 5:46 PM (in response to jinpsu)I don't think its luck! :-)
If JSF navigated correctly to a new page then surely it performed #{bean.action} and returned the proper String. How do you know that the action was not performed?
Stan -
2. Re: JSFClientSession.submit not working with h:commandButton
jinpsu Jun 13, 2008 7:20 AM (in response to jinpsu)Well I know it's not really luck, but it is bizarre. I have no idea where it is getting the navigation rule. When I use RichFacesClient.ajaxSubmit("myButton"), all goes well and I see all my debug in the action routine. When I change just that one line to JSFClientSession.submit("myButton"), I no longer see my action() debug but JSFServerSession.getCurrentViewID() tells me I've navigated to the correct page. I even commented out the entire action() logic and returned null with the same result.
-
3. Re: JSFClientSession.submit not working with h:commandButton
ssilvert Jun 13, 2008 8:35 AM (in response to jinpsu)It could be that RichFaces is doing something weird. Note that we will soon be switching to HtmlUnit for handling this and it works in a different way. You can read about that in the first post of this forum.
Stan