1.Because execution occurs at the behest of the applet, the applet is not listening for spurious executions.
2.I would modify "startserver" in dx/java/server/bin, e.g. set DXMDF . Pete William Matthews wrote: > I tried changing the call to DXLExecuteOnce to DXLExecuteOnChange in > DXApplication.java but this didn't seen to work. How does > DXLExecuteOnChange notify the applet that it is/has been run? Can it? > > Also, what is the best way to load mdf files for nets executed by > javadx? Right now, I have a hacked dxworker script that just adds a > command line argument when it calls dxexec. There must be a better way to > do this. > > William Matthews > [EMAIL PROTECTED] > > > You have it right. I'm going down the hall to talk to Benevolent Dictator > > about how best to implement a true "execute on change" for javadx. > > > > Pete > > > > > > William Matthews wrote: > > > > > What changes would be necessary to java explorer to get execute on change > > > to work properly with custom modules using DXReadyToRun() (on the > > > server side)? It appears that the current java explorer implements > > > execute on change with calls to execute once when it thinks that the data > > > has changed (from the client side). > > > > > > William Matthews > > > [EMAIL PROTECTED]
