|
>I'm having problems getting my Access Module to work
>with the Iconic Map. It works perfectly (sic) using
>the command line interface and with the command line
>interface within the Iconic Map.
>I have three levels of entities : a global entity, a
>subentity beneath the global one and another subentity
>beneath the first subentity.
>The Operations pull down menu displays the available
>operations for the global entity, regardless of which
>entity I am currently accessing. This is rather
>inconvenient! Is this a known bug in the Iconic Map, or
>does it sound like I am doing something silly?
If I understand you, you navigated down to your
subentity, selected the entity, and then pulled down
the operations menu. The operations menu contained
that of the global entity.
I have not seen this behavior before. Please send your .ms
file to BARREL::LEMMON and I will take a look at it.
>My second question is : I have been told that there is
>a bug in the Iconic Map which requires MMs to have a
>CREATE and DELETE directive for all entities. Is this
>correct? If so, why isn't it documented anywhere or
>mentioned in this Notes file? If not, sorry for the
>accusation!
The iconic map does not require a create and delete
directive. The domain fm requires all global entities
to be registered, hence they must provide the REGISTER
directive (with display=true) in the .ms file. You should
also provide (but it is not required) the DEREGISTER directive
too.
I might as well mention here that all entity classes must
support the SHOW IDENTIFIERS command, even if there aren't
any.
/Jim
|
|
.> I might as well mention here that all entity classes must
.> support the SHOW IDENTIFIERS command, even if there aren't
.> any.
>What is the MOM supposed to send back when it gets a SHOW IDENTIFIERS on
>an object that has no identifiers?
By decree of the entity model - All entities must have an identifier
partition. Even if that partition is empty, which is the case for
entities that have no identifiers. When coding a response to SHOW
IDENTIFIERS for entities that have no identifiers, you send back an
empty partition. This is accomplished, in MCC using ILV by coding
status = mcc_ilv_put_param_begin (...)
status = mcc_ilv_put_param_end (...)
If you code these back to back, passing the reply_id in the descriptor
that is an argument to mcc_ilv_put_param_begin, you will create an empty
ilv buffer. The clients understand this as an empty attribute
partition.
I would suppose that you would take whatever is the analogous route in
the MOM. I am not exactly sure how the encoding is done there.
...kjn
|