Hi Yashawant
JavaBeans
1.JavaBeans may be visible or non-visible at runtime. For example, the visual GUI component may be a button, list box, graphic, or a chart
2.JavaBeans are intended to be local to a single process and are primarily intended to run on the client side. Although one can develop server-side JavaBeans, it is far easier to develop them using the
EJB specification instead.
3.JavaBeans is a component technology to create generic Java components that can be composed together into
applets and applications.
4.JavaBeans have an external interface called the Properties interface, which allows a builder tool to interpret the functionality of the bean.
5.JavaBeans may have BeanInfo classes, property editors, or customizers.
6.JavaBeans are not typed.
7.No explicit support exists for transactions in JavaBeans.
8.Component bridges are available for JavaBeans. For example, a JavaBean can also be deployed as an ActiveX control.
EJB
1.An EJB is a non-visual, remote object.
2.EJBs are remotely executable components or business objects that can be deployed only on the server.
3.Even though EJB is a component technology, it neither builds upon nor extends the original JavaBean specification.
4.EJBs have a deployment descriptor that describes its functionality to an external builder tool or
IDE.
5.EJBs have no concept of BeanInfo classes, property editors ,or customizers and provide no additional information other than that described in the deployment descriptor.
6.EJBs are of two types�session beans and entity beans.
7.EJBs may be transactional and the EJB Servers provide transactional support.
8.An EJB cannot be deployed as an ActiveX control because ActiveX controls are intended to run at the desktop and EJBs are server side components. However, CORBA-IIOP compatibility via the EJB-to-CORBA mapping is defined by the OMG.
Regards