Exam questions

1. What is Enterprise JavaBeans(EJB)?

An EJB is a specialized, non-visual JavaBean that runs on a server. It extends JavaBeans Component Model for Mission Critical Transaction Systems, Endorsed by Leading Enterprise Vendors. It is an API specification for building scalable, distributed, component-based, multi-tier applications.
(please refer to Overview of Enterprise JavaBeans)

2. What is JavaBeans?

Java Beans are Javasoft’s approach to component oriented software development, that is making it possible to develop software components that relatively easily can be assembled into an application by an enduser or programmer.
(please refer to Overview of JavaBeans)

3. Name few things what BeanBox can do?

Edit the exported properties of a bean.
Run a customizer to configure a bean.
connect a bean event  source to an event handler method.
connect together bound properties on different beans.
make applets from beans.
get an introspection report on a bean.
add new beans from JAR file.
(please refer to BeanBox)

4. What is difference between ActiveX and JavaBeans?

ActiveX is not a cross-platform solution, Java Bean is Platform independent.
ActiveX is heavyweight, Java Bean is lightweight.
ActiveX is Complex and Costly, JavaBean is Simple and Cost Effective.
(please refer to Javabeans and ActiveX)

5. What are the 3 major features of the JavaBean API?

Properties, event and methods. 
Properties are attributes of the beans internal state.  
Events are dispatched to appropriate listeners. 
Methods are implemented much like core Java.
(please refer to JavaBeans API)

6. What is signed applets?

A signed applet is an applet that is loaded from a source that you consider as trusted. A signed applet has fewer restrictons in accessing the file system, network ports or other resources in the client.                                   
(please refer to Security and Javabeans)

7. Why do we need signed applets?

Signed applets are useful when you want to remove some of the security mechanisms that are used by web browsers for applets. The security manager provided for applets is more strict than when you run your Java programs standalone on the client as applications loaded from the file system of the client. The Java virtual Machine will, by default, not let you load your applet from one Web server and let it connect to another server. this is a feature you might miss when using database servers, transaction servers and so on. You do not want to be forced to run a transaction or database server on the same physical machine as your Web server just to bypass that restriction with applets. You might also want to be able to read or write files on the local disk of the client. This is not permitted for a standard applet, but by making the applet signed, you will be able to do it.
(please refer to Security and Javabeans)