Re: [Wrapper-user] DCOM and wrapper

[Jim R. <jr...@er...>]

Leif,

On 2003.10.30 18:06, Leif Mortenson wrote:
> Jim, Philip,
>    Sorry to hear that you had never gotten that working Jim.  As I 
> said before however, I have never used the COM interface nor have any 
> plans to in the foreseeable future. I would not know where to start 
> trying to fix this with what I have to go on right now.

I haven't really had a chance to get back to it, but that's partly 
because I don't know what to check next.

> 
>    If one of you guys could write up a simple simple application 
> which demonstrates this problem and explain to me what is going, I 
> might be able to figure out the problem and learn a little about COM 
> at the same time :-)  I emphasize the word simple here.

Wow, you managed to use "simple" and "COM" in the same sentence.  Is 
that gramatically correct?

> 
>    In either case the Wrapper process is using the CreateProcess API 
> to create the

The "CreateProcess" seems to have some inherent COM qualities, though 
what I haven't a clue.

Jim


> Jim, Philip,
> 
> 
> Jim Redman wrote:
> 
>> Philip,
>> 
>> I hit the same basic problem - and have no solution.  In my case, I 
>> received an iMarshall request, then no other COM requests.  Again 
>> the app works find as a batch file, just not in the wrapper.  I have 
>> no further clues.
>> 
>> Jim
>>  On 2003.10.30 12:13, Philip Kubat wrote:
>> 
>>> My application is a WMI (Microsoft Wbem) java application.  I have
>>> used JNI
>>> to access WMI via DCOM.  The applications works fine if it is run 
>>> via
>>> the
>>> command line and java.  It does not work within wrapper.  I believe
>>> the
>>> problem is how I am "passing" the pointer to the IWbemServices 
>>> object.
>>>  In
>>> msdev debug I do not seem to retain a valid object (via pointer) of
>>> the
>>> object that I need methods of in additional JNI calls.  I have two 
>>> JNI
>>> functions.  One that creates and connects to WMI via DCOM then 
>>> stores
>>> the
>>> pointer into the java environment (in the object that makes the
>>> function
>>> call to JNI).   The second uses methods of that WMI object via the
>>> pointer
>>> to retrieve system data, this methods is used several time through 
>>> out
>>> the
>>> application.  Any ideas and thought would be helpful.
>>> 
>>> 
>>> 
>>> Does wrapper some who create new threads for these JNI calls?   Do I
>>> need a
>>> better means to pass the pointer?  Is there a what to protect the
>>> memory of
>>> that pointer?
>>> 
>>> 
>>> 
>>> Thanks!
>>> 
>>> 
>> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
-- 

Jim Redman
(505) 662 5156 x85
http://www.ergotech.com