- This topic has 20 replies, 4 voices, and was last updated 15 years, 12 months ago by
.
-
Posts
-
Hi,
I’m tensting this new release, all OK, the only problem I found is the autocopletition with JSF files, too slow compared with previous version 6.6.I noted the propousals are all the bean’s methods not only getter & setter, beautiful but too slow for me.
Best regards,
EmanueleEmanuele,
Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me. I’ll ask the dev team to look into this issue.Do you face the same performance issue with the Auto Complete in a new workspace as well?
the workspace is new created for myeclipse 7, this is the configuration:
*** Date:
mercoledì 21 gennaio 2009 16.13.25 CET** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.5.0_07*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.0
Build id: 7.0-20081201*** Eclipse details:
Eclipse PlatformVersion: 3.4.1
Build id: M20080911-1700Eclipse Platform
Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
Build id: M20080911-1700Eclipse Java Development Tools
Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
Build id: M20080709-0800Eclipse Graphical Editing Framework GEF
Version: 3.4.1.v20080806-67718083A56B4H2A3213573
Build id: 200809101400Eclipse RCP
Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: M20080703-0800Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
D:\MyEclipse 7.0\eclipse\plugins\org.eclipse.platform_3.3.101.v200809111700\splash.bmp
-launcher
D:\MyEclipse 7.0\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
D:\MyEclipse 7.0\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
D:\MyEclipse 7.0\eclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-framework
plugins\org.eclipse.osgi_3.4.2.R34x_v20080826-1230.jar
-vm
C:\Programmi\Java\jre1.5.0_07\bin\client\jvm.dllBest regards,
Emanuele.I don’t know if I can help you to find the problem, but it seems that the beans are analized each time start the autocompletition, no cache are used.
Thanks,
Emanuele.Emanuele,
Can you give me some information about the number of projects in your workspace and the type (technologies) of projects you are working with?Now I have 7 projects in my workspace, but at least 2 open. Some projects are simply java project with class and properties files.
The slow project are web application with Spring,JPA,JSF, 19 packages,80 classes, 13277 lines of code. This project referer other java projects.
Can I disable the EL autocompletion with all methods and properties and use only properties as myeclipse 6.6 ?
It’s better if i use java 6?Best regards,
Emanuele.Update: We have been working on this issue it seems like this is related to JSF projects (most also having JavaScript Dev Tools enabled on them as well). We are working on fixing this and we will get back to you with another update asap.
the upcoming 7.1 version will solve the the bug?
Im afraid this wont make it to the 7.1 release. Will will try and get it in the 7.2 release. Sorry about that.
I got the same problem here: big project and slow performance. Sometimes MyEclipses crashes also. I know people are asking for new features and marketing loves new features. But I’d prefer that new features are DISABLED by default. Or at least it should be possible to turn it off manually.
It is really hard to edit JSF files.
