Đang chuẩn bị liên kết để tải về tài liệu:
Building Java Enterprise Applications Volume I: Architecture phần 6

Tham khảo tài liệu 'building java enterprise applications volume i: architecture phần 6', công nghệ thông tin, kỹ thuật lập trình phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả | Building Java Enterprise Applications Volume I Architecture Finally it s time to compile and close up shop on the LDAPManager class and populate your application s data store. 7.2 Checkpoint You are now ready to prepare a client to access your beans and manager and populate the data stores. Before coding this test client ensure that you have all your Java classes set up and ready for use. As this is a book about enterprise applications usually distributed across multiple machines this is not as simple as in a traditional standalone application. Often certain classes are on one server while others are on another server there are backups load-balanced servers fail-over servers and so on. The Forethought application has a fairly simplistic setup all classes are located on a single server. This represents the logical unit which in your own applications may be a single physical server or may be multiple servers. For example you might have entity beans on one server session beans on another your web server on a third and then have multiple machines for backup on top of those. Additionally you will have clients that are presumably separate from the server. I will assume that any clients are physically separate from the server and its code as that is the typical case in enterprise applications. The trick then is getting the right classes on the server for the server to operate and then the right classes on the client to allow access to the server. Server classes are simple for the most part you ll just throw everything on the server. With EJB for example the remote and home interface the primary key class a value class if there is one and the implementation class should all be on the server. The task of setting the client up though is not as simple. In the case of a web client nothing is needed on the client as a simple web browser is used and all program execution occurs on the server. However you aren t quite to that point yet you need a client that can operate upon your