Correct way to orphan objects

Hello,

This question is mainly aimed at OT DEV, so I hope someone is monitoring this. In CS 10.0 and earlier when I wanted to build an Admin section for my module, I'd go to $WebAdmin, and orphan the AdminIndexCallbacks object. I assume that in the 10.5 world, the correct approach is to a) create a new package, then b) create a new object which would take said object as a parent. If so, I am assuming that I would start typing and the type-ahead feature should find the correct object to orphan from. When I do that,, I'm not finding the specific object I want :

Looking at the module browser, I can see clearly that the AdminIndexCallback exists:

So my question is, what is the correct way to add this orphan to my module and package in 10.5? Is it my imagination or are some parent objects not showing up when I use the autocomplete/browse feature for creating a new object?

Thanks in advance.

-Hugh Ferguson

Find more posts tagged with

Comments

HFCDev

Quick addendum: The browse for parent feature seems to be unable to select (or selectively unable to select) orphans. In my particular example, it would find the parent IndexCallback under WebLL, but I want to orphan the orphan as it were. This is a common requirement in Oscript development.

Appu_Nair1

you might want to use the four square :: things so it will be like so I was confused as well

if that is not what is being asked I know not

Appu_Nair1

screen cap lost I think

appu_screen.docx

HFCDev

I think I found the answer. The browse for parent objects autocomplete only works as a "starts with" type feature. For instance, just sticking in AdminIndexCallback won't find the correct object. Instead, I had to start with WEBADMIN:: and then it found it, i.e:

This does act as a segue into another question: In the past, I would orphan, say $WebLL.LL on which to base my request handlers, then add children beneath. This doesn't seem to be possible any more. Often when creating request handlers, a developer would make one orphan, set the fFuncPrefix feature, perhaps add some additional features and scripts that are common to all their request handlers, and add new request handlers as children of the just created orphan. This doesn't seem to be possible any more. Can someone from OT DEV comment? I have tried adding a new object with my original orphaned object as the parent but I can't get that to work.

-Hugh

HFCDev

Hi Appu,

Ironically, I succeeded in creating an orphan of this particular object yesterday while investigating that other thread to do with creating callbacks (you can see my responses there). What I'm noticing is that the Browse for parent objects seems to match quite selectively and I'm not absolutely certain what the pattern is.

I suspect that there are changes to the rules regarding orphaned objects. I need to find clarification on what those changes are.

-Hugh

Darcy_Casselman

Hugh, your asssumptions are correct. Orphans are just objects whose parents come from other ospaces. You should be able to search for them by typing their name in the Browse dialog.

But there's a bug I need to investigate where some objects don't show up if you just type their name. Although typing their full package name seems to work, as you've discovered.

Besides removing the explicit "create orphan" UI gesture, we haven't done anything to restrict what orphans can be generated. I'm not aware of any changes to Content Server that would prevent orphans of WEBLL::LLRequestHandler or WEBNODE::NodeRequestHandler::LL being created (although I should point out that you can't create orphans of globals as globals only exist at run time). And you should absolutely be able to create children from any object in your ospace, including orphans.

Darcy.

HFCDev

Hi Darcy,

While you're at it, can you investigate these two use cases:

1) Create a child of my orphan by right clicking on the package in which I wish to construct it. The package name shows up, but I can't get my orphan to show up.

2) create a child of my orphan by right clicking on the orphan itself. In this case, the package can't be found. I'm attaching screen shots.

-Hugh

Scenario 1:

Scenario 2:

HFCDev

For the record, I am able to make Scenario 2 work if I populate the package information manually. It's the browse for my package that fails but once I enter it manually, it seems to work.

-Hugh

Darcy_Casselman

Thtat is odd.

I can only assume that the metadata caches in CSIDE aren't being updated properly. I'll look into it.

You may be able to get it to work by restarting Content Server (or possibly Eclipse entirely)

Darcy.

HFCDev

Yes, shutting down Eclipse does solve the problem.