Issue 10554: Request clarification on interface of DLRL object with multi-attribute (data-distribution-rtf) Source: OCI (Mr. Donald Busch, busch_d(at)ociweb.com) Nature: Clarification Severity: Summary: Does a Collection attribute have a setter? For example, suppose I have a Foo with a List<Long> in it (this isn't valid IDL, please humor me): valuetype Foo : DDS::ObjectRoot { public List<long> my_longs; } That generates a Foo::get_my_longs() in the target language. Should it also generate a Foo::set_my_longs() in the target language? Or should there simply be a Foo::get_my_longs(), and I modify the List<long> via add, put, etc? Resolution: Revised Text: Actions taken: December 22, 2006: received issue Discussion: End of Annotations:===== il-OSG: gR2SuQMVM1l65vIKLyEVcpmUoW29HFodUHqNP3bLSVa.Zmtj.z4g7kgvkpuurWlZJipMrKPhg_rwrcrXbGnfTQHk5PS_QWbtSh67OLzx.0G901g.RNeQGugVxqDI_wRrnJE6ChKuOBe3hfA- Date: Fri, 22 Dec 2006 17:07:57 -0600 From: Don Busch User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) To: issues@omg.org Subject: DDS 06-04-09, DLRL Issue: Request clarification on interface of a DLRL object with a multi-attribute (or multi-relation) Does a Collection attribute have a setter? For example, suppose I have a Foo with a List in it (this isn't valid IDL, please humor me): valuetype Foo : DDS::ObjectRoot { public List my_longs; } That generates a Foo::get_my_longs() in the target language. Should it also generate a Foo::set_my_longs() in the target language? Or should there simply be a Foo::get_my_longs(), and I modify the List via add, put, etc? -Don Busch -- ---------------------------------------------------------------- Don Busch, Principal Software Engineer and Partner Object Computing, Inc. (OCI) http://www.ociweb.com http://www.theaceorb.com http://jacorb.ociweb.com "Never let what you can't do get in the way of what you can do." - John Wooden ----------------------------------------------------------------