On 7/7/06, Thomas Lange <[EMAIL PROTECTED]> wrote:
> BTW, can you pass me some reference about language binding? I looked > into dev guide but I've not found any code about component language > binding... I'd like to bind my component to JAVA too, It could be useful. What for?
for just being able to use my component form java. If it is just about being able to use your component from JAVA there is
no need for it. It does not matter in which language an existing component was written. You can use it from any UNO code written in language XY as long as there exists an UNO bridge for that language XY (and maybe the specific compiler). Thus if you write it in C or C++ it can be used e.g. from Python, Java and Basic as well.
Nice to know this, i'll try it now if i face too much trouble i ping you =) The advantage of writing the component in C/C++ is that (because OOo is
written in C++) there is no need for an UNO bridge on that side. That is if you call from a Java component into a Python component two UNO bridges and the office will be involved. Whereas if you have a Java component calling into a C++ component (or vice versa) there will only one UNO bridge and the office be involved. Since I'm not familiar with the implementation of UNO and the UNO bridges I must admit though that I don not know if in the case of Java component 1 calling Java component 2 any UNO bridge is involved or not.
Its not necessary, I wrote it in C++. Thomas
Thanks for now
