David Blezard wrote:
J.Ja, We have had some difficulty setting up the debugging that is similar to Joao question. If done correctly where A references B and B references C, should I be able to debug C without creating the "fake reference A->C? I understadn the idea of setting the entry espace, but, I do not recall seeing A when starting the debugger in C. David -
Make sure that both B and A have been published AFTER C, and make sure that B gets published BEFORE A.
This is all part of the overall architecture of how the DLLs (for .NET) and JARs/WARs (on Java) get built.
Under the hood, when you publish an eSpace it collects the most recent DLLs or JARs from the referenced eSpaces and Extensions and uses them in the publish. So on a .NET server, when you publish A it will make symbolic links in A's deployment directory to the DLLs compiled from B and C. On Java, I think it copies the JAR files for B and C and puts them into A's WAR.
When you turn on the debugger, the "entry eSpace" basically says "debug the code in THIS deployment directory which is the one that will service the request."
End result is that your publish order must be C, B, A, then set the entry eSpace to A, for debugging to work.
J.Ja
J.Ja, We have had some difficulty setting up the debugging that is similar to Joao question. If done correctly where A references B and B references C, should I be able to debug C without creating the "fake reference A->C? I understadn the idea of setting the entry espace, but, I do not recall seeing A when starting the debugger in C.
Make sure that both B and A have been published AFTER C, and make sure that B gets published BEFORE A.
This is all part of the overall architecture of how the DLLs (for .NET) and JARs/WARs (on Java) get built.
Under the hood, when you publish an eSpace it collects the most recent DLLs or JARs from the referenced eSpaces and Extensions and uses them in the publish. So on a .NET server, when you publish A it will make symbolic links in A's deployment directory to the DLLs compiled from B and C. On Java, I think it copies the JAR files for B and C and puts them into A's WAR.
When you turn on the debugger, the "entry eSpace" basically says "debug the code in THIS deployment directory which is the one that will service the request."
End result is that your publish order must be C, B, A, then set the entry eSpace to A, for debugging to work.
J.Ja