M
mopfer
Guest
We have an OpenEdge REST service with methods that are accessed in instances of singleton classes that were generated from PDSOE. In the methods of those singleton instances, we call some .ps and also use some ABL objects. We call the same programs from other applications with no unusual behavior, but in this configuration we are seeing scoping issues with static classes and global variables. What we see - at the beginning of the method we call a .p that changes three things: 1 is a public property in a static class that is used to make session information available to all ABL class-based objects in the session. 2 is a global shared variable that is used to make session information available to all .ps running in the session 3 is an update to a record in a temp-table record in a super-procedure that is used to make session information available to any process in the session that asks for it. When the .p is done, the changed value from #3 is visible to the singleton instance that made the call and to all other processes that are called from the singleton instance after that. The changed values from #1 and #2 are NOT visible to the singleton instance at that point, nor or they visible to any processes that are called from the singleton instance after that. This seems to us like it should be impossible, but it is happening. Does anyone have an explanation of how or why that would happen? We haven't been able to recreate the situation outside of our application, so we're thinking we've done something that we need to change, but taking pieces away from the singleton class until there is nothing left but the call to the .p and some code to see if the values are visible has not made the behavior change. Thanks, Mark Opfer DMSi Software
Continue reading...
Continue reading...