"[EMAIL PROTECTED]" wrote : No. They are not semantically identical. @RequestParameter is simply for injecting a request parameter, page parameters have a deeper effect on your app (parameter propagation, setting values on your model, application of converters).
I understand with page definition you can do more than a simple @RequestParameter injection. Let's forget about propagating parameters values for a while. But when it comes to just passing GET parameters(to the backing bean component) shouldn't they be having the same behaviour? Here is what I found out. When you have the parameter defined in pages.xml, here is the flow of the backing bean component: * Seam calls @Create method first * It then calls setters on the parameters to initialize the values With @RequestParameter, the behaviour is * Seam injects parameter values first (No need to have setters) * It then calls the @Create method Is this the intended behaviour? May be there was a reason to design this way which I don't get it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073234#4073234 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073234 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
