[ http://jira.jboss.com/jira/browse/JBIDE-1916?page=comments#action_12403479 ] Victor Rubezhny commented on JBIDE-1916: ---------------------------------------- Max Andersen [18/Mar/08 02:28 AM] About performance: "I just used the project variables (which are already collected)" ....these variables are (or at least should be done in the background) thus it might not be available since if it blocks the ui for large projects it will be a big showstopper. The initial quickfix popup should not require large calculations and if it requires the seam builder to have completed it will block the creation of that popup - and that is bad plugin behavior. About types then I can't recognize that java search search for all calsses with resultList. It looks for references to the resultList variable/method on the same type as testEntityList is. So to be explicit here is what I think should happen in case of #{testEntity.resultList.size} declaration search (note: not all of these needs to be implemented, we should do them in steps/ that makes sense) testEntity -> declarations with the same name (e.g. testEntity) and if we actually know what specific "testEntity" it is pointing to (e.g. it is a local variable used in a loop) then it should only list the specific declarations (e.g. where the variable is declared in the start of the loop) testEntity.resultList -> search from declarations of testEntity and find its type (might be multiple types) and then scan those types for possible things that resultList can be declared as (e.g. method or resultList or field resultList) testEntity.resultList.size() -> find the type(s) of testEntity, find the things that can be resultList on testEntity (method, field, key in map) and then scan for size() method on those possible types. Similar rules can be defined for references. What I suggest you/we do is to define a list of possible combiations of xhtml, components.xml and java that illustrates all the possible way of having multiple types and references and express that in unittests that we can use to verify 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/JBIDE-1916?page=comments#action_12403480 ] Victor Rubezhny commented on JBIDE-1916: ---------------------------------------- Мах, i've copied your comment from JBIDE-1912 here, because it is strongly related to this issue. Also, this issue cannot be done for 2.1.0.beta1. Also, this issue not a bug, but feature request. Both, type of issue and fix for fields are to be changed. -- 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/JBIDE-1916?page=all ] Max Andersen updated JBIDE-1916: -------------------------------- Issue Type: Feature Request (was: Bug) Fix Version/s: 2.1 (was: 2.1.0.beta1) I updated the type and fix version...ok by you now ? not sure what you wanted and why you didn't update 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

[ http://jira.jboss.com/jira/browse/JBIDE-1916?page=all ] Victor Rubezhny resolved JBIDE-1916. ------------------------------------ Resolution: Done Issue is fixed -- 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/JBIDE-1916?page=all ] Max Andersen updated JBIDE-1916: -------------------------------- Fix Version/s: 2.1.0.beta1 (was: 2.1) batch update of issues with 2.1 fix instead of the correct 2.1.b1 -- 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