Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

OpenEdge 10
Dynamics 2.1

SYMPTOM(s):

adm2 custom procedures (adm2/datacustom.p ) not running on AppServer

Extending Dynamics object classes

CAUSE:

Somehow, one may expect everything to be started from the Dynamics environment by relying on the definitions of classes in the repository. But, the White Paper Extending Object Classes with Progress Dynamics® says in the ADM Customization Chapter:
Recompile all the static Objects that you want to inherit the new behavior. The static objects will include the custom include file in the procedure, which in turn will cause the custom super procedure to be started at runtime and added to each Object's stack.
Then it refers to Progress Dynamics Programming Handbook on Writing Super Procedures for Dynamic Objects, which reads:
2.2.5 ADM customization
[...]
Every Viewer you create will now inherit the behavior defined in viewercustom.p. Remember that you have to recompile the physical procedure that is the driver for dynamic Objects of the type. For Viewers, for example, this is the file ry/obj/rydynviewv.w.

FIX:

Recompile the rendering procedure of the objects that require the adm2/custom procedures, like dynsdo.w for object that will use adm2/custom/datacustom.p.
Note that procedures like dynsdo.w and dyncontainer.p are registered as 'Static Object' in the repository, so according to the white parer they should indeed be recompiled.