Issue 802:  POAManager (02) (port-rtf)
Source:  (, )
Nature:  Uncategorized Issue
Severity:  Minor
Summary: Summary: How does a POA associate itself with a POAManager?
 

Resolution: 
Revised Text:  clarified/fixed
Actions taken:
December 12, 1997: received issue
January 12, 1998: moved from C++ to Portability RTF
February 22, 1999: closed issue
Discussion: 
 closed issue
End of Annotations:=====
Return-Path: <michi@dstc.edu.au>
X-Authentication-Warning: tigger.dstc.edu.au: michi owned process
doing -bs
Date: Fri, 12 Dec 1997 09:05:28 +1000 (EST)
From: Michi Henning <michi@dstc.edu.au>
To: cxx_revision@omg.org, issues@omg.org
Subject: DynAny create member ambiguity


The spec for DynAny says:

	"The rest of the operations used to create DynAny objects
	 receive a TypeCode input parameter and throw the
	 InconsistentTypeCode exception if the TypeCode passed as a
	 parameter is not consistent with the operation."

This is ambiguous. What does "not consistent with the operation" mean?
In particular, it is not clear whether the following is legal:

	// IDL
	typedef string address;

	// C++
	CORBA::DynAny_var da;
	da = orb->create_basic_dyn_any(_tc_address);	// Doubtful?
	da->insert_string("Uni of Qld 4072");

Here, I am using create_basic_dyn_any(), but the type code I supply
is an *alias* for a basic type. The spec does not make it clear
whether this is legal.

I believe it should be.

							Cheers,

								Michi.
--
Michi Henning              +61 7 33654310
DSTC Pty Ltd               +61 7 33654311 (fax)
University of Qld 4072     michi@dstc.edu.au
AUSTRALIA
http://www.dstc.edu.au/BDU/staff/michi-henning.html