Unable to use OTMAIL, NGD and RECMAN as parent objects

I'm trying to patch OTEMAIL::llnode (Document)::Email to diagnose a fault when adding emails to CS10.5.

When browsing for a parent Object to create from there is nothing under OTEMAIL::

Anyone else had this? Any workarounds?

I had the same behaviour with NGD, but I managed to get that working by importing NGD and right-clicking the object I wanted as parent. I've had similar problems with RECMAN, too.

Find more posts tagged with

Comments

John Simon

Hi John,

I find figuring out what to specify for inheritance frustrating, and the GUI does not seem to help so we no longer use it to create packages and scripts. To create a package we right click on our object and create a new folder, name it whatever. It shows in the gui as a folder until you put something in it (and maybe compile?!?). To create a script we right click on the package (or where ever) and create a new file, name it whatever.os. Then we have our package statement and the object we are going to inherit...for now we just point to the object's root. Ex:

package MODULE::Package::SubPackage
public object overrideEmail inherits MODULE::moduleRoot
end

Then we save and compile. NOW you can go back to the inherits statement and change it to what you want. I specified "inherits OTEMAIL::LL" and hit cntl-space and it should popup a list of objects you can inherit. I fiddled around and eventually ended up with

package PSXNOTIFY::Utilities::testjws
public object overrideEmail inherits OTEMAIL::LLNode_Document_::EMail
end

Now when I compile I get an "Invalid new parent" which I get fairly often going about it this way. But if I clean, close and reopent eClipse, it all seems to be OK. Just fyi, I am on 16.2 and running the latest drop-in (16.2.2.5).

Cheers...

John Underhill

Thanks John.

I found with NGD I could inherit from the module if I first imported it. Yes, I know this is dangerous (I backed up the module first then deleted it once I got what I wanted,. and restored the original). But then I could use the imported NGD as the object to create an orphan FROM. However, when I tried this on OTEMAIL, the imported module wouldn't compile. The iimported object names had parentises in Module view, but underscores in OScript view. I wonder if the import/compile can't cope with some characters in some modules? Presumably Open Text can compile their own modules.

Strange that the Orphan function is available in Module view (as if it was Builder), but doesn't do anything!

I did try creating a child from a flat,empty .os file, but I'll give your method a try, too.

John Simon

"I know this is dangerous" - because you are worried it will overlay the OLL from your source? We turn off Build Automatically (thanks to a warning from Appu!) which should prevent an accidental build, yes?

I haven't tried to import OTEMAIL but I hope the method I described works for you. If not, let me know and I will try importing.

Cheers...

John Simon

"Strange that the Orphan function is available in Module view (as if it was Builder), but doesn't do anything!"

Not sure I follow. When I right click on an object and New:Orphan, I get a pop up asking which Ospace to store the orphan in (the popup displays all unlocked modules). If I choose one it creates the orphan. I can "Show Inherited Features" and change whatever I want. I can save and it will build the new oll, I can start/stop eclipse and all of my changes are still there. However if I ever build the module from the Oscript Explorer view then all of the changes I made in Module Explorer are gone (because they were never part of the source code). I only know about this because I know of some prominent long time oscripters who (in a pinch) work this way (rather than deal with some CSIDE's "features")