I would recommend JNI on the server side. I have used things like JNative in the past for simple things, and JNI for more complicated ones.
For your specific issue, make it platform independent. Simply have another thread (JMS, EJB asynchronous, etc) that uses a ProcessBuilder and Process#waitFor. I usually pass things back via stdout, but I guess you can share diskspace if necessary. You will need some push mechanism. It seems most use comet-style pushing (ref: http://code.google.com/p/rocket-gwt/wiki/Comet) from reading these threads. On Mar 1, 2:33 am, ArmanGal <[email protected]> wrote: > We used C++ browser add on that allows javascript to communicate with C > ++ object (in browser) where C++ executes commands on registry/file > system/... and also we were listening for events on DOM object that C+ > + triggered in order to invoke some functionality in GWT. > > On Feb 26, 7:55 pm, Alexander <[email protected]> wrote: > > > Hello everyone, > > > I would like my GWT application to communicate with a Windows > > Application. > > > on the presentation layer. It is no problem to start the Windows > > Application. Something that works using a special URL redirect. Now I > > wonder how both can communicate at Runtime: > > > 1) The GWT App needs to know when the other application finishes. > > 2) The GWT App needs to receive return parameters from the other > > application. > > > I had two ideas in mind, but I don't know whether this will work. > > > 1) Let them communicate over a shared temporary file > > 2) Use some sort of AJAX-Magic > > > Is there any common approach? Any experiences? Any help appreciated! > > > Thanks in advance! > > Alexander > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
