-
1. Re: s:link EL bug, seam-2.0.0.BETA1
thejavafreak Aug 8, 2007 4:45 AM (in response to msznapka)The code that you posted uses h:commandLink
-
2. Re: s:link EL bug, seam-2.0.0.BETA1
thejavafreak Aug 8, 2007 10:51 PM (in response to msznapka)Show us how you use s:link in your application because the code that you posted uses h:commandLink not s:link
-
3. Re: s:link EL bug, seam-2.0.0.BETA1
msznapka Aug 9, 2007 2:55 AM (in response to msznapka)I think it is clear from original post: which works fine until i change h:commandLink to s:link
<ui:repeat value="#{someArray}" var="item"> <s:link action="#{util.action(item.id)}" .../> </ui:repeat>
or this example shows the problem best:<ui:repeat value="#{someArray}" var="item"> <s:link action="#{util.action(item.id)}" .../> <h:commandLink action="#{util.action(item.id)}" .../> </ui:repeat>
h:commandLink works fine, s:link not, like i described before -
4. Re: s:link EL bug, seam-2.0.0.BETA1
dmitriy.lapko Aug 9, 2007 7:00 AM (in response to msznapka)Did you search this forum for similar questions?
May be you can find an answer here: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=113909
You can't construct action value dynamically in s:link tag. -
5. Re: s:link EL bug, seam-2.0.0.BETA1
msznapka Aug 9, 2007 8:02 AM (in response to msznapka)Thx for link, so the results are:
- try @DataModel
- try f:param
But i still dont understand why such case is possible with h:commandLink and is not with s:link, which is strange because s:link should be something more sophisticated than h:commandLink.
That is why i am thinking that there is bug in s:link - simply find solution in h:commandLink source code and put such behaviour in s:link -
6. Re: s:link EL bug, seam-2.0.0.BETA1
pmuir Aug 9, 2007 8:21 AM (in response to msznapka)No, s:link is something *different* to h:commandLink, it's *not* a direct replacement.
-
7. Re: s:link EL bug, seam-2.0.0.BETA1
msznapka Aug 9, 2007 8:56 AM (in response to msznapka)But it should be direct replacement. I am forced to use s:link, because of right conversation management and i am not lucky if i have reduced functionality with s:link.
Anyway, thanks for answers, i will try different ways in my problem. -
8. Re: s:link EL bug, seam-2.0.0.BETA1
pmuir Aug 9, 2007 9:27 AM (in response to msznapka)No it shouldn't be a direct replacement (that would be highly pointless). It is for a different purpose. You should use s:link for navigation and a commandLink for working with forms.
-
9. Re: s:link EL bug, seam-2.0.0.BETA1
msznapka Aug 9, 2007 12:08 PM (in response to msznapka)Ok, i should learn better ;)
Thanks!