To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=78308
User sb changed the following:
What |Old value |New value
================================================================================
Component|api |udk
--------------------------------------------------------------------------------
Ever confirmed| |1
--------------------------------------------------------------------------------
Status|UNCONFIRMED |STARTED
--------------------------------------------------------------------------------
Priority|P2 |P3
--------------------------------------------------------------------------------
QA contact|[EMAIL PROTECTED] |[EMAIL PROTECTED]
--------------------------------------------------------------------------------
Target milestone|--- |OOo 2.x
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Tue Jun 12 08:01:23 +0000
2007 -------
Java serialization and UNO are at odds. In a sense, URP is UNO's replacement
for Java serialization. Anyway, since some of the Java types representing UNO
type system entities are (indirectly) serializable (e.g., all UNO exception
types are represented by subtypes of java.lang.Throwable), something should be
done about this.
For all Java representations of UNO type system entities but for Java
representations of non-null references to UNO objects (UNO interface types),
adding serialization should be fairly straightforward. Remains the question how
to serialize such non-null object references. (All UNO types can recursively be
contained in UNO exception types, so even if we restricted ourselves to fixing
just the exception serialization problem, we would end fixing the generalized
serialization problem.)
For a non-null UNO object reference of interface type T (where T should probably
be the static type of the reference if it is a component of a sequence type or a
member of a struct or exception type, and the dynamic type T' if it is the value
<T',v> of an ANY), deserialization should probably produce a Java object that
implements all the methods of T (plus com.sun.star.uno.IQueryInterface) and
throws some specific java.lang.RuntimeException (like a
DeserializedUnoObjectReferenceException) on every method invocation. (In
general, it cannot work to serialize references to UNO objects and guarantee
that they are still functional upon deserialization, so this is probably the
closest possible general approximation.)
@ronald15: If you need a quick solution, I would suggest you either use UNO to
send exceptions from server to client, or send toString-representations of the
exceptions.
---------------------------------------------------------------------
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]
