-
15. Re: xhtml code assist performance
laixer Jun 24, 2010 7:39 PM (in response to vrubezhny)Thank you Victor. I didn't know that 3.1.1 has been releaesed. I'm used to seeing updates from in.relation.to RSS.
I forgot that you guys moved your posts to a different location... I'll give it a try as soon as I can.
-
16. Re: xhtml code assist performance
laixer Jun 24, 2010 8:07 PM (in response to vrubezhny)I just gave it a quick test and it works great! Code assist performance is definitely better now.
I noticed another problem (which may have been present in earlier version too).
If I close and open Eclipse, open a file and try to perform Code Assist, I don't see any Seam components in the list.
I have to right click on the project and click refresh for them to show up.
-
17. Re: xhtml code assist performance
dgolovin Jun 24, 2010 8:12 PM (in response to laixer)Does Seam Components View contain any components after eclipse restarted but before project refresh called?
-
18. Re: xhtml code assist performance
laixer Jun 24, 2010 8:16 PM (in response to dgolovin)I can't tell because as soon as I expand "+ ProjectName" in the "Seam Components" window, Code Assist starts working.
My guess they are not there until I expand the Project.
-
19. Re: xhtml code assist performance
vrubezhny Jun 24, 2010 8:30 PM (in response to laixer)It is required that projects to be built to have Seam components in CA. But it seems that the build was not performed for your projects. Refresh action may invoke the builders.
So, is Project->Build Automatically Option turned ON for your projects? And if so, have the builder jobs finished their work before you call the CA?
-
20. Re: xhtml code assist performance
laixer Jun 24, 2010 8:47 PM (in response to vrubezhny)Yes, build automatically is always on. I don't think the builders get run when I first open Eclipse unless I use 'Refresh' on the project.
Not sure if it helps, but I have attached the builders configuration for this project.
It's not that big of a deal for me since getting it to work is very easy, but it might be confusing for new users if they hit the same problem...
-
builders.png 3.3 KB
-
-
21. Re: xhtml code assist performance
vrubezhny Jun 24, 2010 9:23 PM (in response to laixer)It's all OK with the builders for the first look.
Try to clean configuration. This should help.
-
22. Re: xhtml code assist performance
akazakov Jun 25, 2010 2:42 AM (in response to laixer)Vadim, It seems to be a bug. Could you please report it to JIRA? Thanks.
-
23. Re: xhtml code assist performance
laixer Jun 25, 2010 10:05 AM (in response to akazakov)I've opened an issue here https://jira.jboss.org/browse/JBIDE-6541
I did some additional testing so the issue has a bit more information in it.
-
24. Re: xhtml code assist performance
akazakov Jun 25, 2010 10:23 AM (in response to laixer)Vadim, thank you.
-
25. Re: xhtml code assist performance
vrubezhny Jun 25, 2010 11:21 AM (in response to laixer)Vadim,
You wrote in the https://jira.jboss.org/browse/JBIDE-6541 issue that you tried it with "a clean workspace", but I asked you to clean the configuration (not the workspace itself)...
Did you tried to start eclipse with -clean option or to set osgi.clean option to "true"?
The trick is that something is cached in the workspace configuration for the Java Model, and since no Java code was changed the builder was not started at the first start of the new eclipse version. But eclipse (JBoss Tools and Seam Components model structure) was replaced with a new one, so actually the model needs to be re-build.
So, -clean option should help is this case. Did you tried it?
-
26. Re: xhtml code assist performance
laixer Jun 25, 2010 11:31 AM (in response to vrubezhny)Sorry, 'clean configuration' was a little too ambigious for me...
I started eclipse with -clean, tried to perform EL completion and I saw Seam components in the list.
I closed Eclipse and started it normally and tried to perform EL completition and once again I didn't have any Seam components.
-
27. Re: xhtml code assist performance
vrubezhny Jun 25, 2010 11:46 AM (in response to laixer)It's definitely what I wanted to see.
IMHO, it's a bug.
Thank you, Vadim