BUG: JavaTLB Generates Invalid Classes for MFC Server

MORE INFORMATION

Steps to Reproduce Behavior

1. Generate a default MFC AppWizard application, selecting OLE automation support.
2. Add an Automation method (using Class Wizard, OLE Automation tab) that takes a parameter of type "BSTR *" or "long *".
3. Build the MFC project, and run it once to register.
4. From the command-line, run JAVATLB /U:T on the .TLB file for the Server. This creates Java class files with information about the COM interfaces and methods. You need to run JAVATLB from the command-line, because running Java Type Library wizard doesn't list MFC Automation Server's Type Library, from within the IDE.
5. Create a Java project and include the following code to call into OLE server:

         import server.*;    //this is generated by running JAVATLB on the
                               server's .TLB.
   
         class test
         {
           public static void main(String args[])
           {
         System.out.println("\nStarting test...\n");
              IPtrTest ptrTest = (IPtrTest) new PTRTEST();
   
         String[] strParam = new String[1];
         //int[] intParam = new int[1];
         ptrTest.TestBstr(strParam);   //Calling the automation method
         }
         }
   
   					

6. Build the Java code and execute the application.
7. If this is the first time you have run the application, Developer Studio prompts you for the name of the class.
8. This Java code gives the ClassFormatError as soon as it tries to load.