customizationsrt WrapScript happening before patches

I am trying to override a function using CustomizationsRT WrapScripts(). It appears that WrapScripts (which I call from my orphaned object's __Init( ) function ) is running *before* patches are being applied, so that after WrapScripts replaces the target function it then gets overwritten by a patch. If I put a breakpoint into the __Init( ) function then it appears to run in the desired order, ie after patches. Is there some additional magic needed to force the __Init( ) to run *after* patches are applied??Thanks, -Dave

Find more posts tagged with

Comments

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

The __init function is called by standard Livelink on initialization and before the patches.

The other magic you can do is create an orphan of the CustRTroot\Patch object. No documentation available, but an example of the use is its child object Standard, which patches the retrieval of the webLingo file and is used by the HTMLmap functionality.

Basicly what you do is setting the 2 features and create a features that refers to an object which contains patched features.

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: maandag 10 januari 2005 13:42
To: eLink Recipient
Subject: customizationsrt WrapScript happening before patches

customizationsrt WrapScript happening before patches Posted by EU0013859 (Pollock, David) on 01/10/2005 07:37 AM

I am trying to override a function using CustomizationsRT WrapScripts(). It appears that WrapScripts (which I call from my orphaned object's __Init( ) function ) is running *before* patches are being applied, so that after WrapScripts replaces the target function it then gets overwritten by a patch. If I put a breakpoint into the __Init( ) function then it appears to run in the desired order, ie after patches. Is there some additional magic needed to force the __Init( ) to run *after* patches are applied??

Thanks, -Dave

David_Pollock

Hans, Thanks, I was able to get this to work (creating the Patch orphan feature that references my override object took some trial and error; I finally created a global reference to my override object which I then moved to the patch orphan, and this seems to work). Maybe I'm missing something, but it still is odd to me that patches are applied *after* ospace __Init( ) functions are called, instead of *before*. Doesn't OT ever have to release a patch that fixes an __Init( ) function? And doesn't the fact that a patch will wipe out a WrapScript( ) function that is called the documented way (via __Init( )) cause lots of trouble for people who use WrapScript( )?-Dave

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Hi Dave,

That is indeed the way to create a reference to an object.

__Init functions don't do much in general. Most of the time they only register the object with a subsystem.

You exactly point out the reason why I created the Patch object.

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: maandag 10 januari 2005 18:27
To: eLink Recipient
Subject: Hans,

Hans, Posted by EU0013859 (Pollock, David) on 01/10/2005 12:23 PM
In reply to: RE customizationsrt WrapScript happening before patches Posted by hstoop (Stoop, Hans) on 01/10/2005 09:42 AM

Hans,
Thanks, I was able to get this to work (creating the Patch orphan feature that references my override object took some trial and error; I finally created a global reference to my override object which I then moved to the patch orphan, and this seems to work).

Maybe I'm missing something, but it still is odd to me that patches are applied *after* ospace __Init( ) functions are called, instead of *before*. Doesn't OT ever have to release a patch that fixes an __Init( ) function? And doesn't the fact that a patch will wipe out a WrapScript( ) function that is called the documented way (via __Init( )) cause lots of trouble for people who use WrapScript( )?

-Dave