Download JAR files tagged by synchronous with all dependencies

The eAudit4j library provides a simple and pluggable solution for auditing in Java. This library uses the concept of "audit streams", with a stream being comprised of one or more "audit processors". An application can configure an unlimited number of audit streams, each with a different configuration. When an application wants to audit an event, it will create and populate an "Event" instance, and then submit the event to the audit stream for processing and persitance. Depending on the audit stream configuration and the processors being used in the audit stream configuration, processing my be synchronous or asynchronous, and utilize different security features.

Spring AMQP is framework that makes it easy to write Java applications for the Advanced Message Queue Protocol. It supports a variety of common high-level messaging patterns, like synchronous and asynchronous consumers, synchronous producers, automatic re-connection, transactions, batching. The emphasis is on declarative configuration and a POJO programming model without hiding the full power of the underlying protocol.

Bundle with a synchronous activator which will install OGEMA resources from XML (.ogx) or JSON (.ogj) files located in config/resources (default). This requires a running OGEMA framework when the bundle is started and enables the installation of basic resources before other applications are activated. Also adds a service for felix fileinstall that will install such resource files. Files installed through fileinstall will be reinstalled when they are updated or when a newer version of an installed file is found after a restart (using the file's last modification timestamp). Files installed from the configuration directory will only be reinstalled on a restart, if they have been changed.

Axis2 is an effort to re-design and totally re-implement both Axis/Java and (eventually) Axis/C++ on a new architecture. Evolving from the now standard "handler chain" model which Axis1 pioneered, Axis2 is developing a more flexible pipeline architecture which can yet be managed and packaged in a more organized manner. This new design acknowledges the maturing of the Web services space in terms of new protocols such as WS-ReliableMessaging, WS-Security and WS-Addressing that are built on top of the base SOAP system. At the time Axis1 was designed, while it was fully expected that other protocols such as WS-ReliableMessaging would be built on top of it, there was not a proper extension architecture defined to enable clean composition of such layers. Thus, one of the key motivations for Axis2 is to provide a clean and simple environment for like Apache Sandesha and Apache WSS4J to layer on top of the base SOAP system. Another driving force for Axis2 as well as the move away from RPC oriented Web services towards more document-oriented, message style asynchronous service interactions. The Axis2 project is centered on a new representation for SOAP messages called AXIOM (AXIs Object Model). AXIOM consists of two parts: a complete XML Infoset representation and a SOAP Infoset representation on top of that. The XML Infoset representation provides a JDOM-like simple API but is built on a deferred model via a StAX-based (Streaming API for XML) pull parsing API. A key feature of AXIOM is that it allows one to stop building the XML tree and just access the pull stream directly; thus enabling both maximum flexibility and maximum performance. This approach allows us to support multiple levels of abstraction for consuming and offering Web services: using plain AXIOM, using generated code and statically data-bound data types and so on. At the time of Axis1's design, RPC-style, synchronous, request-response interactions were the order of the day for Web services. Today service interactions are much more message -oriented and exploit many different message exchange patterns. The Axis2 engine architecture is careful to not build in any assumptions of request-response patterns to ensure that it can be used easily to support arbitrary message exchange patterns.