module/ospace loading order at startup

What controls the loading order o ospaces in different modules? How can I make sure all the ospaces in my module to be loaded after the core Livelink modules?What I saw on my server is: some of my ospace were loaded before core Livelink ospaces/modules, while my other ospaces were loaded at the end. Thanks.Cecilia

Find more posts tagged with

Comments

sıɹɥɔ

Message from Chris Webster <cwebster@opentext.com> via eLink

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

Ospace load ordering is determined by dependencies established through object orphaning. Typically you don't need to specify ordering as dependencies will "automatically" be defined by orphaning that is done during development. If for some reason your ospace needs to load after another ospace without there being any orphaning between them you need to create a "dummy" orphan e.g. orphan the other ospace's Root object and perhaps create a Documentation feature with a note as to why that orphan dependency exists.

(Note that these ospace ordering dependencies are completely distinct from the WebModule dependencies that define installation-time ordering and not load-time ordering.)

Hope this helps,

-chris

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: Wednesday, June 18, 2008 10:54 AM
To: eLink Recipient
Subject: module/ospace loading order at startup

module/ospace loading order at startup

Posted by bmouser5 (Qian, Cecilia) on 06/18/2008 11:50 AM

What controls the loading order o ospaces in different modules? How can I make sure all the ospaces in my module to be loaded after the core Livelink modules?

What I saw on my server is: some of my ospace were loaded before core Livelink ospaces/modules, while my other ospaces were loaded at the end.

Thanks.

Cecilia

Cecilia_Qian

Chris,Thank you for your prompt response. I'll give it a try.Two more questions related to the subject:1) Based on the livelink log, it looks like livelink loads the osapces based on the object number of each ospace. Is this true?2) If 1) is true, then how Livelink determines the object number for an ospace root object? What baout other non-root objects?Thanks.Cecilia

Hans Stoop

Message from Hans Stoop via eLinkIt is the otherway around, Livelink assigns the OSPace number based onthe initialisation order.Every object within an Ospace get an internal number assigned based onthe order of creation. The complete reference number is 'osapceinitialisation order' concatenated with 'internal number'.Hans> -----Original Message-----> From: eLink Discussion: Development Discussion > [mailto:development@elinkkc.opentext.com] > Sent: woensdag 18 juni 2008 20:41> To: eLink Recipient> Subject: Chris,> > Chris,> Posted by Qian, Cecilia on 06/18/2008 02:38 PM> > Chris,> > Thank you for your prompt response. I'll give it a try.> > Two more questions related to the subject:> 1) Based on the livelink log, it looks like livelink loads > the osapces based on the object number of each ospace. Is this true?> > 2) If 1) is true, then how Livelink determines the object > number for an ospace root object? What baout other non-root objects?> > Thanks.> > Cecilia> > [To reply to this thread, use your normal E-mail reply function.]> > ============================================================> > Topic: module/ospace loading order at startup> https://knowledge.opentext.com/knowledge/llisapi.dll/open/14663655> > Discussion: Development Discussion> https://knowledge.opentext.com/knowledge/llisapi.dll/open/786303> > Livelink Server:> https://knowledge.opentext.com/knowledge/llisapi.dll> > To Unsubscribe from this Discussion, send an e-mail to > unsubscribe.development@elinkkc.opentext.com.> > >

Cecilia_Qian

Hans,Thank you for your response.Cecilia