Java Enterprise and Web Technologies

jBPM (JBoss Business Process Management) is the default BPM tool for JBoss ESB, providing workflow automation and process management capabilities. It's part of the JBoss community project and integrates seamlessly with JBoss ESB.

IBM WebSphere is a proprietary commercial portal and application server platform requiring licensing fees. JBoss and Liferay are both open-source portal solutions with community and enterprise editions.

All statements about Liferay are true: it is open source, based on Java and Web 2.0, and built on CMS and collaboration tools. Therefore 'None of the above' (meaning none are false) is correct.

jBPM was originally created by Tom Baeyens as an open-source project before being acquired by JBoss. JBoss itself was later acquired by Red Hat in 2006. Red Hat currently manages and develops the project as part of its middleware portfolio.

WSO2 ESB is built on Apache Axis2 as its underlying Web Services framework. Axis2 provides the core messaging and SOAP processing capabilities that power WSO2's integration middleware.

Fuse ESB (part of Apache ServiceMix) uses Eclipse Equinox as its default OSGi container implementation. This is a well-documented architectural choice in the Fuse ESB documentation. Apache Felix and Apache Aries are alternative OSGi implementations but not the default for Fuse.

JBOSS ESB 4.x was officially tested and certified against JBOSS AS 4.2.3 GA and 5.1.0 GA application servers. These are the documented compatibility targets in JBOSS ESB 4.x release notes. Version 6.0.0 and JBOSS 7 (which introduced modular classloading) came later and are not supported for ESB 4.x.

WSO2 ESB is built on Apache Synapse, a lightweight and high-performance ESB framework that provides the core mediation and routing capabilities. This architectural choice is fundamental to WSO2 ESB's design. Apache ServiceMix is a separate ESB project (JBI-based), and Open ESB is another distinct implementation.

FUSE ESB supports multiple integration standards including JBI (Java Business Integration), JMS (Java Message Service), JCA (Java Connector Architecture), and JMX (Java Management Extensions). Since the question asks which standards are supported and all listed options are valid standards that FUSE ESB implements, 'All of the above' is the correct comprehensive answer.

Fuse ESB is based on Apache ServiceMix and supports a wide range of enterprise standards including Java Business Integration (JBI), JMS for messaging, JCA for resource adapters, and JMX for management.

Fuse ESB uses Apache Camel as its framework for implementing Enterprise Integration Patterns (EIP). Apache Camel provides a powerful routing and mediation engine with support for numerous integration patterns. The other animal names (Deer, Crocodile, Zebra, Elephant) are fictional distractors.

JBoss ESB supports SOAP for web services, JEE for enterprise Java integration, and UDDI for service registry and discovery. These standards form the core interoperability framework of the ESB. JBI (Java Business Integration) and SCA (Service Component Architecture) are separate integration specifications not primarily supported by JBoss ESB.

Mule ESB supports Apache Maven out of the box through Mule Maven plugins and archetypes, making it easy to build, package, and deploy Mule applications. Maven is the standard build tool for Mule projects. Apache Ant is supported but not the primary out-of-the-box mechanism. Hudson, IVY, and Continuum are not Mule's core build tools.

Joomla originated from Mambo CMS in 2005 when the development team forked the project due to disagreements with the copyright holder. Mambo subsequently declined and became deprecated while Joomla flourished.

jBPM encompasses all three aspects: it's a Java framework using Hibernate for persistence, represents business processes as graphs (BPMN/jPDL), and functions as a workflow engine for process automation.