[ https://jira.jboss.org/jira/browse/JBSEAM-3213?page=com.atlassian.jira.pl... ] Nicklas Karlsson updated JBSEAM-3213: ------------------------------------- Fix Version/s: 2.1.1.CR1 Affects Version/s: 2.1.0.CR1 -- 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-3213?page=com.atlassian.jira.pl... ] Pete Muir updated JBSEAM-3213: ------------------------------ Fix Version/s: 2.1.2.CR1 (was: 2.1.1.CR2) -- 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://issues.jboss.org/browse/JBSEAM-3213?page=com.atlassian.jira.plugi... ] bart king commented on JBSEAM-3213: ----------------------------------- I would appreciate if this feature gets some attention from the Seam Excel Application developers ASAP. Most of the rich:datatables in our app are not of simple variety - which includes h:outputText values surrounded by <s:link>, <a> tags eventually looking out for another alternative to export the table in excel format. Although, this API is the easiest I have ever used, but some limitations like above could go against its popularity. Hope my shout out gets immediate attention. Thanks! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira