Java Enterprise and Web Technologies

A session bean is not shared, it means that it may have just one client.

It extends javax.ejb.EJBHome, which in turn extends java.rmi.Remote.

The enterprise java beans architecture will address the development, deployment and runtime aspects of an enterprise application's life cycle.

It is responsible for mapping the security roles defined by the application assembler to the user groups and accounts that exist in the operational environment in which the enterprise beans are deployed.

When a client invokes the method of a stateless bean, the bean's instance variables may contain a state, but only for the duration of the invocation.

This is the correct option because destroy() method is invoked when browser exits normally to inform the applet that is no longer needed and should release any recourses allocated.So this is the correct method. Hence this is correct choice according to the question asked.

The FBEAN package is Oracle Forms' built-in interface for communicating with JavaBeans. It provides PL/SQL built-ins to register JavaBeans, set/get properties, and invoke methods. Using FBEAN eliminates the need to write custom Java wrapper code or implement custom integration layers - it's the standard, supported mechanism for Forms-JavaBean interaction.

JAVA EE contains JDBC,Servlets,JSP, etc.

Tomcat maintains only a single instance of each JSP page in memory at any given time. This single instance is then used to serve multiple requests concurrently through different threads, ensuring memory efficiency while handling simultaneous users.

Tomcat executes JSP pages using threads from its thread pool rather than spawning separate processes or using CGI. When a JSP is requested, Tomcat uses one of its worker threads to execute the compiled servlet (which is what a JSP becomes after compilation), making it much more efficient than CGI scripts or separate processes.

JSP pages are translated into Java servlets by the JSP container. The servlet is then compiled into bytecode and executed by the server. This transformation happens automatically the first time the JSP is accessed or when it's modified. Options A is incorrect because applets run on the client side, not the server.

JSP uses Java as its primary server-side scripting language. While JavaScript may appear in client-side code within JSP pages, the server-side scriptlets and expressions must be written in Java. Options A and B are Microsoft technologies not used in JSP, and D is incorrect because JSP does not support VBScript or JScript.

Apache Tomcat is the servlet container developed jointly by Apache Foundation and Sun Microsystems (now Oracle). It implements Java servlet and JSP specifications. The Apache Web server (option B) serves static content and is not a servlet processor, and there is no official 'Sun servlet processor' product.

Java servlets run on the web server and respond to HTTP requests. They are the server-side counterpart to applets. Option A is incorrect because standalone Java applications aren't invoked via HTTP, and B is wrong because applets run client-side in browsers, not on servers.