-
Every time I launch DDE it does a rebuild, as if the code has changed since the last time DDE was launched, when only DDE is used to change code. While it’s doing this rebuild, DDE is essentially completely useless for a full minute. This unusability extends to each and every Lotus window that’s currently open. So the Client and Administrator are equally uselessly unresponsive during this automagic rebuild that can’t be prevented. Basically the developer launches DDE, then picks belly-button lint until the “Gold” product deigns to function again.
-
If some “setup” is needed for the first build it would make considerably more sense to do that setup the first time a build is done, rather than at DDE start. If that setup is going to, in effect, disable everything for a full minute, then it makes considerably more sense to present a progress dialog or something so the user knows the system will be dead for a while. The three crawling boxes imply something in the background, not a near total lack of response from everything Lotus on the machine.
-
Since DDE is so unstable, and must be launched multiple times per day, one discovers that it takes a fraction of the time to do this rebuild on subsequent launches, that boot-up, than it does the first time. Perhaps this isn’t a rebuild at all, but some other goofy automagic razzle-dazzle? All I know is this appears in the log every launch:
<values>com.ibm.designer.domino.ipc.exception.IPCException: Automatic Recompilation: Unsupported design element
	at com.ibm.designer.domino.lscript.ipc.IPCHelper.processResponse(Unknown Source)
	at com.ibm.designer.domino.lscript.ipc.IPCHelper.sendIPCMessageBackground(Unknown Source)
	at com.ibm.designer.domino.lscript.ipc.IPCHelper.sendIPCMessage(Unknown Source)
	at com.ibm.designer.domino.lscript.ipc.LSApiSessionManager.recompileNote(Unknown Source)
	at com.ibm.designer.domino.lscript.builder.LSAutoRecompilationTree.runCompilations(Unknown Source)
	at com.ibm.designer.domino.lscript.builder.LSBuilder.build(Unknown Source)
	at org.eclipse.core.internal.events.BuildManager$2.run(Unknown Source)
	at org.eclipse.core.runtime.SafeRunner.run(Unknown Source)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(Unknown Source)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(</values> <values>Unknown Source)
	at org.eclipse.core.internal.events.BuildManager.build(Unknown Source)
	at org.eclipse.core.internal.resources.Project.internalBuild(Unknown Source)
	at org.eclipse.core.internal.resources.Project.build(Unknown Source)
	at com.ibm.designer.domino.ide.resources.project.BuildJob.runInWorkspace(Unknown Source)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(Unknown Source)
	at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
Caused by: java.lang.Exception
	at com.ibm.designer.domino.ipc.exception.IPCException.<init>(Unknown Source)
	... 16 more
</values> -
And I know effectively disabling the entire system every time DDE launches gets old faster than my rants.
Subject: any chance I could have a sample db that gives that error?
“unsupported design element” looks suspicious and it would be good to track that down.
What shows in the progress bar during the time it appears to be building? Is it by any chance “initializing Java tooling”?
thanks