When using the Eclipse LotusScript Editor I frequently get issues with elements giving errors when referencing objects in script libraries that are nested in other libraries.
Example:
LibraryB defines the function test()
LibraryA defines some other functions and has Use “LibraryB”
AgentA has Use “LibraryA” and tries to call test()
If the code is compiled using recompile all, it works just fine, but if I go into AgentA, sometimes it will tell me that test() is not defined… even after recompile all.
The work around for it is to manually open LibraryB first, then open LibraryA. Then the error will disappear in AgentA.
What is odd is that it doesn’t always have a problem and isn’t related to changes to the libraries becomes in most cases they haven’t been touched. It just seems like the LS Editor sometimes stops checking through dependencies.
Subject: inconsistent results from nested script libraries
i’ve had exactly the same experience. i had several nested script libraries that were called by a webquerysave agent. in a browser, i could save the same page say 20 times in a row: sometimes the agent executed perfectly and sometimes it gave an error saying it couldn’t find a function that was saved in a script library. there were no other changes to the code or the server environment. success and failure just depended on the “mood” of the server at any given moment. i ended up combining the script libraries into only 2. it worked for a while.
now i’ve made a change inside the nested script library of the 2 that remain. one server recognises the change automatically. another server, despite having the very same change, does not recognise the change. on the second server, i had to re-save the parent script library and then re-save the calling agent before it would recognise the change. now my boss tells me that the mirror of the second server isn’t getting the change…
and I don’t have the option to recompile all the libraries (since that re-signs everything with my id). There’s certainly an element of caching involved. I posted before that sometimes changes in LS code made on another machine do not show up, even though it executes.