Summary: The COM/CORBA Part A spec states that user exceptions go after return values in one place, and before return values in another. (3.2.10.3 and 4.1.3.1)
Summary: Several LifeCycle methods take a "key" argument, but do not clarify whether multiple NameComponents are allowed in a key, if ordering matters, etc.
Summary: The Externalization spec does not state how a stream implementation is to discover that a context exists when internalizing an object.
Summary: The standard stream data format does not define tags to be used to identify the beginning and end of a context.
Summary: The standard stream format should specify that it is portable across different ORBs and hardware, but not across streamable object implementations whch use different semantic content.
Summary: What happens when multiple calls are made to Stream::externalize() at the top level? Does the stream contain all those objects, and how does a client discover this?
Summary: If the ORB times out while LockSet::lock() is being called, how does the client know if the lock was granted or not?
Summary: If the ORB suffered a communication failure while LockSet::lock() is being called, how does the client know if the lock was granted or not?
Summary: In a non-transactional lock request, the lock identity is supposedly based on thread ID. How can the server code get the client thread ID when they may be on different machines?
Summary: It is not clear whether CosTransactions::Coordinator is responsible for freeing locks at the end of a transaction.
Summary: CosTransactions Coordinator does not have any IDL method to remember LockCoordinator. How does it know what Lock Coordinators should be informed to drop locks?
Summary: For a non-transactional client who wants to get a LockCoordinator, what input values should one use for the "which argument?
Summary: It seemed more useful for the concurrency service to be non-IDL, and just based on local thread identification.
Summary: When reading a stream, there is no way of telling where context (limited to calls to begin_context and end_context) end and a new one starts.. Resolved problem with new "tag-byte" 0xFF.
Summary: If CosGraphs::deep propagation value is encountered, is the Node"s related object supposed to get copied, too. What if LifeCycleObject delegates to CosCompoundLifeCycle::Operations?
Summary: The second pass of operation is to "cause the node and all of its roles" to be copied. How do you get related object of the NEW roles to be the New Node?
Summary: When Node::externalize_node is called, is node responsible for externalizing related object? What happens, if related object isn"t a CosStream::Streamable?
Summary: Role in new node are disconnected It"s role of read_graph to correctly establish new relationships. How is that accomplished?
Summary: When internalizing a relationships, how do the "shallow" nodes and roles get included?
Summary: I assume that we are allowed to scope membership in a collection via an interface test (e.g, must be rooted off of Collection) and throw an InvalidElement exception?
Summary: Using collection factories, can you add multiple elements at once, and/or add new create methods?
Summary: On CollectionObj->remove_element_at(IteratorRef), how does the collection "know" the index?
Summary: How do IteratorObjs and CollectionObjs share state?
Summary: What does the IteratorPositionInvalid exception mean? Is it only that the user has cycled through the list elements and that no reset() has been issued?
Summary: How does the Iterator know to become invalid when the Collection is altered?
Summary: Can an iterator "reset()" throw an exception such as IteratorPositionInvalid if it is wrapping a db cursor which has no facility for reset?
Summary: Where are the destroy methods on the Iterator or on the Collection?
Summary: Can an interator have a next_n()? Or is this supposed to be via subtyping the interface?
Summary: Is it correct to offer the vanilla collection methods and add a new set for keyed access?
Summary: Clarifications on interfaces which support QueryableCollection.
Summary: When using iterator operations like adding, inserting, etc., how are changes reflected back to the datastores?
Summary: Appendix D states that a challenge structure consists of the MD5 of the arguments, but does not specify how the arguments are laid into a stream of octets for the MD5 algorithm.
Summary: Is it not possible that objects in a collection could have changed in between calls to the iterator accessing them?
Summary: Several of the bullets in section 11.1.5 are unclear.
Summary: How does this operation work?
Summary: Section 11.4.2 para. 3 says that FieldValues may be NULL. What if my datastore is a flat file without a concept of NULL. Does NULL take on the value of empty string for flat files?
Summary: Is there a way that I can delegate the functionality of the Iterators to the RDBMS itself?
Summary: Need all operations on the Collection be made using the SQL-92/QOL-93? If so, how is it possible to handle flat file datastores?
Summary: Need the OQS have any interface with the POS? I don"t see how the two can be interfaced.
Summary: It is not believed that the spec ever defines what a "malformed" PropertyName is. The closest definition is in para on page 26, section 5.1.1.2 and is not much help
Summary: Issue regarding implementation of the Query IDL specifications on a Java ORB. Issue involves implementing following idl definition from the CosQueryCollection module
Summary: Existing software based on messages with ASNI format description and a future version based on IDL. Does anybody know something about such a compiler?