Subject: DevelopMentor License Still Pertinent - msg#00011

Previous Message by Date: click to view message preview

Re: Bug or typo in SharedStubs ?

Convert bytes to int! ----- Original Message ----- From: "Dominique Gallot" <dominique_gallot@xxxxxxxxxxxxxx> To: <JAWIN@xxxxxxxxxxxxxxxxxxx> Sent: Monday, September 08, 2003 9:37 AM Subject: Re: [JAWIN] Bug or typo in SharedStubs ? > >Is there no function that fits your needs? Then lets make one. > There is one in je java source code, but it does not seems welll written > > on the java side The function is definied as > > public static native byte[] invokeIG_I(int arg0, String arg1, int peer, > int flags); > > from the comments that means > > I int > G string > O out arg sizeof(int) > P array > S sized out/retval > > ---> So my the function returns a byte[], it should return a int ? no ? > However the jni c function is defined as returning a int and not a int[] ? > > > >Is this causing some problem? > > for me ? no, I don't use it, but if there is no needs for a jlong why don't > put a jint for the constancy. > > Regards, > > Dominique > > > > |---------+-----------------------------> > | | Roger I Martin PhD| > | | <hypernexdev@HYPER| > | | NEXINC.COM> | > | | Sent by: | > | | Discussion of | > | | Java/Win32/COM | > | | integration with | > | | Jawin | > | | <JAWIN@xxxxxxxxxxx| > | | ELOP.COM> | > | | | > | | | > | | 05/09/2003 13:52 | > | | Please respond to | > | | Discussion of | > | | Java/Win32/COM | > | | integration with | > | | Jawin | > | | | > |---------+-----------------------------> > >--------------------------------------------------------------------------- -------------------------------------------| > | | > | To: JAWIN@xxxxxxxxxxxxxxxxxxx | > | cc: (bcc: Dominique Gallot/BRU/MASTERCARD) | > | Subject: Re: [JAWIN] Bug or typo in SharedStubs ? | > >--------------------------------------------------------------------------- -------------------------------------------| > > > > > Is there no function that fits your needs? Then lets make one. > > On your second question about the jint on returns from org.jawin instead of > jlong, the native code does not produce jlong; the number will never be > that > big. Is this causing some problem? > -- > Roger > ----- Original Message ----- > From: "Dominique Gallot" <dominique_gallot@xxxxxxxxxxxxxx> > To: <JAWIN@xxxxxxxxxxxxxxxxxxx> > Sent: Friday, September 05, 2003 4:26 AM > Subject: Re: [JAWIN] Bug or typo in SharedStubs ? > > > > I should call an API which return an integer and have 2 paramters one > > integer and a string, no ? > > > > Dominique > > > > > > > > > > > > > ----------------------------------------- > CONFIDENTIALITY NOTICE > This E-mail message and any documents which accompany it are intended only for the use of the individual or entity to which addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If the reader is not the intended recipient, any disclosure, distribution or other use of this E-mail message is prohibited. If you have received this E-mail message in error, please delete and notify the sender immediately. Thank you.

Next Message by Date: click to view message preview

Callbacks

Hope someone can help me. I am trying to register a callback with a DLL Type Library without much success. I have created a class for the type (extends COMPtr) and have successfully implemented methods in this class to call the dll for primitive and String parameters. But when attempting to call methods that register a callback (passing a pointer to an interface also defined in the DLL) I'm not having any success. Can anyone help point me in the right direction as to what call and params I need to be making. The methods simply accept a single parameter (a pointer to callback instance). Both interfaces defined in the idl extend IUnknown. Not sure if this is relevant or not. Thanks mick

Previous Message by Thread: click to view message preview

Bug or typo in SharedStubs ?

Is this a bug In the Shared public static native byte[] invokeIG_I(int arg0, String arg1, int peer, int flags); As the method state IG_I it should return a int ? so why a byte[]. And in the cpp file the method return a jlong, not a jbyteArray ? same error for both SharedStubs Is this a typo ? Also, why all jni method return a jlong for the package com.develop.jawin and jint for org.jawin.marshal ? ( and the java class define a int ) Regards, Dominique Gallot ----------------------------------------- CONFIDENTIALITY NOTICE This E-mail message and any documents which accompany it are intended only for the use of the individual or entity to which addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If the reader is not the intended recipient, any disclosure, distribution or other use of this E-mail message is prohibited. If you have received this E-mail message in error, please delete and notify the sender immediately. Thank you.

Next Message by Thread: click to view message preview

Re: DevelopMentor License Still Pertinent

Stu would need to answer this. Jawin is now on Sourceforge so it is good you brought this up. I'll ask around for answers. Roger ----- Original Message ----- From: "Greg K." <Gregory_Kedge@xxxxxxxxxxxx> To: <JAWIN@xxxxxxxxxxxxxxxxxxx> Sent: Monday, September 08, 2003 5:35 PM Subject: [JAWIN] DevelopMentor License Still Pertinent > In the SourceForge distribution, there is a License.txt that pertains to > citing DevelopMentor for using the Jawin code. Is it still an expectation > give the "org.jawin" implementation that is now being offered? > > Kind Regards, > > Greg K. > > > ______________________________________________________________________ > IMPORTANT NOTICE: > The information in this email is confidential and proprietary to NexPress > Solutions LLC and may be legally privileged. It is for the intended > recipient(s) named above only. Any unauthorized review, printing, copying, > > use or distribution of this email by anyone else is prohibited and may be a > > criminal offense. If you have received this email in error, please notify > the > sender immediately by reply email and delete the original message. >