[Scott Hamilton]

Dunno if this is a bug so much as a potential area for performance improvements.

Our application is large and complex and has some 5k+ beans defined in many different spring context files (over many different MyEclipse projects).

The trouble we have is that if I start typing:

<bean id=”does.not.matter” class=”still.does.not.matter”>
<property name=”autocomplete works great here” ref=”

BOOM – the IDE will lock up for 2-3 minutes while it builds a a list of beans to supply for the bean reference.

Given the size of our application, I don’t know what optimization could be done to this code but certainly it would be nice if a try could be made.

HOWEVER, maybe there’s a way to at least turn off autocomplete in the spring editor that you could tell me how or else consider that part of an enhancement request?

Thanks!

My Installation Details:
*** Date:
Monday, August 23, 2010 6:23:57 PM EDT

** System properties:
OS=windows 7
OS version=6.1.0
Java version=1.6.0_16

*** 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
R:\bin\myeclipse-7.5\myeclipse.exe
-name
Myeclipse
–launcher.library
R:\bin\myeclipse-7.5\../genuitec-common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
R:\bin\myeclipse-7.5\../genuitec-common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
-clean
-configuration
configuration
-vm
R:\bin\jdk1.6.0_16\jre\bin\client\jvm.dll

[support-shalini]

scotthamilton77,
Are there any errors logged in the log file located at workspace dir > .metadata > .log when the CA is invoked? Please clear the file, save it and then invoke CA to get the relevant errors.
Also, I noted that you are using ME7.5, the current stable version of ME is 8.6 which has improved performance.
Can you upgrade to the latest version and check if that helps?

[Scott Hamilton]

As for trying out the 8.x version I would like to – need to budget some time to do so, however. I have to get that to the point where all the projects are imported and building successfully to compare apples to apples (as much as possible here).

The .log file has no errors that seem relevant to this case. The only one I see [repeated several times] on a clean .log looks like this:

!ENTRY org.eclipse.core.resources 4 2 2010-08-27 15:33:24.286
!MESSAGE Problems occurred when invoking code from plug-in: “org.eclipse.core.resources”.
!STACK 0
java.lang.NullPointerException
at com.genuitec.eclipse.ast.deploy.core.Deployment.resourcedDeleted(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ProjectDeltaVisitor.visit(Unknown Source)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:55)
at com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder.?(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder.buildDelta(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder.build(Unknown Source)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

[support-shalini]

scotthamilton77,
I shall escalate this issue to the dev team member.
They will get back to you on this.

[Scott Hamilton]

Thanks!

[Author]

Posts