javabean（Java组件）.docVIP

javabean（Java组件） JavaBean and EJB differ You may now be in the use of JavaBean, but also do not understand it. If there is a browser that supports Java, then use JavaBean on the desktop is not restricted. Use the Web page to bean as part of a small application. You will soon as part of the JavaBean browser and visual interaction, then the JavaBean will interface with the EJB server. This ability can also be extended to the Internet and intranet. JavaBean and Server Bean (commonly known as Enterprise JavaBean (EJB)) have some basic similarities. They are created with a set of properties to objects or components to perform their specific tasks. They have the ability from the current container resides on the server to obtain other characteristics. This makes according to specific tasks and the different behavior of bean. This opens up huge opportunities. Because JavaBean is platform independent, so for the solution of the future, the supplier can easily to different users to launch its client side JavaBean, without having to create or maintain different versions. These JavaBean can be with the implementation of business functions (such as ordering, credit card processing, electronic remittance, inventory allocation, transportation etc.) with the use of EJB. There is a huge potential, which is the component agent (WebSphere Application Server Enterprise Edition) that is designed to provide the potential. JavaBean is a component, it is in the internal interface or related attributes, so that different people in different time can be developed and integrated to ask bean. You can build a bean, but after the construction of the bean and other binding. This process provides the first construction method and then reused, this concept is a component of the. This can be a single application deployment into independent procedures, ActiveX components or in the browser. JavaBean because of its external interface (i.e. attribute interface) is different from pure objects. This inter