JDK-4413669 : Plug-In converts java.lang.Double to double
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.3.0
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_98
  • CPU: x86
  • Submitted: 2001-02-09
  • Updated: 2002-04-29
  • Resolved: 2002-04-29
Related Reports
Duplicate :  
Description

Name: boT120536			Date: 02/08/2001


java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)

This bug was formerly issued unter No. 115987

The problem is that ActiveX-Bridge always converts java.lang.Double class to
double data type. This is very bad because we have many beans that essentially
need to get/set Double: The beans rely on the NULL information for "there is no
value". For ActiveX-Bridge converts java.lang.*-Wrappers into data types, we
cannot read or set NULL for this methods!

See this source code:

public class theBean implements java.io.Serializable {
  private Double _value = new Double(10.0581);
  public theBean() {
  }
  public Double getDouble() {
    return this._value;
  }
  public void setDouble(Double newValue) {
    this._value = newValue;
  }
}

When I try to access this bean from ActiveX (either C++, VisualBasic or
something else), getDouble delivers double not Double, and setDouble accepts
double but not Double. So I cannot do setDouble(NULL) from inside C++ and I
cannot check if(myInstance.getDouble()==NULL)! This is only with java.lang.*-
Wrappers! Other datatypes work.
(Review ID: 116113) 
======================================================================

Comments
WORK AROUND Name: boT120536 Date: 02/08/2001 There is no known workaround. ======================================================================
11-06-2004

EVALUATION The Active-X Bridge was removed in Java 1.4.0 based on a Java Steering Committee decision nearly 2 years ago. The decision was based on 2 things. Customer interest was marginal at best and Java Plug-in was no longer dependent on the bridge technology to operate. It was necessary to remove it to allow for code refactoring and reworking in 1.4.0. Since removing the bridge, many customers have expressed interest in it. We have filed an RFE (4616580) for this support in a future release. We are currently evaluating whether we have a significant business case to justify the 1-3 man-month engineering effort (more for supporting teams) in the Mantis/Tiger timeframe. NOTE: Mantis = Java 1.4.2 FCS Q2, 2003 Tiger = Java 1.5 FCS Q4, 2003 Support for the bridge in existing 1.3.x releases is limited to escalations and can be persued with our CTE team. This bug will be closed as a duplicate of 4616580. ###@###.### 2002-04-29
29-04-2002