CORBA24 — creation of arguments to TypeCode creation ops

It is not clear from section 10.7.3 of CORBA 2.3 how much param checking
the ORB operations for TypeCode creation should do. It is also unclear
whether only the BAD_PARAM exception should be raised, or whether some
others are legitimate; e.g. BAD_TYPECODE.

Here are some detailed questions on TypeCode creation argument checking:

1) should the operations that take a "name" argument check that it
is a valid IDL name? A non null string?

2) should the operations that take a "RepositoryId" argument check
that it has a recognisable format?

3) should the operations that take content and member types as
parameters check that they are legitimate; i.e. that they
don't have kinds tk_null, tk_void or tk_exception.

4) should the operations that take members check that the member
names are valid IDL names and that they are unique within the
member list?

5) should create_union_tc check that there are no duplicate label
values? Should it check that the labels' TypeCodes are equal to
discriminator TypeCode? Or equivalent?

6) should create_union_tc check that the supplied discriminator
type is legitimate?

There are probably more cases as well.

No Data Available