Java Enterprise and Web Technologies

The URL Rewrite module allows administrators to create powerful rules using regular expressions and wildcards to transform complex URLs into clean, user-friendly, and SEO-optimized URLs without changing the underlying application structure.

WCF's default instancing mode is PerCall, where a new service object is created for each operation invocation and disposed after the response. This provides better scalability and statelessness unless another mode (PerSession or Single) is explicitly configured.

WSDL (Web Services Description Language) is an XML-based format used to define the methods, parameters, and access points of a web service. SOAP is the protocol used to call these services, and UDDI is the registry directory for discovering them, making the other options incorrect.

Web services advantages: (A) Open Standards - XML/SOAP are W3C standards, (B) Secure - CAN be secured with WS-Security/HTTPS, (C) Text-based - XML is human-readable, but security isn't automatic. 'All of them' is wrong because security requires additional configuration.

Axis is Apache's tool for web services in Java: (B) Generates services from Java classes (bottom-up), (C) Generates stubs/proxies from WSDL (top-down). It's NOT the service itself (A) and not a single 'all-in-one' tool (D) - it handles generation and deployment.

Hibernate mapping files can be configured both programmatically by adding them to the Configuration object in application code, and declaratively by using elements in hibernate.cfg.xml. Both approaches are valid and can be used together, giving developers flexibility in their configuration approach.

The SAP XI (Exchange Infrastructure) Adapter Engine is built on the J2EE (Java 2 Enterprise Edition) platform, which provides the runtime environment for Java-based adapters and cross-system communication. ABAP is SAP's proprietary language, .NET is Microsoft's framework, and JCA is a connector architecture - none serve as XI's foundational engine.

Java Web Start (JNLP) enables deploying and caching Java applications from the web, allowing users to launch full-featured Java applications with a single click while maintaining local copies for offline use. It's not for writing code, executing mappings, or JMS connectivity - those are separate Java technologies.

Java Mapping in SAP XI/PI requires implementing com.sap.aii.mapping.api.StreamTransformation interface, which defines the execute() method for transformation logic and setParameter() for runtime configuration. Options A, B, and C have incorrect package hierarchies - 'aii' (Application Integration Infrastructure) is required.

Hibernate supports BOTH configuration methods: programmatically adding mapping files via Configuration.addResource() or configuring them in hibernate.cfg.xml using elements. Both approaches are valid.

HQL (Hibernate Query Language) is executed using session.createQuery(), which takes an HQL string and returns a Query object. Option B uses Criteria API (not HQL). Option C creates native SQL queries. Option D is not a valid Hibernate method.

Hibernate does NOT require persistent classes to implement Serializable. Serializable is only needed if you want to store objects in HttpSession or replicate them across a clustered cache. Plain POJOs can be persisted without implementing Serializable. Option A is incorrect.

In Android, a ContentProvider is the standard component designed to securely share and expose an application's private data to other applications. Central Provider and Data Provider are incorrect terminology and do not exist in the Android SDK components.