###@###.### 2003-02-06

J2SE Version (please include all output from java -version flag):
  java version "1.4.2-beta"
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-beta-b14)
  Java HotSpot(TM) Client VM (build 1.4.2-beta-b14, mixed mode)

Does this problem occur on J2SE 1.3, 1.4 or 1.4.1?
  No

Operating System Configuration Information (be specific):
  Microsoft Windows 2000 [Version 5.00.2195]
  Service Pack 3
  Latest Security Patches

Hardware Configuration Information (be specific):
  Standard PC (320MB RAM, P3-450)
  ATI RAGE PRO TURBO AGP 2X

Bug Description:

  ActiveX Documentation is not good enough by far.
  Should be improved to include much more examples for every step and option.
  Should not only include simple things but also complex stuff, as e. g.
  how to handle that multiply overloaded methods.

  Here are some problems we have with your current docs:

  1) How to create a JavaObject from C++ and pass it as a parameter to
     the ActiveX's method foo(Object x)?

  2) Why have to deploy to that JRE\axbridge\bin directory? might want Bean
     located within own app dir instead.

  3) Why should not use -reg when -out is pointing to C:\MyAppDir?

  4) For what is the -clsid switch? When to use it, when not to? What happens
     if omitted? What happens if used?

  5) Docs tell that the full path to the JAR has to be given. That's wrong.
     The packager accepts relative paths, e. g. ..\x\myJar.jar

  6) Docs includes samples where <jre_home> is set to C:\j2re1.4.2. Actually
     the JRE is installed to C:\Program Files\Java and not C:\ This is very
     confusing.

  7) Docs do not tell that the C:\Program Files\Java\j2re1.4.2 is to be used
     but not C:\j2sdk1.4.2\jre. This is very confusing.

  8) Docs tell that lib directory is created when using regsvr32, but do not
     tell so when using -reg switch with packager. Indeed this also creates
     the lib and copies the dll into it. This should be told to not confuse
     the user.

  9) When having registered a packaged activex and changing that bean's
     interface after that, you need to package again. This is missing in
     the docs.

  10) When doing what (9) tells (changing a bean after registration), then
      the packager has to be called with -clsid and the class id that was used
      last time. This is not missing in the doc. Also the docs should tell how
      I can query the classid that the packager used when not specified -clsid.

  11) When removing an installed activex from the user's machine, the bean has
      to be unregistered with regsvr -u. This is not told in the doc.