What is the difference between javabean with widgets?
JavaBean defines a design time interface that allows the application design tool or constructor to query the component to understand the type of attribute defined by the component, the type of event type or the response type.
In visualized application constructors, Beans are sometimes seen as reusable software components or customizable controls. Software components such as JavaBeans are different from the standard Windows control or Motif Widgets. They encapsulate design time information (attributes and methods) that allows the build tool to understand their capabilities.
In addition, end users or third-party software vendors, can be independent of the GUI platform or operating system when customizing Beans. The IS department can distribute these third-party software components to their enterprise's internal customers, or you can sell these components as additional components to any people intend to use constructors to create applications.
What is the difference between JavaBean with the Java class?
Any Java class that conforms to a certain attribute and an event interface definition can be a JavaBean. The bean is a Java class that can be operated in a visual constructor, and these Java classes can be placed in the application.
Self-test is how to analyze Bean how to work, it can distinguish Bean from a typical Java class. Since Bean is encoded with a predefined mode, the definition of the method and class can be encoded, so that the software tool that can identify these modes can analyze the beans and can set their properties and behavior.
The self-test allows the bean to set the status setting in the design phase, that is, when installed as a component to a large application. In order to achieve this goal, the BEAN's method format must be carried out in some mode so that the self-test tool recognizes the Bean in the design phase and the run phase.
In fact, the bean publishes its properties and behaviors through specific modes in their methods, which can be identified by application constructive tools corresponding to Beans. Despite this, these constructors are not used to construct or test your bean. These specific modes can be easily identified by allowing the constructor to identify. When constructing Bean, you first know one of things is how to identify and construct methods that meet these modes.
Bean is not suitable for use, and they are most suitable for use as software components, which can be visualized in the construction tool. Functions such as JDBCTM API are still optimally provided by programming program interfaces or text interfaces, not suitable for providing by visual interfaces.
