王在祥 wrote:
Attachment is some demo code on mapping IDL to Java5, the mapping is
compatible with old version, and require no change of the UNO runtime.
All the idea is just provide a more clear API for java to access exists
component and write new Components in java.
Not sure in how far your
Hi,
thanks for sharing your ideas ...
王在祥 wrote:
I am a beginner of OpenOffice and I am learning the SDK document now.
Instead, i found the mapping from IDL to java looks missing something:
1. the mapped Java classes contains less information than the IDL, By using
the Java 5 annotations
王在祥 wrote:
I am a beginner of OpenOffice and I am learning the SDK document now.
Instead, i found the mapping from IDL to java looks missing something:
The Java UNO language binding predates Java 5 by some years. That might
explain why some of its features look strange or less than optimal
The Java UNO language binding predates Java 5 by some years. That might
explain why some of its features look strange or less than optimal in a
Java 5 context. Also, we try hard to keep the Java UNO language binding
and Java UNO environment compatible with Java 1.3.
Sure. Is it possible to
王在祥 wrote:
The Java UNO language binding predates Java 5 by some years. That might
explain why some of its features look strange or less than optimal in a
Java 5 context. Also, we try hard to keep the Java UNO language binding
and Java UNO environment compatible with Java 1.3.
Sure. Is it
I am a beginner of OpenOffice and I am learning the SDK document now.
Instead, i found the mapping from IDL to java looks missing something:
1. the mapped Java classes contains less information than the IDL, By using
the Java 5 annotations will solve this problem, and we can even write no IDL
