Hmm. I can determine the selectionIndex for my own. But as Seam is a framework and those annotations are public they should work, even if I use both. Additionally I think that the @DataModelSelectionIndex delivers the index more efficiently than my workaround, which iterates the whole list searching the selected element. OK, I could go the other way letting Seam inject the index and then ask the list for the element at this position.
In my opinion they should work together or this behavious should be documented at a place where everybody recognizes it to prevent posts like mine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951917#3951917 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951917 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
