Both ActiveX and JavaBeans (from Microsoft and JavaSoft, respectively) can be used for Internet/intranet development, as we found out in last month's strategic analysis, but these two component frameworks are broadly different in scope. How do you know which is right for you? In this article I answer to the fundamental technical questions crucial to developers -- "How do they work?" "What can they do?" "Which is right for you?" -- so you determine which component object model best suits your needs. To top it off, I include in the In practice section a close look (complete with scores!) at how well each performs in five critical areas: availability, capability, security, interoperability, and cross- platformability.
Are you ready? Let's talk turkey. (March 1997, 4,200 words)
JavaBeans, the important new component software model from Sun, introduces the rapid applications development methodology to Java and presents a standard framework for the development of reusable software components. In this, the conclusion of our two-part mini-series, we finish the development of our suite of beans by looking at constructing beans from other beans. We also examine a simple application written using these components that further demonstrates software use of JavaBeans. Along the way, we'll encounter more beans, observable properties, inner classes, and programmatic access to JavaBeans components. (September 1997, 4,800 words)
Both ActiveX and JavaBeans (from Microsoft and JavaSoft, respectively) can be used for Internet/intranet development, as we found out in last month's strategic analysis, but these two component frameworks are broadly different in scope. How do you know which is right for you? In this article I answer to the fundamental technical questions crucial to developers -- "How do they work?" "What can they do?" "Which is right for you?" -- so you determine which component object model best suits your needs. To top it off, I include in the In practice section a close look (complete with scores!) at how well each performs in five critical areas: availability, capability, security, interoperability, and cross- platformability.
Are you ready? Let's talk turkey. (March 1997, 4,200 words)