Projects tagged ‘java’, ‘messaging’, and ‘soa’

Mule is an ESB (Enterprise Service Bus) and integration platform. It is a scalable, highly distributable object broker that can seamlessly handle interactions with services and applications using disparate transport and messaging technologies.

Apache Camel is a powerful rule based integration framework which provides a POJO based implementation of the Enterprise Integration Patterns using an extremely powerful fluent API (or declarative Java Domain Specific Language) to configure routing ... [More] and mediation rules. The Domain Specific Language means that Apache Camel can support type-safe smart completion of routing rules in your IDE using regular Java code without huge amounts of XML configuration files; though Xml Configuration inside Spring is also supported. [Less]

PEtALS is the highly distributed Open Source ESB hosted by OW2. PEtALS delivers OW2 JavaTM Business Integration (JBI) platform. PEtALS provides lightweight and packaged integration solutions, based on JSR-208 specifications, with a strong focus on ... [More] distribution and clustering. PEtALS helps you to integrate your Enterprise Business Units in order to provide a value added global solution. By assembling all your enterprise elements, you can provide new applications by re-using some existing ones. Thus, all your applications expose their logic by exposing services. This concept is know as a Service Oriented Architecture (SOA). The project also provides a set of JBI components and a component development kit that will help users to develop their own components. [Less]

JORAM (Java Open Reliable Asynchronous Messaging) is an open source implementation of the JMS (Java Message Service) 1.1 API.

The WSO2 ESB is an ultra fast, light-weight and versatile Enterprise Service Bus based on the Apache Synapse ESB. It allows you to Connect, Manage and Transform service interactions between Web services, REST/POX services and Legacy systems. WSO2 ESB is released under the Apache License v2.0

Apache Synapse is a simple to use, lightweight and high performance Enterprise Service Bus (ESB) from Apache. It can deal with SOAP 1.1/1.2, REST, POX, Plain Text, Binary, Hessian, FIX and other types of messages over non-blocking http/s, JMS ... [More] (1.0/1.1), File systems (s/ftp, CIFS, local, tar/zip/gz..), Mail (POP3, IMAP, SMTP), AMQP, TCP/UDP, XMPP and others. It can also deal with initiating/terminating WS-Addressing, WS-Security and WS-Reliable Messaging Please note that the project has a much longer history than the Ohloh metrics indicate, because of an SVN move. The project started in September 2005, and has had 5 major releases. Refer to: http://people.apache.org/~asankha/synapse/statsvn/ for true code statistics [Less]

GASwerk provides production ready solutions based on proven OpenSource components. Three server assemblies based on Apache Geronimo Application Server are available. Each of them solving a particular problem. - GASwerk SOA Stack is a powerful ... [More] feature-rich SOA assembly for agile businesses that want to bring their IT department closer to their business processes. GASwerk SOA provides an Enterprise Service Bus for connectivity and an business process engine to model all the processes. - GASwerk Spring is focused on developer needs. It provides a Spring framework deployment feature. Equipped with GASwerk Spring, your Geronimo Application Server is able to directly deploy Spring Applications to your server. - GASwerk JMS is a Messaging Cluster based on Javas Messaging Service (JMS). [Less]

JBoss Messaging was designed and built from the ground up and was not based on the JBoss MQ architecture and is 100% JMS Compliant The main new features are related to clustering functionality. JBoss Messaging contains a fully functioning and ... [More] highly scalable clustering implementation. Unlike JBoss MQ, JBoss Messaging does not rely on a "HA Singleton", this was a major drawback in JBoss MQ, where only one JMS server in the cluster was active at any one time, providing a scalability bottleneck. With JBoss Messaging this limitation disappears and all nodes in the cluster can simultaneously host active JMS servers allowing the load to be distributed much more smoothly. [Less]