Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Other editions.

Author:Dakinos Nerisar
Language:English (Spanish)
Genre:Health and Food
Published (Last):16 January 2017
PDF File Size:12.9 Mb
ePub File Size:8.77 Mb
Price:Free* [*Free Regsitration Required]

Thinking in Enterprise Java by Bruce Eckel et. Note : This document requires the installation of the fonts Georgia, Verdana and Andale Mono code font for proper viewing. Identifying a machine. A simple server and client Serving multiple clients. Using URLs from within an applet. More to networking. Remote interfaces. Implementing the remote interface.

Creating stubs and skeletons. Using the remote object. Getting the example to work. A GUI version of the lookup program.. A more sophisticated example. The basic servlet. Servlets and multithreading. Handling sessions with servlets. Running the servlet examples. Implicit objects. JSP directives. JSP scripting elements. Extracting fields and values. JSP page attributes and scope. Manipulating sessions in JSP.

Creating and modifying cookies. JSP summary. What do custom tags give us? Using Tags and JavaBeans. Tags that manipulate their body content. Tags that iterate. Tags within Tags. The Tag Classes. Using TagExtraInfo classes. Tag Library Descriptors Revisited. Deploying Tag Libraries. Using Third Party Tag Libraries. Enterprise JavaBean Flavors. EJB Roles. The Basic APIs. JNDI EJB Container internals. The example application. Your first Enterprise JavaBean.

Home Interface. Component Interface. Primary Key. Implementation Class. Deployment Descriptor. Building it all An EJB client application.

Simplifying EJB Development Implementing a session bean. EJB Local Interfaces. Bulk accessors and value objects. Entity Relationships. What is XML? XML Elements. XML Attributes. Character Sets. XML Technologies. XML Namespaces. XML Serialization. Xerces Serialization. DOM Level 3 Serialization. XML Transformations. The Root Node. XLink and XPointer. Historically, programming across multiple machines has been error-prone, difficult, and complex.

The programmer had to know many details about the network and sometimes even the hardware. It was a daunting task. However, the basic idea of distributed computing is not so difficult, and is abstracted very nicely in the Java libraries. You want to:. This is accomplished with basic network programming. This is accomplished with Java DataBase Connectivity JDBC , which is an abstraction away from the messy, platform-specific details of SQL the structured query language used for most database transactions.

EJBs are not actually a distributed architecture, but the resulting applications are usually used in a networked client-server system. Please note that each subject is voluminous and by itself the subject of entire books, so this book is only meant to familiarize you with the topics, not make you an expert however, you can go a long way with the information presented here. This book assumes you have read and understood most of Thinking in Java, 3rd Edition Prentice-Hall, , available for download at www.

The goal of J2EE is to create a set of tools that allows the Java developer to build server-based applications more quickly than before, and in a platform-independent way. J2EE provides a framework to assist in creating server-based applications; these applications are in demand now, and that demand appears to be increasing.

As much as possible, the underlying details of networking have been abstracted away and taken care of within the JVM and local machine installation of Java. Of course, in order to tell one machine from another and to make sure that you are connected with a particular machine, there must be some way of uniquely identifying machines on a network.

Early networks were satisfied to provide unique names for machines within the local network. However, Java works within the Internet, which requires a way to uniquely identify a machine from all the others in the world. My domain name is bruceeckel. This is exactly the kind of name that you use when you send email to people, and is often incorporated into a World Wide Web address.

In both cases, the IP address is represented internally as a bit number [1] so each of the quad numbers cannot exceed , and you can get a special Java object to represent this number from either of the forms above by using the static InetAddress. As a simple example of using InetAddress.

Each time you dial up, you are assigned a temporary IP address. If someone connects to your machine using your IP address then they can connect to a Web server or FTP server that you have running on your machine. Of course, they need to know your IP address, and since a new one is assigned each time you dial up, how can you find out what it is?

The following program uses InetAddress. To use it, you must know the name of your computer. The whole point of a network is to allow two machines to connect and talk to each other. Once the two machines have found each other they can have a nice, two-way conversation. But how do they find each other? This distinction is important only while the client is trying to connect to the server. The job of the client is to try to make a connection to a server, and this is performed by the special client object you create.

This is one of the nice features of Java networking. For many reasons, you might not have a client machine, a server machine, and a network available to test your programs.


Bruce Eckel's Programming Books



Thinking in Enterprise Java






Related Articles