## Supported Standards

### JMS 1.1

JMS 1.1 allows J2EE application components to create, send, receive, and read messages for reliable, loosely coupled communication across distributed systems.

FUSE Message Broker supports the following JMS features:

- Queue- and topic-based messaging

- Persistent and non-persistent messaging

- JMS transactions

- XA transactions

### J2EE 1.4

FUSE Message Broker can be used with your organization's existing J2EE platform architecture. It supports any J2EE application server, such as Geronimo 1.x, JBoss 4.x, WebSphere 6.x or WebLogic 9.x.

The JCA Resource Adapter allows a J2EE application server to efficiently pool connections, control transactions, and manage security for FUSE Message Broker.

### JNDI

Java Naming and Directory Interface (JNDI) enables applications to locate and connect with services, for seamless connectivity to heterogeneous enterprise naming and directory services. Developers rely on the JNDI standard to build directory-enabled applications.

You can set up JNDI in FUSE Message Broker simply by adding a `jndi.properties` file to your classpath.

### AJAX and REST

FUSE Message Broker facilitates integration of existing Internet applications and wireless devices that depend on HTTP. It includes a Representational State Transfer (REST) API that allows you to integrate Asynchronous JavaScript and XML (AJAX) applications into your organization's messaging backbone.