XINS is a technology used to define, create, and invoke remote APIs. XINS is specification-oriented. When API specifications are written (in XML), XINS will transform them to HTML-based documentation and Java code for both the client-side and the server-side. The communication is based on HTTP. XINS competes with the complex SOAP technology. Main design goals include simplicity, scalability, and testability. XINS is not only a specification technology, but also an application development framework. It offers transaction logging, unique log documentation, and active code generation.
Membrane SOAP Router is a modular SOAP intermediary written in Java. It is fully configurable due to Spring style configuration. You can audit SOAP traffic, route messages through DMZ, and gather performance statistics. The small memory consumption of less than 20 Megabytes makes it possible to run an instance of Membrane SOAP Monitor on any computer that provides or consumes Web services.
LemonLDAP::NG is a modular Web SSO based on Apache::Session modules. It simplifies the building of a protected area with a few changes in the application. It manages both authentication and authorization and provides headers for accounting, so you can have full AAA protection for your Web space. LemonLDAP::NG is a complete rewrite of LemonLDAP. All components needed to use it and to administer it are included in the tarball. However, all modules developed for LemonLDAP may not work with LemonLDAP::NG.
python-fedex is light wrapper for Fedex's Web Services SOAP API. The intent is to stay out of the way of the developer as much as possible, while handling some of the more repetitive and mundane portions of forming and sending SOAP requests. The module makes use of the excellent suds package along with Python versions 2.5 and up, but not yet Py3K.
Chief Database records time series data in real time. Data is compressed to reduce disk requirements and improve performance. Redo logging and caching provide high performance on minimal hardware, with minimal data loss in the event of hardware failure. 1 million coordinates can be processed per second on server-level hardware. All interfaces are SOAP; allowing for easy integration with other systems and Web sites. Data is usually from a telemetered resource, but can also come from SNMP. Chief Trends allows for trending data inside Firefox. Chief Calculator is a Perl calculation engine to manipulate the data in whatever way you want.
iSfinx is a Web services based prototype of the Sfinx PIM. Sfinx is a personal knowledge and data manager which can manage your private data like contacts, events, notes, files, tasks, know-how, etc. Each data item is structured with abstract "slices", which are organized with a category hierarchy that you can define for your own needs. Every data item must be connected to some Sfinx object. Events can be connected to contacts, contacts to tasks, tasks to data sources, know-how, or notes, and so on. You can freely edit, delete, or reconnect them. Additional tags, which can be slices or other Sfinx objects, can also be attached to items, so any data you enter to Sfinx can be cross-connected with any other data or abstract category. A search engine helps you to navigate in this information ocean.
Moose is a framework for getting XML into and out of Java software. It integrates easily with Spring, Spring Web Services, or plain Java applications. It will generate an XML schema which describes your mapping configuration. Spring Web Services can wrap Moose's schema generator, creating a nice stack for simple, rapid development of SOAP Web services in Java.