[ https://jira.jboss.org/jira/browse/JBSEAM-3428?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-3428: ----------------------------------- A workaround for this is to leverage the JBoss EL. #{eventContext.set('variableName', componentName.anyMethod())} Granted, it is not as pretty as: <s:let var="variableName" value="#{componentName.anyMethod()}" scope="event"/> I do really like the idea of creating the tag. People with no sense decided somewhere along the line that variables are a bad thing that that we should do everything with our feet strapped to the floor and our hands tied around our backs. This tag would be extremely trivial to write. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3428?page=com.atlassian.jira.pl... ] Pete Muir commented on JBSEAM-3428: ----------------------------------- I'm not sure this is semantically correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3428?page=com.atlassian.jira.pl... ] Pete Muir commented on JBSEAM-3428: ----------------------------------- It's an implicit alteration of the object's scope. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3428?page=com.atlassian.jira.pl... ] Jakub Janczak commented on JBSEAM-3428: --------------------------------------- use <c:set .. /> JSTL tag -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3428?page=com.atlassian.jira.pl... ] Jakub Janczak commented on JBSEAM-3428: --------------------------------------- @Ronald - good to know - it's a great idea IMO but still the let defined variables can be used only within the render and decode phases. The c:set on the other hand gives you more flexibility because you can use the var all the time (conditional component tree building and so on). No matter what - both are usable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira