Apache Tomcat and Web Services

WSDL defines five valid SOAP binding style/use combinations. Document/literal and RPC/literal are WS-I compliant and recommended. RPC/encoded was common in early SOAP but is now deprecated. Document/encoded is technically valid though rarely used. RPC/document is not a standard WSDL combination.

According to SOAP specification, a Fault element must appear within the Body element of the SOAP message. It cannot be in Header, Envelope (the root), or be a root element itself. The Fault element carries error or fault information from the endpoint.

SAAJ stands for SOAP with Attachments API for Java. It's a Java API for creating and sending SOAP messages with attachments. The other options are fabricated: Simple Access, Serial Access, and Sun Access are not real Java API names.

SAAJ messages can use the Java Messaging Service (JMS) or other routing mechanisms to reach multiple destinations. A single SOAP message created with SAAJ can be sent to multiple endpoints, supporting publish-subscribe or multicast patterns.

SOAP messages MUST use the SOAP Envelope namespace (xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/') as it defines the message structure. They MUST NOT contain DTD references because SOAP is designed to work with XML parsers that may not validate against DTDs. SOAP Encoding namespace is optional (used with rpc/encoded style).

The Web Services architecture stack consists of five key layers: Discovery (UDDI for finding services), Description (WSDL for defining service interface), Packaging (SOAP for message formatting), Transport (HTTP/SMTP for message transmission), and Network (TCP/IP for underlying connectivity). All these layers work together to enable service-oriented architecture.

In the Web Services conceptual stack, SOAP (Simple Object Access Protocol) is categorized in the Packaging or Messaging layer. It defines the XML structure (Envelope, Header, Body) used to wrap the data. Transport refers to protocols like HTTP, while Discovery refers to UDDI.

James Duncan Davidson created Tomcat while working at Sun Microsystems. Bjarne Stroustrup created C++, Ben Kingsley is an actor, and Keith Fletcher is not the Tomcat inventor.

AJP (Apache JServ Protocol) is the wire protocol enabling communication between Apache web server and Tomcat. HTTP is for web communication, FTP for file transfer, and AJAX for asynchronous web updates.

Tomcat is primarily a Servlet Container and JSP engine. It is not a full EJB server (which requires Java EE application server like JBoss), not a complete J2EE server, and certainly not 'nothing'.

Apache Software Foundation develops and maintains Tomcat as an open-source project. IEEE is a professional association, AT&T Bell Labs is a research facility, and Microsoft is a separate company.

$CATALINA_HOME is the environment variable that points to the Tomcat installation directory, which serves as the root directory for the Tomcat server. $BIN, $ROOT, and $CONF are not standard Tomcat environment variables for the root directory.

Session Persistence specifically refers to the mechanism of saving HTTP session data to disk when a server shuts down and reloading it when the server restarts. This ensures that user sessions survive server restarts without losing data. Persistence and Server Persistence are too general, while Streaming relates to data transfer, not session storage.

JNDI (Java Naming and Directory Interface) is the API and service that Tomcat uses to provide access to resources like databases, connection pools, and JavaMail sessions through a naming context. Naming Lookup is too vague, Class Loader is for Java classes, and Buffering is for I/O operations.

Apache Tomcat is a web server and servlet container that implements several Java EE specifications, providing robust server-side capabilities for running Java servlets and JSPs.

CGI (Common Gateway Interface) is the standard protocol for web servers to execute external programs that generate web content dynamically, typically processing form data. CORBA is for distributed objects, IIS Server is a Microsoft web server product, and Java Servlets are Java-based server-side programs (not external programs in the CGI sense).

The Admin web application is configured through an XML descriptor file located at CATALINA_BASE/webapps/admin.xml. This follows the standard Tomcat deployment descriptor pattern where configuration is in XML files, not HTML files. The CATALINA_BASE path is used for instance-specific configurations.

SSL (Secure Socket Layer) is the protocol Tomcat supports for encrypting data transmitted over the network. SSL and its successor TLS provide the encryption layer for secure HTTPS connections. TCP/IP is the underlying transport protocol, PKI is the infrastructure for managing keys, and HTTPS is the application-level protocol that uses SSL/TLS.