Bug 1617 - Valuetypes that support concrete interfaces must inherit from PortableServer::ValueRefCountBase.
Summary: Valuetypes that support concrete interfaces must inherit from PortableServer:...
Status: NEW
Alias: None
Product: TAO
Classification: Unclassified
Component: IDL Compiler (show other bugs)
Version: 1.3.6
Hardware: All All
: P3 normal
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 2003-10-21 05:39 CDT by George Thomas Edwards
Modified: 2018-01-15 11:21 CST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description George Thomas Edwards 2003-10-21 05:39:12 CDT 
Valuetypes that support concrete interfaces must inherit from 
PortableServer::ValueRefCountBase.
Comment 1 George Thomas Edwards 2003-10-31 12:26:17 CST 
Assigning to George Edwards.
Comment 2 Johnny Willemsen 2004-01-04 05:50:41 CST 
changed version info
Comment 3 Johnny Willemsen 2006-04-11 08:32:13 CDT 
to Kees as part of valuetype work
Comment 4 Johnny Willemsen 2006-04-11 08:36:08 CDT 
seems to me that PortableServer::ValueRefCountBase has to be added as class to
the valuetype library in its own file.
Comment 5 Johnny Willemsen 2007-12-17 13:12:23 CST 
pool
Comment 6 Jeff Parsons 2007-12-18 14:19:36 CST 
If the valuetype supports any interface, abstract or concrete, its OBV_ class already has CORBA::DefaultValueRefCountBase as a mix-in. This may not be compliant, but _add_ref() and _remove_ref() are needed elsewhere in generated code, so fixing it will take some time and thought. And its presence means that mixing in PortableServer::RefCountBase at the application level will cause a operation name clash compile error.