To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=83863
------- Additional comments from [EMAIL PROTECTED] Wed Dec 12 14:33:06 +0000 2007 ------- Thinking further about my previous comments: - The concept of OIDs should be considered an implementation detail of UNO, not visible to users of UNO. It is most unfortunate that com.sun.star.uno.UnoRuntime.generateOid is a publicly available Java method, see issue 84491. - The way OIDs are used in UNO, their uniqueness is only important relative to the objects' life cycles (i.e., it is no problem if two objects have the same OID as long as those two objects are never active at the same time, see <http://udk.openoffice.org/common/man/lifecycle.html>). As a result, the way OIDs are implemented in UNO, their uniqueness is not guaranteed across time. The documentation of the (conceptionally private, see above) com.sun.star.uno.UnoRuntime.generateOid method can be considered misleading here. - One consequence of OIDs being an implementation detail of UNO is that the writer code's approach of generating and discarding UNO wrapper objects around core writer C++ objects on the fly is legitimate---there is no way for a client to distinguish this behavior from a behavior where the wrappers remain "fixed." - Another consequence is that client code cannot access UNO objects through anything but the (language-binding dependent) references to objects and the (language-binding dependent) equality checks on those references. In particular, there is no way to use something other than such a reference itself (e.g., a string) as a replacement representation for the reference (modulo differently typed references to the same object, which *can* be used as replacements for one another). --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
