I updated this thread just in case another developers might come accross the same issue.

We found out that all events interface from PowerPoint library are defined not as usual dispinterfaces but as dual interfaces. Here is the quotation from the Microsoft support article:

Note that EApplication is derived from IDispatch and is not the dispinterface that is
commonly used as a source interface. If the source interface is a dispinterface,
you can determine the dispatch identifiers (DISPIDs) for its methods by using
the OLE/COM Object Viewer. However, because EApplication is not a dispinterface, you cannot
determine the DISPIDs for PowerPoint events by examining the type library.

That is why the "Codegen for ComfyJ" application does not generate the appropriate *Server classes.

However it's still possible to listen to events of application. In fact, all those *Server classes are just the stubs which are derived from IDispatchServer class which also implement the required events interface.

In case of PowerPoint integration such Java COM server class will look like following:

public static class PowerPointEventHandler extends com.jniwrapper.win32.com.server.IDispatchServer implements EApplication {
  ...
}

The EApplicaiton here is the interface designed for handling power point events. We also found that they do not define the ID's of the methods in this interface in regular way. That's why we had to add all those ID's from the IDL file manually, by defining them as constants.

I attached the complete PowerPointEventsHandling.java example that demonstrates how to subscribe to the events of PowerPoint application.

-Serge

I have not seen such issues though I tried it with MS Office 2007. We will investigate this issue tomorrow and let you know the results.

What configuration (version of OS, JDK and ComfyJ) do you run it on?

-Serge

I tested it on Windows Vista with the same JDK and ComFyj version, and the MS Office 2003,  the same things happened.

Thanks,

Cobble S.

That warning message simply indicates that ComfyJ could not find an appropriate EApplicationWithDispVTBL class in order to configure the class factory server automatically in the following constructor:

classFactoryServer = new IClassFactoryServer(PowerPointEventHandler.class);

ComfyJ constructs EApplicationWithDispVTBL class name by concatenation of interface name (EApplicationWithDisp) plus 'VTBL' suffix. Then IClassFactoryServer searches it in the 'server' subpackage, relatively to a location of EApplicationWithDisp interface.

You can simply ignore that message, because the 'classFactoryServer' object is configured by two following lines:

classFactoryServer.registerInterface(EApplicationWithDisp.class, new IDispatchVTBL(classFactoryServer));
classFactoryServer.setDefaultInterface(IDispatch.class);

And the simplest way to aviod that message at all is to move all these DISPID constants directly to the EApplication interface, of course if you do not use a compiled library, for example:

public interface EApplication extends com.jniwrapper.win32.automation.IDispatch {
    final static String INTERFACE_IDENTIFIER = "{914934C2-5A91-11CF-8700-00AA0060263B}";
   
    final static int DISPID_windowSelectionChange = 2001;
    final static int DISPID_windowBeforeRightClick = 2002;
    final static int DISPID_windowBeforeDoubleClick = 2003;
    final static int DISPID_presentationClose = 2004;
    final static int DISPID_presentationSave = 2005;
    ...

-Serge

We were able to reproduce this issue with Office 2003 applicaitons and now we are looking for the solution. The good news that there is no such problem with Office 2007 applicaitons. We'll provide the updated ComfyJ library when this issue is fixed.

-Serge