s:button VS h:commandButton / s:link VS h:commandLink

[ngeadah]

What is the difference between s:button and h:commandButton for simple things like calling an action?

I have Seam 1.1CR1, JSF, Facelets all configured fine (at least I think), and the following works great:

<h:commandButton value="Login" action="#{loginClient.login}"/>

While the following calls out to the action but does not seem to perform any injection.

<s:button value="Login" action="#{loginClient.login}"/>

Same problem with s:link VS h:commandLink (which uses JS to submit - yuck!). I would much rather use the Seam UI components but they simply are not working right for me because the injection is not occuring. Anyone seen this problem before?

[gavin.king]

Injection (ie. @In) works just fine. I think it is the form submission that does not happen. Which is the whole point....

If you want the form to be submitted, use h:commandButton. If you want a bookmarkable URl, use s:button.

[ngeadah]

If s:xxx does not submit the form (which in turn prevents the injection from happening), does anyone have a recommendation on how to submit a form using a regular link (other than using h:commandLink, which works but uses JavaScript)?

[mzeijen]

If you want to submit a form using a link then you must use javascript. There is no other way... Only a form submit-button can submit a form without javascript.