Can someone please help me with the steps/approach in order to override overrirde an existing patch? I need to ensure that the OpenText patch gets executed first & then the one which I plan to write.
Thanks, Amit
eLink : How to override an existing patch?How to override an existing patch? Posted byamit.tongaonkar@cognizant.com (Tongaonkar, Amit)On 08/31/2015 05:15 AM Can someone please help me with the steps/approach in order to override overrirde an existing patch? I need to ensure that the OpenText patch gets executed first & then the one which I plan to write.Thanks, Amit[To post a comment, use the normal reply function]Forum:Content Server Development ForumContent Server:Knowledge Center
Take a look at Hans Stoop’s reply inside the below discussion. This scenario is achieved using the CustomizationsRT module sans the disclaimer that this must be used ONLY as a last resort.
https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=17342512&objAction=viewincontainer&ShowReplyEntry=17345935#forum_topic_17345935
- Pramod
Amit
So you want to monkey-patch/duck punch an existing patch? Due to some missing functionality such as callbacks etc? If you are patching an existing one this can lead to an unstable system since the next patch may require different paths etc.
David
Hi Amit,
Patches with the same naming convention are usually applied in alphabetical order. Try and see if this works: Give your patch a name similar to the OpenText one and increment the last digit before the file extension. If this doesn't work then have a closer look at $LLPATCH.Utils.Sort and $LLPATCH.Utils.Patchto better understand how patches are sorted before being applied.
$LLPATCH.Utils.Sort
$LLPATCH.Utils.Patch
I don't believe there is a naming convention for third-party patches, so hopefully this doesn't conflict with anything else.
Good luck! Chris
HI Amit,
Chris is right about the alphabetically order. I prefer to name my patches with the current date so I’m sure they are always executed after the standard patches. Although my biggest preference is not to use patches at all. You need to check with every new patch if you need to update your own patch again.
The big question is why you need a patch in the first place, what do you try to establish? Maybe we know a different way to accomplish the same.
Patches are really the last resort. It even comes after reading the documentation.
Hans
From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]Sent: Montag, 31. August 2015 15:18To: eLink RecipientSubject: How to override an existing patch?
How to override an existing patch?
Posted bycmeyer@rhouse.ch (Meyer, Christopher) On 08/31/2015 09:11 AM
Patches with the same naming convention are usually applied in alphabetical order. Try and see if this works: Give your patch a name similar to the OpenText one and increment the last digit before the file extension. If this doesn't work then have a closer look at $LLPATCH.Utils.Sort and$LLPATCH.Utils.Patchto better understand how patches are sorted before being applied.
[To post a comment, use the normal reply function]
Topic:
Forum:
Content Server Development Forum
Content Server:
Knowledge Center