ActiveX is Microsoft's component-based software framwork, JavaBean is component software architecture from Java Platform. Both ActiveX and JavaBeans can be used for Internet/intranet development to bring to the Web. Since we learned ActiveX in our class, it is interesting to take a look at the comparion of these two products. The following table is from JAVABEANSTM AND ACTIVEX
JavaBeans and ActiveX
JavaBeans
ActiveX
1. Platform
Yes JavaBeans is operating system-independent:
NoActiveX APIs are specific to each platform.
Neutral
"Write Once, Run Anywhere",Reuse Everywhere.
Ports to platforms other than Win32 still will not provide
And JavaBeans are ready to use today.
"Write Once, Run Anywhere", Reuse Everywhere capabilities.
2. Ubiquitous
Yes The JavaBeans framework is available on any
No Again, ActiveX is platform-and desktop-specific.
system hosting a Java Virtual Machine - from
desktops to network computers to embedded devices.
3. Clean
Yes The component and registration discovery mechanisms
NoWhen building ActiveX components, developers
Integration
of JavaBeans are integrated into the Java platform. Developers
must invest development resources in both ActiveX and the
need only invest development resources in a single
development language used to deliver solutions.
technology to deliver solutions.
4. Interoperability
Built-in The JavaBeans Bridge for ActiveX, from
Needs JavaBeans ActiveX Bridge
Sun, is provided with JavaBeans API suite.
The only way to integrate JavaBeans into ActiveX
It integrates JavaBeans into ActiveX containers.
containers is with the JavaBeans Bridge for ActiveX,
from JavaSoft - which is provided with
the JavaBeans API suite.
5. Lightweight
Yes JavaBeans are lightweight so they can run efficiently
No Heavyweight applications must be invoked to
on network computers and embedded devices, yet can
serve as a container for the ActiveX component.
scale to robust desktop solutions.
6. Network
Extensive JavaBeans is ideal for an extensive
Limited Based on an older desktop application
Device
range of systems, from mainframes to desktops to
technology, ActiveX is not designed for use on thin
Support
embedded devices.
clients.
7. Software
Simple and Cost Effective Because
Complex and Costly Developers must
Versioning
JavaBeans is platform independent, developers need
maintain separate versions of each ActiveX component
and Distribution
to maintain just one version of a JavaBeans component.
for each target hardware platform - even if the operating
system remains the same.
8. Communications
Extensive Through CORBA & RMI
Limited by DCOM DCOM is a closed
JavaBeans components have the flexibility to communicate
technology that does not support industry standards,
with network objects via CORBA or RMI, so they can access
so links to CORBA-based applications are not possible.
components regardless of language or platform.
This limits the utility of ActiveX within the enterprise.
9. Performance
ConsistentLeveraging the unique advantages
Uncertain Designed for high performance on
of the Java language, JavaBeans provide consistently
Win32 platforms, the performance of ActiveX ports to
efficient, platform-neutral performance.
other platforms is not yet known.
10. Security
Multiple Levels Java and the JavaBeans
Signed Components Only The ActiveX
architecture meet the security requirements of Internet-based
approach to security is incomplete - signed components
applications via Java's highly customizable security model.
alone cannot block viruses or other malicious applications.
References:
The JavaBeans Bridge for ActiveX
JavaBeans and ActiveX go head to head
Java 1.1 Third Edition by Michael Morrison, er al.