[ http://jira.jboss.com/jira/browse/JBSEAM-754?page=comments#action_12352096 ] Peter Muir commented on JBSEAM-754: ----------------------------------- * There is a problem outjecting a Trinidad TreeModel (none of the children appear). AFAICS this is a Trinidad bug, I'm going to pursue it over there * EL enhancements don't work - is this worth fixing in light of http://jira.jboss.org/jira/browse/JBSEAM-697? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-754?page=comments#action_12352098 ] Peter Muir commented on JBSEAM-754: ----------------------------------- There are probably some good ways of tying certain Trinidad components into Seam better: 1) @TreeModel - Trinidad do almost all the work here by having a ChildPropertyTreeModel(object, "childProperty") - @TreeModel could just wrap this up in an annotation. Also a @TreeModelSelection 2) Data paging: Seam has it good from the efficiency POV, Trinidad (et al) has it good from the JSF/ui POV. I see two ways of doing this: either add in some sort of PagingController interface which then could be (i) impld by them as now (ii) impld by Seam using EntityQuery as a backend or Use the existing-in-Trinidad RangeChangeEvent to alter query parameters 3) Perhaps an @MenuModel annotation (Trinidad have been extensively refactoring menus, I'm not sure how stable this is AND I'm not convinced of the value of this) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-754?page=comments#action_12356808 ] Joshua Jackson commented on JBSEAM-754: --------------------------------------- Will Trinidad work with JSF RI 1.2 since in future Seam will embrace JSF RI 1.2 What is the advantage of Trinidad compares to ajax4jsf? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-754?page=all ] Pete Muir closed JBSEAM-754. ---------------------------- Resolution: Rejected Actually, this is a silly bug so I'm closing it -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira