Problem:

Debugging JPI will different JRE settings is painful because it requires changing the settings in JPI Control Panel and restart the browser. Tool vendors may also find it hard to debug with JPI because of the complication of changing the settings.

Solution:

Provide JRE command line debug option that may be passed to the browser but read by JPI. The idea is to pass any JRE debug option through browser command line that the browser ignores. When JPI startup, it may read the browser command line and determine if the JRE settings need to be changed. Using this scheme, JPI may be configured dynamically with various JRE settings without going through JPI Control Panel.

###@###.### 2001-11-05

I'd like to reopen this RFE to the effect that the _JAVA_OPTIONS
support will also be included into a 1.3.1_0X release.

Justification:

Our ISV, SAP AG, has developed (and is actively shipping) a CRM application
based on the integration of Java components with the MS landscape via
the ActiveX bridge. Up to 1.3.0, they were able to configure the classpath
via the $CLASSPATH varible. In 1.3.1, this is not possible anymore, and
they have no acceptable workaround available. There are many users on the
client side, meaning that for each user the Java plugin settings would need
to be set via the ControlPanel.

SAP is one of Sun's most important ISVs (if not the most important), so if
the effort required to backport the already available fix to 1.3.1_05
(ideally) is acceptable, SAP would very much appreciate this.

###@###.### 2002-06-07