Re: Trying Jawin
Morten Andersen <[email protected]>
| Newsgroups | gmane.comp.windows.devel.jawin |
|---|---|
| Organization | Arosii Information Systems A/S |
| Message-ID | <[email protected]> |
Hi Olivier First sorry taking so long in answering your questions. Olivier Lefevre wrote: > I am new to Jawin and I have 3 questions: > * does the stub generator have an equivalent of the /xh > option of jactivex (MS JVM)? Sorry, I have newer worked with the MS JVM, so I don't know what this option does (or what the jactivex does, either) > * what is the performance impact of the Jawin approach > as opposed to raw JNI? Since this question, you send me (offlist) an elaboration on this question, that I have included for completeness below: "To elaborate on my 1st question, what I meant by raw JNI was to to use the MSVC++ compiler to write a small DLL calling the COM methods I need and exposing them with the signatures expected by the Java side. If you have only a handlful of methods to wrap, what are the advantages of Jawin as opposed to this manual method?" Jawin, is primarely for the scenario, where you don't have any experience with C/C++ coding of JNI. And where you don't want the tedious and errorprone task of manually writing the marshalling/unmarshalling between the JNI types and the native types (eg. from/to jstring to c Strings or char[], etc.). So I would say, that if you have the necessary JNI, COM and C experience, and you only have one single project where you need simple COM access, the barrier to learn Jawin is probably to high? (although if the COM objects you want to access, have scriptable IDispatch interfaces, the Jawin support is pretty good by now). With respect to the performance impact, we don't really have new measures but if you download the source-release, there are some old performance documents in the docs/perfdata folder, that you could check (but please be aware that the code have changed somewhat since these documents). > * why did my very first attempt to generate stubs against > a type library end in: [SNIP trace] We had previously had some reported issues, where errors happened due to spaces in the path for either the Jawin Typebrowser or the TLB to generate stubs for, can you verify whether this is the case for you? Best Regards Morten