[ http://jira.jboss.com/jira/browse/JBIDE-1912?page=all ] Victor Rubezhny resolved JBIDE-1912. ------------------------------------ Resolution: Done -- 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-1912?page=comments#action_12403152 ] Victor Rubezhny commented on JBIDE-1912: ---------------------------------------- Max, You wrote: ...except know it seems that it actually does the search to determine if the query would result in something...won't that cost alot of performance/waittime on larger projects ? I don't think that it would cost much more for the larger projects... I just used the project variables (which are already collected) to decide if the text under the cursor starts with some variable name. If it is true the search will be continued for the variable declaration/references. Otherwise search will not be performed. You wrote: e.g. it shows up on identity.getUsername(); but not on userName.length(); ....how can it know that userName will not return a result without doing the actual search first ? In jbide-509 we decided to search for the variable declarations/references, so for now it doesn't matters of the end of EL. The only starting part of EL (variable name) will be search for. jbide-1912 is to extend this to search for methods/properties of the Seam variable... I'm confused a little bit in what to display in this case, because it is to be searched thru the EL before I can display the real query is to be searched for... It was simple to calculate the display string while we're searching for the variables. Now it will be more difficult, but still realizable. Here is a question on what shall I search. For example: #{testEntityList.resultList.size} if the cursor is placed over the testEntityList I'll search for declaration of/references to testEntityList variable (this is how it works now), but... if the cursor is placed over the resultList I'll search for resultList property or method declarations/references for any component in the project. (java search does in the same way). It's not realized now. But what shall I search if the cursor is placed over the size property or method? Shall I still search for size property or method declarations/references for any component in the project? Or shall I search for resultList property/method? -- 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-1912?page=all ] Victor Rubezhny updated JBIDE-1912: ----------------------------------- Attachment: javasearch-screenshot.jpg -- 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-1912?page=comments#action_12403485 ] Victor Rubezhny commented on JBIDE-1912: ---------------------------------------- The quick-fix is showing the items to be search (as they declared in JBIDE-509), so the issue linking is to be moved to JBIDE-1916 from JBIDE-1860. Or an additional issue is to be created. I've copied the comment on the performance and the items to be search to JBIDE-1916. -- 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-1912?page=all ] Max Andersen updated JBIDE-1912: -------------------------------- Attachment: 2008-03-19_0014.png My search result when I allow potential matches. Can\t reproduce what you see. could you explain how you get 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-1912?page=comments#action_12403603 ] Max Andersen commented on JBIDE-1912: ------------------------------------- With potential matches for Find references I get 4 extra matches as shown in my screenshot. With Find declarations then yes you get alot of hints and the logic I see here is that you are already on the declaration so it is searching for other possible declarations. This is two different kind of searches and I can't see how it is different in context of seam/jsf el-references. Wether it is an abstract class that cannot be instantieted I cannot see how that influences the search since this also the case for interfaces...it is just a method search. -- 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-1912?page=all ] Max Andersen updated JBIDE-1912: -------------------------------- 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