The following is from a JSF resource: "If the user triggered the request by clicking a button or a link, the corresponding UICommand component discovers this in the Apply Request Values phase when it finds a request parameter with a name that matches its ID. It creates an ActionEvent to represent the event, but doesn't notify the listeners immediately, because the rest of the components in the tree may not have picked up their values yet. Instead it adds it to a queue by calling its queueEvent() method."
What confuses me is how if you have a page A that contains a command link to a page B, when page B's component tree is created, how will that command link ever find a request parameter "with a name that matches its ID"...doesn't the command link exist only in page A, not in page B? (Is the paragraph above describing only what happens when page A forwards to itself, page A?) This is actually part of a bigger issue I'm having trouble with: anytime you have a page that is the result of a request, wouldn't the component tree in that second page have different components from that in the page that initiates the request, making all of these issues (conversion, validation, and the other JSF phases) not possible to do - because the components have never existed prior to this page. It seems all these things only happen when a page forwards to itself (page A to page A), but what about page A to page B types of scenarios? But clearly that's not how it works, and I know I'm completely thinking about this the wrong way...perhaps somebody here could clear things up. Thanks. -- View this message in context: http://www.nabble.com/Basic-UICommand-ActionEvent-question-tf2792395.html#a7790584 Sent from the MyFaces - Users mailing list archive at Nabble.com.
