Bernie
Wed Nov 09 23:25:59 CST 2005
Thanks JW!
"mr_unreliable" <kindlyReplyToNewsgroup@notmail.com> wrote in message
news:ep$eqPY5FHA.2916@TK2MSFTNGP11.phx.gbl...
> hi Bernie,
>
> O.K., so you don't want to use a file.
>
> When you say "direct call" as with an ocx, you are talking "COM"
> (Component Object Model), the latest Microsoft hot technology,
> that is until the net framework came along.
>
> afaik, Java doesn't support com interfaces directly, but if you
> google on it, you will find 3rd-party software packages that do
> provide for "interoperability" -- i.e., that allow for adding
> com-compliant interfaces to java programs.
>
> Here are just the first two candidates that cropped up.
>
> J-Integra for COM, (purchased software), found here:
>
>
http://j-integra.intrinsyc.com/products/java_com.asp
>
> And, "The JACOB Project: A JAva-COM Bridge" (available from
> Source Forge, and so apparently freeware), found here:
>
>
http://danadler.com/jacob/
>
> There are probably others.
>
> cheers, jw
>
> p.s. My own favorite "trick" when dealing with a non-COM app
> (such as a mini-app written in AutoIt) is to simply present a
> textbox on the main form/window of the app, and then use
> sendkeys (or something similiar, like cut-and-paste) to enter
> text in the non-COM app's textbox. Then the non-COM app is
> programmed to look in its textbox for messages from me.
>
> Another "trick" that is used sometimes is to simply call the
> app, with the text message as a parameter. Like this:
>
> NONCOM.EXE /M:"This is a text message"
>
> Some languages have a "previous instance" capability (vb has it).
> The noncom app is programmed to test for a previous instance
> of itself running. If there is a previous instance, it will just
> pass along the parameter (the text message) to the previous
> instance, using whatever native capabilities that language has
> for passing along data. For example, the "SendData" api call.
> This could continue indefinitely, i.e., you could just keep
> passing messages this way. The receiving app would be programmed
> to keep handling your messages until something like "QUIT" or
> "EXIT" shows up.
>
> Then there is DDE (Dynamic Data Exchange), which was Microsoft's
> latest hot technology before COM came along, but is still
> supported.
>
> I could go on-and-on, but the dinner bell is ringing.
>
>
> Bernie Hunt wrote:
>> JW,
>>
>> The java app belongs to the user. It can be modified, so I can somewhat
>> dictate what is needed. The applicaiton is to pass a status message to
>> their application and have it store it in their log. Obviously I could
>> write the message to a file and have their app pick up the message when
>> they see the file exits, but I was hoping for a direct call to the java
>> app, like you can call into an OCX.
>>
>> Bernie