Java save agent failure

Has anyone else run into this or come up with a fix.

When a Java agent is being developed and in debug it is common to make a change to a java class save it, save the agent and then run a test of the modified agent.

If the java class is saved but not the agent and then the test is run the unmodified code is run as expected. But once it has been run before the agent was saved it is no longer possible to save the agent and all code changes will be lost. A save agent request will be ignored and if it is Xed you will get the normal options to Save, Close without saving or Cancel but the Save option doesn’t Save and close the agent, it remains open until it is closed without saving or cancelled.

I know that I should save both each time but senility has set in.

Thanks

Don

Subject: Yes, I have seen this

Hi Don,

I don’t have a fix, but I can confirm this behaviour. At least, to a point. I can’t say for sure if running the agent while “dirty” subsequently prevents future saves, as you observed, but I will pay closer attention now to see if that is what is happening.

Incidentally, I have the property set to save the design element when the Java code is saved. This works very often, but then I get the situation you describe in which the agent itself does not save, even though the individual Java source code editors will save. However, if you cannot finally save the agent, those changes are lost.

It’s frustrating.