In more recent projects I’ve written my agents in Java. Although it meant copying some code across (and in some cases, rewriting it a bit because the agents were not using OpenNTF Domino API), it helped keep muscle memory.
However, I encountered some strange behaviour when refreshing design of the databases. LotusScript agents were fine, XPages were fine, XPages Java code was fine. But changes were not picked up on agents.
It turns out refreshing design does not work for updating Java agents. However, replacing design does.
A minor tweak, but one that helps keep me sane, until scheduled XOTS tasks are available.
I not sure that is a general rule. I never use replace and my java agents still gets updated from the templates.
Very strange Paul. I refresh designs all the time, especially when moving design changes from my local environment to a client’s QA environment and have never faced this particular problem.
And I would’ve noticed as 95% of my logic is written in Java. Is this still happening on your side?
Strange indeed. I was able to reproduce it. Maybe it was something with my agent. I’ve only recently started using Java agents and had problems over a few months with NoClassDefFoundErrors on a class in a Script Library called by the agent. Whenever I refreshed design, even though the database I took the template from worked fine, the database threw this error. The only way round it was to edit and save the script library, then edit and save the agent. So I moved the script library into the agent.