Java Enterprise and Web Technologies

Projectserver.nielsen.com uses Dot Net (Microsoft .NET) technology. This is consistent with Microsoft-based enterprise project management systems. Flex (A) and Silverlight (C) are RIA frameworks, not backend server technologies. JSP (B) is Java-based, while .NET is Microsoft's framework.

Wicket's key benefits are: clean HTML/Java separation (pages are pure XHTML with minimal Wicket tags), automated state management (no manual HTTP session handling), and abstraction from Servlet/HTTP protocol details (developers work with Java components, not HTTP requests directly). Option C describes JSP/taglibs, which Wicket specifically avoids.

Struts is considered outdated because: (A) it's not truly object-oriented - Action classes are HTTP-driven rather than OO-designed; (C) it requires learning JSP and custom taglibs for HTML output. Options B and D incorrectly describe Struts - B mentions hierarchies (not a Struts strength) and D claims it's clean OO (which it is not).

Wicket solves Struts' problems by: (B) being fully object-oriented with component hierarchies, and (C) using pure HTML markup that complies with XHTML standards. Option A describes Struts' problem (Action classes tied to HTTP), and D describes Struts' architecture (not Wicket's).

Wicket explicitly abstracts away Servlet API and HTTP protocol details. Developers work with Java components and models, while Wicket handles HTTP requests, sessions, and parameters behind the scenes. The statement claims Wicket does NOT hide these details, which is false.

With Apache Wicket, developers get the benefits of Ajax functionality (partial page updates, dynamic content refresh) without writing raw JavaScript code. Wicket's Ajax-enabled components handle all the complex Ajax plumbing behind the scenes while you work with just Java and HTML. The correct answer is Ajax.

WSDL (Web Services Description Language) is an XML-based language used to describe the public interface, operations, parameters, and access endpoints of a web service. SOAP is the protocol used to call them, and UDDI is used for discovery.

Apache Axis is primarily a tool for generating web services from Java classes (B) and for generating web service stubs/proxies (C). While Axis can work with web services (A), describing it as 'a web service' is not its primary definition - it's a framework/tool for creating and consuming web services. Option D 'All of the above' is incorrect because A is misleadingly worded.

WSDL (Web Services Description Language) is an XML-based language that describes the interface, operations, parameters, and location of a web service. It enables clients to understand how to invoke the service. The other options are not standard web service acronyms.

Hibernate configuration is typically defined using programmatic mapping files and XML configuration files like hibernate.cfg.xml. Config files like http.conf (Apache Web Server) and web.config (ASP.NET) are completely unrelated to Hibernate.

Hibernate Session objects are explicitly designed to be non-threadsafe. Each thread should have its own Session instance to prevent race conditions and data corruption. The Session is lightweight but must not be shared across threads.

Configuration, Session, Query, and Criteria are core Hibernate interfaces used to establish settings, manage database connections, and run queries. The User interface is not part of Hibernate's core framework APIs.

The Hibernate Session interface wraps a JDBC connection and provides methods for CRUD operations. It also holds a first-level cache and is created by SessionFactory (not during application initialization - that's when SessionFactory is created). The Session itself does not act as a factory.

The Intercepting Filter pattern in Java EE is implemented by implementing the javax.servlet.Filter interface. This interface defines methods like init(), doFilter(), and destroy() that allow pre/post-processing of requests and responses. FilterChain and FilterConfig are supporting interfaces used by filters but are not the primary interface to implement.

The Front Controller pattern is implemented by creating a servlet that implements the javax.servlet.Servlet interface (typically by extending HttpServlet). The servlet acts as a centralized entry point for all requests. ServletConfig and ServletContext are interfaces for configuration and context access, not for implementing the controller itself.