Projects tagged ‘java’, ‘jms’, and ‘middleware’


Jump to tag:

Projects tagged ‘java’, ‘jms’, and ‘middleware’

Filtered by Project Tags java jms middleware

Refine results Project Tags soa (7) enterprise (6) j2ee (6) messaging (6) interoperable (5) xml (5) javaee (5) jee (5) soap (4) integration (4) webservice (4) ws-security (4)

[10 total ]

159USERS
   

JBoss Application Server is the #1 most widely used Java application server on the market. A J2EE certified platform for developing and deploying enterprise Java applications, Web applications, and Portals, JBoss Application Server provides the full ... [More] range of J2EE 1.4 features as well as extended enterprise services including clustering, caching, and persistence. [Less]

31USERS
   

Apache CXF simplifies the construction, integration, and flexible reuse of technical and business components using a standards-based, service-oriented architecture (SOA). CXF is a merger of two prior OSS projects - Celtix ObjectWeb and XFire ... [More] projects. CXF support JAX-WS, RESTful and POJO for the building Web Services. CXF support SOAP, JMS, CORBA and more. [Less]

25USERS
   

The goal of the Geronimo project is to produce a server runtime framework that pulls together the best Open Source alternatives to create runtimes that meet the needs of developers and system administrators. Geronimo 2.0 is a fully certified Java EE ... [More] 5 application server runtime. Websphere Application Server Community Edition from IBM is based on this code. [Less]

16USERS
   

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]

14USERS
 

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]

13USERS
 

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

5USERS

JBoss Web Services Framework

3USERS
 

Create Web Services with PHP5 in minutes. InstantSVC (pronounced as Instant Services) provides a set of tools to ease your development. You just need to document your object oriented PHP code with PHPDocumentor in order to generate Web Services from ... [More] it - SOAP Services as well as RESTful Web Services. Features of InstantSVC include an Extended Reflection API with information about data types, Annotations for PHP, a WSDL generator conform to WS-I Basic Profile, a Document/literal adapter generator, a Handler chain mechanism for SOAP processing, Implementations of WS-Security and the Username Token Profile, a Server for RESTful Web Services and an Administration tool for convenient creation and management of SOAP and REST servers. [Less]

3USERS
   

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]

1USERS

This is a connector 1.5 resource adapter that helps integrating JMS compliant message providers with J2EE 1.4 compliant application servers such as Sun Java System Application Server