[atomz4peace]

I was looking at purchasing myeclipse but ran into a problem with JSF editing. We set up a jsf page and link it to the bean with faces-config. Everything works fine until we try to do code-complete on the bean methods (e.g. value=”#{ hit ctrl-space)

It finds the bean very quickly, but when we hit ctrl-space after the . after we populate the bean, (e.g. #{mybean.<-ctrl-space here ) myeclipse takes up 100% cpu for at least 10-15 seconds before showing the results. It always happens. It’s as if it won’t cache the results or something.

Does anyone have a clue of what to check? The beans have many variables but not really that big.

Thoughts?

Thanks!

[support-shalini]

atomz4peace,
What is the version of MyEclipse that you are using?
ME7.5 has included a lot of performance enhancements. You can optionally switch off the capabilities you are not using under
Windows > Prefs > General > Capabilities > Advanced

[atomz4peace]

I’m using the latest. I just downloaded the trial a few days ago to test it out. Maybe it’s a wtp instead of myclipse bug. But would you have any idea how to tell or what might take so long to compute the auto-complete? Is there a debug to see what it’s doing when it’s pegged the cpu?

Thanks!

[Loyal Water]

atomz4peace,
What version of MyEclipse are you working with? Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

We have enhanced the performance of the IDE in our latest release (MyEclipse 7.5) and you should not be facing this issue incase you are working with MyEclipse 7.5.

[claudio]

hi to all.
I’m facing the same problem, whenever I ask to autocomplete on JSF *.jspx It hangs and i have to wait a while (30-40 sec) to get it reponsive again. I lauched it in console mode but nothing appens during the hang.
here is my configuration:
*** Date:
venerdì 24 luglio 2009 8.22.26 CEST

** System properties:
OS=WindowsVista
OS version=6.0.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.5
Build id: 7.5-20090609

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 7.5
Build id: 7.5-20090609

Eclipse Plug-in Development Environment

Version: 3.4.2.R342_v20090122-7T7U1E9imVKz-A8Vz-p_jRS
Build id: M20080703-0800

Eclipse Platform

Version: 3.4.2.R342_v20090122-9I96EiWElHi8lheoJKJIvhM3JfVsYbRrgVIWL
Build id: M20090211-1700

Eclipse Graphical Editing Framework GEF

Version: 3.4.2.v20090218-1145-67728084A56B4I233613552
Build id: 200809101400

Eclipse RCP

Version: 3.4.200.R342_v20090122-989JESTEbig-SVaL8UJHcYBr4A63
Build id: M20090211-1700

Eclipse Java Development Tools

Version: 3.4.2.r342_v20081217-7o7tEAoEEDWEm5HTrKn-svO4BbDI
Build id: M20090211-1700

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\WinApp\java\MyEclipse 7.5\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\WinApp\java\MyEclipse 7.5\Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\WinApp\java\MyEclipse 7.5\Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
-clean
-configuration
configuration
-clean
-console
-consoleLog
-debug
-vm
C:\WinApp\java\MyEclipse 7.5\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dll

[Loyal Water]

cgennari,
What editor are you working with? Can you paste a sample JSPX file here for me and let me know what bit of code you are trying to autocomplete and facing this problem.

[claudio]

Hello, I’m just back from holidays 😉
I’m using “Myeclypse Visual JSF Designer” editor with ICEFaces components 1.8.1.
When I digit “#{bean^sp } it gives me correct list of my registered bean.
No matter what complex JSF page I edit, I cannot dig into bean properties.
IT hangs for more than one minutes.
If you want I can send you a simple project (hello world) with this behavior
Ciao

[Loyal Water]

If you want I can send you a simple project (hello world) with this behavior

That would be very helpful. You can send us the project at support@genuitec.com ATTN Nipun (with a link to this post).

[ernestz]

I am also encountering the problem where ME hangs when attempting to autocomplete JSF on a .jspx page. In case, the page(s) vary in size, but the backing beans can be rather large. In an example I am currently watching, I started entering a expression as … value=”#{backingBean.

As soon as I entered “.”, ME has stalled for several minutes now, pegging my CPU at 90% all the while.

Is there any way to disable auto complete altogether?

[ernestz]

@ernestz wrote:

Is there any way to disable auto complete altogether?

Or is there a magical keystroke/mouse wave (anything) that I can do to interrupt whatever code is being executed so I can cleanly recover? Right now, if I have to kill ME, I’ve lost some work, which can be recreated, but still … ME shouldn’t hang for several minutes trying to autocomplete the JSTL expression.

[guyr]

I’m having the opposite problem: my JSF pages don’t offer auto-complete suggestions. How do I enable this? Pulse just upgraded me to ME 8.5. We use a .jsf extension on our files if that makes any difference. ME is using the JSF editor. Thanks.

[support-shalini]

Guy,
I could not replicate this at my end. Can you give some more information?
1. Can you copy paste your installation details from MyEclilpse > Installation Summary > Installation Details?
2. What are the errors logged in the log file located at workspace dir > .metadata > .log? Please clear the log file, save it and execute the auto complete action to check for relevant errors.
Also, can you switch to a new workspace and check if the issue persists?

[atomz4peace]

I have a few more details. If I move the project over to a new workspace, it works for a while. I actually can re-create these steps by copying in a save .metadata directory.

So if I copy a saved .metadata to the workspace, it will initially auto-complete fine. In the .log file, I see several messages about files out of sync with file system on web.xml and faces-config.xml. But everything works fine at this point. Note that the project is already built, complied, auto-compile and all that.

If I hit F5 or refresh on the project, it will refresh and re-build. After the refresh, the autocomplete goes back to the 100% cpu for about 10-20 seconds. The error message in the log about out of sync no longer gets logged when I restart eclipse.

So it looks like something on the refresh does me in. Is there a way to turn on more debugging or anything?

It does NOT do this with eclipse 3.3. It does this with 3.4, 3.5, and ME. Any ideas on what to test?

[support-shalini]

atomz4peace,
Thank you for the details. I will escalate this to the dev team member. they will get back to you on this.

[Author]

Posts